catgirl, branch 1.9a IRC client https://git.causal.agency/catgirl/atom?h=1.9a 2021-08-15T16:24:15+00:00 Handle tags without values 2021-08-15T16:24:15+00:00 C. McEnroe june@causal.agency 2021-08-15T16:24:15+00:00 urn:sha1:df1e5613786ab7e0a40a42bd339e30355bc75165 Otherwise a tag with no value would cause a segfault trying to unescape the NULL tag pointer. This shouldn't happen for the server tags we parse, but clients could send @+draft/reply with no value. Fix missing include for flock(2) 2021-08-10T00:14:24+00:00 C. McEnroe june@causal.agency 2021-08-10T00:14:24+00:00 urn:sha1:3f3585d0f32e66ad5c8c6c713f315e14810230eb On OpenBSD it's in <fcntl.h>, and it gets declared anyway on FreeBSD and macOS. Curiously, on GNU/Linux, LOCK_* are defined, but flock(2) isn't declared. Silence maybe uninitialized warning 2021-08-10T00:12:44+00:00 C. McEnroe june@causal.agency 2021-08-10T00:12:44+00:00 urn:sha1:a585b1b073459187adeeba1bc9512eb556045b24 Wouldn't happen anyway since configPath will always return at least one path. Use (bright) red for \com text macro 2021-07-26T22:25:05+00:00 C. McEnroe june@causal.agency 2021-07-26T22:25:05+00:00 urn:sha1:56139227a4e59bc99e7c90bb8b6b0a76bebc4ed6 chroot: Avoid passing paths to -s 2021-07-21T01:27:24+00:00 C. McEnroe june@causal.agency 2021-07-21T01:27:24+00:00 urn:sha1:78a020df8242ae5e4e2ac210bc8d85dc27b43bb6 FreeBSD: Revert caph_enter(3) call to cap_enter(2) 2021-07-20T17:25:04+00:00 C. McEnroe june@causal.agency 2021-07-20T17:25:04+00:00 urn:sha1:d9388fa2a8672831075fa0e48dff35033347a4af caph_enter(3) is the same as cap_enter(2) except that it returns success even if the kernel does not support capability mode. Since we only enter capability mode when explicitly requested by the restrict option, it should fail loudly if it is not supported. On the other hand, we make calls to caph_rights_limit(3) and friends in some places regardless of whether we actually enter capability mode (to keep the code simple), so those should continue to succeed even if capability mode is not supported. Don't apply uiThreshold to Network and Debug 2021-07-20T16:09:24+00:00 C. McEnroe june@causal.agency 2021-07-20T16:09:24+00:00 urn:sha1:347e2b461f2fbe407cca9a4b59f1f00a01fccd7f Messages don't really need to be hidden from <network> and I think it could be confusing. Debug messages are all Cold so everything would be hidden, and I want to keep them that way so that <debug> doesn't clutter the status line needlessly. Add -q/quiet option to raise default message visibility threshold 2021-07-20T16:03:46+00:00 Klemens Nanni klemens@posteo.de 2021-07-17T20:04:15+00:00 urn:sha1:f8e3414af06df95b18b8e29caa74a7eea3022c92 Silencing all windows with `M-+' (across multiple catgirl instances) can be cumbersome, so provide an option to hide events, JOIN/PART noise, etc. by default (each window's threshold will persist across load/save cycles, i.e. when using the `-s/save' option). Started out as `-v | visibility = threshold' to set a specific level, the idea of a simpler toggle comes from june, who also squashed other bugs (as usual). chat.tmux.conf: Fix base-index setting 2021-07-15T18:43:30+00:00 Klemens Nanni klemens@posteo.de 2021-07-08T22:42:17+00:00 urn:sha1:773d5bbdc006077e93ee5e3dc54f3c8ae6f15f33 "base-index" expects integer values, tmux prints a warning at load-time but otherwise ignores the configuration line. Use /ns in manual example 2021-07-15T18:42:33+00:00 Klemens Nanni klemens@posteo.de 2021-07-08T12:26:06+00:00 urn:sha1:e365bae8e0c13b720d3b72fb1c84e1d550e6aa8e Follow a79a3fc "Use NS and CS server aliases".