| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
Currently only /setname.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This saves 4K in the edit buffers, not to mention all the heap
allocations for the separate mbs buffers!
There might be a way to be more clever about capacities, but I don't
think it's worth it.
|
|
|
|
|
|
| |
Otherwise a command that switches windows will update the status
line while the edit buffer still has input "pending", showing an
indicator.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
In other words, warn when a function is missing static. I don't see
why this isn't in -Wextra.
|
| |
|
|
|
|
| |
I know, it feels wrong.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Losing tab complete and text macros, for now.
This new implementation works on an instance of a struct and does
not interact with the rest of catgirl, making it possible to copy
into another project. Unlike existing line editing libraries, this
one is entirely abstract and can be rendered externally.
My goal with this library is to be able to implement vi mode. Since
it operates on struct instances rather than globals, it might also
be possible to give catgirl separate line editing buffers for each
window, which would be a nice UX improvement.
|
|
|
|
|
|
|
|
| |
Do some extra work by adding the portion before the cursor to the
input window twice, but simplify the interaction with the split
point. This fixes the awkward behaviour when moving the cursor
across colour codes where the code would be partially interpreted
up to the cursor.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We don't use any flags, so just define them in the compat source
file.
|
|
|
|
| |
At 5d08070de6aadd979e3752263d2ec1e709bf037e.
|
| |
|
|
|
|
| |
This matches behaviour of, e.g. zsh -o emacs.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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-+.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When cross-compiling, it's common to have executables prefixed with
the name of the architecture you're building for,
e.g. aarch64-unknown-linux-musl-cc or x86_64-unknown-freebsd-pkg-config.
Lots of build tools support a PKG_CONFIG environment variable to
enable this use case.
With this change, I was able to successfully cross-compile and run
catgirl.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allows completing a nick at the beginning of a message without a
colon by continuing to press tab, as well as after another nick
already followed by a colon without turning it into a comma-separated
list of nicks all followed by a colon. For example, tab can be used
to cycle between the following pairs:
nick1: |
nick1 |
nick1, nick2: |
nick1: nick2 |
|
|
|
|
| |
How did this normal sounding format string get in there!
|
|
|
|
| |
<https://modern.ircdocs.horse/index.html#rplwhoisspecial-320>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Strip formatting when calculating the timestamp width to avoid
moving a bunch of code around. Use styleAdd (now with an initial
style parameter) to show timestamps.
This allows changing the style of the timestamps from the default
gray using literal IRC formatting codes in the string. Not ideal,
but no new options needed.
Suggested by Hoël Bézier and Sebastian LaVine.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Otherwise only /ban can be used to list bans and /mode b or /mode
+b won't show the listing.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
catgirl correctly handles receiving "self-messages". pounce always
sends them.
[1]: https://wiki.znc.in/Query_buffers
[2]: https://defs.ircdocs.horse/info/selfmessages.html
|