Dont queue msg if its a WHOIS msg already queued as last msg #1485
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Found by: michaelortmann
Patch by: michaelortmann
Fixes: #715
One-line summary:
Dont queue msg if its a WHOIS msg already queued as last msg
Additional description (if needed):
We already have config setting double-server, but it defaults to 1 and i guess it would have side effects to change its default value to 1, while sending two identical WHOIS in a row should be avoided and doesnt make sense.
eggdrop/eggdrop.conf
Lines 1250 to 1251 in 322bddb
Test cases demonstrating functionality (if applicable):
.console *
connect to irc server
Before:
After: