Sébastien Helleu
Sébastien Helleu
@Hackerpcs, could you please get a backtrace with gdb? The WeeChat crash log file doesn't provide accurate information on the exact location in code where the crash happened. Thanks.
Hi, Thanks I can reproduce the issue on Archlinux with Ruby 3.0.1. For now, Ruby 3 is not supported in WeeChat and has not been tested at all, so I...
Hi, As mentioned in the iterm2 issue (on GitLab), the problem is that ncurses doesn't support this OSC8 ANSI code. I made a POC, visible in this commit: 2d387313a099fcf0673b3d955fee09adcec2e4fb (very...
I fixed by displaying always the same message, which is now: `lag is high, disconnecting from server xxx`. If option `autoreconnect` is `on` (default and recommended value), another message will...
Thanks for testing and reporting it, it's now fixed!
Hi @stapelberg, Sorry for the long time to reply, I was focused on other bugs and new features in WeeChat for the release of v1.2 (scheduled in two days). So...
This is the current behavior, not really a bug, but the help on the option does not mention it applies only to WeeChat config itself (weechat.conf). That's why I tagged...
Hi, This is not really a bug but the way dynamic options are working. Bars, like triggers and some other settings are dynamic options, that means you can add/rename/delete bars...
Yes the script iset.pl could check if it's a dynamic option/section (not sure if it's really easy) and if yes do not display the default value if it's not relevant.
But this will not fix the default value displayed with `/help weechat.bar.xxx.option`.