| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
This feels a little redundant but the API makes sense, I think?
|
|
Doesn't work when colors are disabled.
|
|
|
|
So that more values can be added sensibly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
As a side-effect, even with only one nick set you'll still be
highlighted by it even if your current nick is different.
|
|
For some reason this makes it look so much better to me.
|
|
Also prefix with the numeric. I don't really want to show numerics
to the user, but I'm not sure these really make sense without.
|
|
|
|
|
|
Currently only /setname.
|
|
|
|
|
|
|
|
Woops! BASE64_SIZE is the size of the string buffer. Somehow ergo
is the only server software (that I know of) to reject the accidental
null byte.
Reported by smlavine.
|
|
So that they can be hidden with M-+.
|
|
How did this normal sounding format string get in there!
|
|
<https://modern.ircdocs.horse/index.html#rplwhoisspecial-320>
|
|
POSIX does not define a %F for strptime[1], but does define %F for
strftime[2]. Afaik most libc's implement %F for both, but musl is very
standards-compliant and does not have %F on strptime, leading to
unparsed message tag times, which causes all backlog sent from bouncer
on startup to have a timestamp of the current time, instead of the
actual timestamp sent.
[1] https://pubs.opengroup.org/onlinepubs/9699919799/functions/strptime.html
[2] https://pubs.opengroup.org/onlinepubs/9699919799/functions/strftime.html
|
|
Only the first colon should be replaced with a null byte.
Ported from pounce.
|
|
|
|
|
|
|
|
|
|
Used by Solanum for "actually using host".
|
|
Missed this one.
|
|
The format of the reply is defined as "<nick> :{[@|+]<channel><space>}".
|
|
|
|
`-H 0,0`/"hash = 0,0" makes catgirl mostly colorless which is great,
but topic changes still hardcode brown/green colors to show differences
which is usually not desired by users (like me) disabling colors.
Go for a less eye stressing topic change message that shows both old
and new in reverse video with default terminal colors.
This isn't perfect, other parts of catgirl still hardcode colors and
`-H 0,0`/"hash = 0,0" was never meant to disable colors completely, but
topics change often enough that avoiding less readable^Waccessible topic
diffs seems sensible enough.
NB: parseHash() is brittle and "0,0" is not the only value disabling
colors...
|
|
|
|
It should have 4, but the handler only uses 3.
|
|
|
|
At least in InspIRCd's implementation, you only get invite-notify
INVITEs if you are op, so inviting with no op (where allowed by a
channel mode) results in only a 341. On the other hand, inviting
as an op produces both a 341 and an INVITE, so will be displayed
twice, but showing something sometimes twice is better than not
showing it at all.
|
|
This feature is rarely used, so just skip STATUSMSG prefixes in the
target so messages get routed correctly.
|
|
This restores showing the topic and names for automatic joined
channels, while still avoiding touching the windows, by using Cold
heat.
|
|
In other words, only automatically switch to an automatically joined
channel window if there's only one. Otherwise, stay on the <network>
window and avoid touching the channel windows with their automatic
topic and names replies.
This fixes unintentionally clearing saved window unread counts when
rejoining channels automatically by switching to them as they are
joined.
|
|
This is used by InspIRCd to indicate if a user is a bot (if it set
user mode +B).
|
|
Otherwise they are invisible with M-+ and commands having no output
is confusing.
|
|
|
|
|
|
|
|
|
|
|
