519fcc436f
Factor out reply count checking and decrementing
2020-12-30 16:54:03 -05:00
8b6a476c35
Add /whowas
2020-12-30 14:29:32 -05:00
05fbcb41c9
Show setnames like nick changes
2020-12-30 00:19:52 -05:00
1662b01a5f
Add /setname command
...
I'm not sure about that replies check in handleStandardReply. If more of
those are added the reply counter system will definitely need
refactoring.
2020-12-29 23:54:30 -05:00
b4ed58602b
Handle so-called Standard Replies
2020-12-29 23:11:57 -05:00
997c932e83
Handle 437 ERR_UNAVAILRESOURCE like ERR_NICKNAMEINUSE
...
Not totally clear under what conditions 437 is returned, but if it
happens during registration, we should pick a new nick.
2020-12-05 23:06:45 -05:00
ded0455d3e
Remove static buffer from colorMentions
2020-11-08 15:16:25 -05:00
a8264f31e0
Remove static buffer from capList
2020-11-08 15:07:13 -05:00
a0abd6582e
Highlight changed portion of topic
...
"%.*ls" is useless.
2020-11-08 12:42:01 -05:00
f7f5acbbe2
Double up /help for server help
...
While the automatic search via LESS is neat, I don't think it's very
useful. Just always open the manual to the COMMANDS section, and fix it
to append to LESS rather than replace it.
2020-10-02 19:38:37 -04:00
f3a56b0d01
Use WHO for /ops
...
Accumulate names in a buffer and show away status.
2020-09-30 19:21:34 -04:00
3e67bf6557
Add /ops command
...
It's pretty awkward with large channels since NAMES isn't sorted by
prefixes or anything... But having it accumulate names across many
replies would require more reworking.
2020-09-30 17:52:39 -04:00
2b8a45779d
Switch back to checking for server by nick with '.'
...
This fixes a bug where if you send a private message before joining any
channels, your message will be routed to the <network> window. That
happens because without a JOIN, self.user remains unset, which means
that require will copy self.nick (set by echoMessage) to self.host. The
easiest solution is to go back to checking for '.' and add a '.' to the
default nick, so now if a server sends a NOTICE with no origin it will
look like -*.*- which is kinda cute.
2020-09-18 18:13:09 -04:00
e229931253
Don't call completeTouch for ignored messages
2020-09-02 17:51:51 -04:00
b06470294d
Match mentions case-sensitively
...
The mention coloring code already matches case-sensitively, and any
proper ping should be using tab-complete anyway so there's no reason for
differing case. And the month of June should not ping me.
2020-08-18 21:26:17 -04:00
10e953b8b5
Set origin fields to "*" if missing
...
Also determine if a message is from the server by if the host field has
been copied from the nick field.
EFNet sends NOTICEs with no origin during registration.
RFC 1459 has this to say:
> If the prefix is missing from the message, it is assumed to have
> originated from the connection from which it was received.
I suppose a more correct implementation would be to set the origin to
the hostname of the server, but we don't store that globally, so this
is good enough.
2020-08-16 22:52:01 -04:00
814c36223a
Say "OpenSSL" in additional permission notices
...
LibreSSL is "a modified version of that library".
2020-08-04 12:19:14 -04:00
4c1b1fc6a3
Replace catf with something that tracks len
...
Also the old catf would be broken with -DNDEBUG oops!
2020-07-30 14:37:46 -04:00
5a3b63e444
Remove use of strlcat
...
catf is not better though and should really be replaced.
2020-07-30 13:05:24 -04:00
3e03b7502b
Add current topic to tab-complete so it can edited
2020-07-13 10:22:33 -04:00
e6db22d2bb
Don't scan ignored messages for URLs
2020-07-09 22:43:35 -04:00
94fb9798c5
Bump ParamCap to 254
...
Apparently IRCds have decided that the 15-parameter limit doesn't matter
anymore. 254 is the maximum number of single-byte parameters (following
a single-byte command) which fit in a 512-byte CR-LF-terminated line.
When everyone decides that the 512-byte line length limit doesn't matter
either, I will delete my software and people can use some JavaScript
garbage instead.
This makes struct Message 2080 bytes, but there's only ever one or two
of them around at once. Avoid passing it by value to handle.
2020-06-24 13:36:24 -04:00
4fb94a1a22
Color mentions up to first ": " rather than just ":"
...
Avoids coloring everything up to a ":)".
2020-06-16 23:14:07 -04:00
721c3a9ee6
Add additional permission for linking with LibreSSL
...
https://www.gnu.org/licenses/gpl-faq.en.html#GPLIncompatibleLibs
2020-06-08 17:48:07 -04:00
73bda18110
Check ignores against id
...
Otherwise they do not work correctly for QUIT and NICK. This also lets
you ignore private messages only by putting the nick in the third field.
2020-04-07 13:18:42 -04:00
1969c9125f
Error on missing MODE parameters
2020-04-05 13:17:38 -04:00
bb531a71b1
Error on invalid ISUPPORT values
2020-04-05 13:11:19 -04:00
75a6aa9258
Use gnu-case-range and gnu-conditional-omitted-operand extensions
...
I'm sad to do this but I just can't stand writing (foo ? foo : bar)
anymore.
2020-04-03 17:10:52 -04:00
25f419465f
Add /ignore message filtering patterns
2020-03-31 14:30:42 -04:00
ff78362826
Replace some declaration; while loops with for loops
...
I should have been using this for getopt loops already but the call here
is slightly too long to fit on one line as a for loop.
2020-03-30 19:44:45 -04:00
bb2f3c7a01
Rewrite mode formatting again and write to log
...
Going back to one line per mode change again because it's easier.
2020-03-28 12:08:10 -04:00
3dc998272e
Log chat events
...
Still missing is logging MODE changes, which will be hell, unless it
just logs the raw stuff.
2020-03-25 18:58:48 -04:00
4f40ace9d4
Track MODE in replies
2020-03-23 16:52:24 -04:00
cf1545870a
Assume worst case for unknown user and host in splitMessage
...
The default USERLEN of 9 doesn't have a great source, the RFC only says
that nicks are length 9, so my assumption is that usernames are not
longer.
2020-03-23 13:25:10 -04:00
eb6316c235
Track own host, handle CHGHOST
2020-03-22 14:32:20 -04:00
0d0a6d1575
Handle RPL_CHANNELMODEIS
2020-03-22 11:40:58 -04:00
61828a12e9
Handle user mode changes
2020-03-22 11:26:16 -04:00
8da45d9183
Rewrite handleMode
2020-03-22 11:18:21 -04:00
1c508b78ab
Handle RPL_UMODEIS
2020-03-18 08:33:42 -04:00
2f53f75892
Ignore 422 ERR_NOMOTD
...
pounce will start sending these because some silly clients don't think
they're connected until some MOTD reply...
2020-03-09 03:08:59 -04:00
7e120f00a1
Set self.pos before handling the message
...
This intuitively feels wrong, but isn't. Most importantly, handleError
immediately exits, but we still need to "consume" that message,
otherwise pounce will keep sending it on reconnect. The same goes for
any other handler that might cause an exit, such as a require parameter
count failure.
2020-03-08 23:15:56 -04:00
8570a62235
Implement the causal.agency/consumer capability
2020-02-29 01:03:46 -05:00
78b4832bfe
Add raw modes to mode message
2020-02-25 03:00:36 -05:00
e9524b4af3
Handle changing setParamModes, paramModes and other channel modes
2020-02-25 02:54:15 -05:00
431945614d
Fix handling EXCEPTS and INVEX without values
2020-02-25 02:24:29 -05:00
3c5e1c95a4
Add /mode, /except, /invex and handle lists replies
2020-02-25 02:12:35 -05:00
c3c40d738b
Accumulate mode changes into a buffer for one message
2020-02-23 22:44:19 -05:00
9609723dc6
Handle ERR_CHANOPRIVSNEEDED
2020-02-20 05:04:58 -05:00
50a6d34a55
Handle MODE changing channel list modes
2020-02-20 04:53:06 -05:00
c2c8595012
Handle MODE setting channel prefix modes
2020-02-20 04:18:25 -05:00
a3b6d5d9a7
Change ban list formatting
2020-02-20 03:44:57 -05:00
b3c5458fc9
Rearrange some handlers
2020-02-20 03:18:48 -05:00
42ad42887c
Handle RPL_INVITING when no invite-notify
2020-02-20 02:32:36 -05:00
5c79b16a51
Handle ERR_BANLISTFULL
2020-02-20 02:13:23 -05:00
1b01045bf0
Add handlers for user-in-channel errors
2020-02-20 01:52:58 -05:00
f494fe6edb
Add generic error reply handler
...
This should have been in way earlier...
2020-02-20 01:38:31 -05:00
56de4668ac
Add /ban, /unban and handle ban list replies
2020-02-19 21:47:16 -05:00
2a33ee68dd
Format WHOIS signon date with %F %T
2020-02-19 21:29:51 -05:00
ba524ed804
Replace a lot of snprintf with a catf implementation
2020-02-16 19:12:19 -05:00
3885dd5231
Add 379 to WHOIS responses
2020-02-16 18:42:38 -05:00
edd8855418
Track EXCEPTS and INVEX modes
2020-02-16 18:31:50 -05:00
f84ab67311
Apply colorMentions to actions
...
The first-two-words branch works well for "/me verbs nick".
2020-02-16 05:22:28 -05:00
700b5d5870
Replace small integers in size_t with uint
2020-02-15 22:19:55 -05:00
83df94b359
Still add nick without prefixes to complete
2020-02-15 22:19:05 -05:00
9b1ab69908
Track PREFIX modes and CHANMODES
2020-02-15 05:29:54 -05:00
cd341076c0
Show prefixes in NAMES and WHOIS replies
2020-02-15 05:04:43 -05:00
42d106260b
Separate network info from self
2020-02-15 04:54:53 -05:00
39a343980b
Add /invite
2020-02-14 21:36:58 -05:00
8aa6dd86f6
Add /away
2020-02-14 21:10:40 -05:00
be08880fac
Only exit on errorneous nick during registration
2020-02-12 19:30:07 -05:00
05579773c8
Add 378 to list of WHOIS responses
...
It's the one (from freenode anyway) that tells you where you're
connecting from.
2020-02-12 19:14:49 -05:00
489df70c37
Add /list
2020-02-12 02:39:23 -05:00
3a325d3914
Handle RPL_AWAY
2020-02-12 00:17:28 -05:00
7c171b8aff
Rename query ID on nick change
2020-02-11 18:23:04 -05:00
6a5ebb0bab
Don't insert color codes for non-mentions
2020-02-11 18:15:25 -05:00
4d532ec738
Take first two words in colorMentions
...
This lets phrases like "hi june" get colored, but still doesn't get
carried away.
2020-02-11 18:08:05 -05:00
cc80fae758
Set self.nick to * initially
...
Allows removing a bunch of checks that self.nick is set, and it's what
the server usually calls you before registration.
Never highlight notices as mentions.
2020-02-11 17:52:55 -05:00
83a8952cf5
Move base64 out of chat.h
2020-02-11 17:40:08 -05:00
ac4876718f
Fix whois idle unit calculation
...
Rookie mistake.
2020-02-11 04:00:25 -05:00
36e0bbc4cd
Split on <> in colorMentions
...
This allows it to color the nick in the common case of pasting "<nick>
something they said" into the chat. Technically it should color the
brackets too but that would be too much work.
2020-02-10 20:58:14 -05:00
80a79467ef
Only automatically switch to expected joins
2020-02-10 20:24:07 -05:00
8e55c049b5
Avoid coloring mentions if there are control codes
...
This was breaking leading color codes.
2020-02-10 03:58:25 -05:00
fabb89077d
Update prompt when own nick changes
2020-02-10 01:29:30 -05:00
3436cd1068
Add /whois
2020-02-09 16:45:49 -05:00
82cf445858
Add self.nick to completion in Network, not None
2020-02-09 02:16:17 -05:00
a212a7ae2c
Show realname on JOIN if it is different from nick
2020-02-09 00:55:41 -05:00
b30b93f672
Use fmemopen to build colored mentions string
2020-02-08 23:29:32 -05:00
ec73174c4c
Use unexpected NAMES replies to populate complete
2020-02-08 22:55:11 -05:00
9cbec9ca7e
Color mentions
...
Sort of like Textual does, but only in the first part of the messaage,
either before a colon or before a space. Hopefully this makes it less
costly than it would be, and prevents false positives on people with
common nouns for nicks.
2020-02-08 22:51:13 -05:00
f502260dd0
Scan messages for URLs
2020-02-08 18:29:01 -05:00
b6bf6d62b0
Only show expected topic/names replies
2020-02-08 03:15:17 -05:00
b5707af4b8
Handle KICK
...
See I knew the color cache in complete would be useful in at least one
place!
2020-02-08 00:58:17 -05:00
f14175ebed
Handle QUIT
2020-02-08 00:36:23 -05:00
7ebfeea330
Handle NAMES reply
2020-02-08 00:25:09 -05:00
58e1d5b4e2
Handle NICK
2020-02-08 00:01:59 -05:00
8b7cc1a0ed
Clear completion for ID on self-part
2020-02-07 23:44:03 -05:00
d314523b90
Update completion on join, part, privmsg
2020-02-07 23:33:23 -05:00
87e42cc627
Color notices LightGray by default
2020-02-06 22:59:49 -05:00
34514cf2ee
Render actions in italic
...
Also render italic as normal if it's unsupported, as that is what would
happen anyway if curses has A_ITALIC but the terminal has no sitm. That
format string is kinda bad.
2020-02-06 18:48:49 -05:00
e1f10958c9
Never consider notices hot
2020-02-06 04:37:28 -05:00
C. McEnroe