dnkl changed the topic of #foot to: Foot - fast, lightweight and minimalistic Wayland terminal emulator || 1.11.0 || https://codeberg.org/dnkl/foot || channel logs: https://libera.irclog.whitequark.org/foot
pmnw has joined #foot
pmnw has quit [Quit: ERC (IRC client for Emacs 27.2)]
<alebastr> Arnavion: Fedora doesn't use /usr/etc. I know that there are people who participate in both distributions and are trying to copy such changes from openSUSE, but that didn't happen yet
<alebastr> we need more people complaining about breaking their immutable OS by editing configs in /etc :)
ghost08 has joined #foot
<alebastr> dnkl: with my packager's fedora on, sysconfdir/xdg/foot is fine. it's standard for desktop software and I won't even have to deal with migrating configs from previous location (looks at dunst)
<Arnavion> Ah
ghost08 has quit [Quit: WeeChat 3.5]
ghost08 has joined #foot
<sterni> 26peetee
<sterni> ooops
ghost08 has quit [Quit: WeeChat 3.5]
<kraftwerk28> Saw this issue https://codeberg.org/dnkl/foot/issues/1009 after some mappings in my recent neovim stopped working. Is there a solution other than `echo -e '\e[>4;2m'`?
<kraftwerk28> And still I don't understand how this happens... `showkey -a` displays correct character in foot and other terminals.
<dnkl> kraftwerk28: well, >4;2m is the problem in this case... it's an escape that enables a special keyboard mode in xterm (and foot), where many key combinations send escape sequences. Recent neovim versions have started enabling this mode
<dnkl> there's a PR up for foot that tries to increase compatibility with XTerm
<dnkl> would be great if you could test that :)
<kraftwerk28> Do you know why neovim started using it?
<dnkl> because it disambiguates key combos
<dnkl> without it, applications cannot tell the difference between e.g. "key" and "ctrl+key", for many keys (and other modifiers)
<kraftwerk28> Also, where can I find the docs about \e[>4;2m? Searched through foot-ctlseqs, but no luck
<dnkl> mode '2', specifically
<dnkl> but the documentation is pretty slim...
<dnkl> and you're right, it seems we don't even mention it in foot-ctlseq
<dnkl> foot-ctlseq has been updated in #1017
<kraftwerk28> Ok, should I clone+build latest foot from master to test it?
<kraftwerk28> I'm currently using it from arch packages
<dnkl> almost; clone and checkout the "modify-other-keys-2-improve-xterm-compatibility" branch, then build
<dnkl> (foot --version should mention that branch name)
<dnkl> note that it is quite possible there are bugs in neovim as well, related to this
<dnkl> you might want to follow https://github.com/neovim/neovim/issues/18010
<kraftwerk28> Are you planning to add some foot.ini config flag to enable/disable that xterm-compat mode?
<dnkl> no, it's intended to be enabled/disabled by applications. Just like what's happening here
<kraftwerk28> ah, so foot doesn't handle \e[>4;2m properly right now, am I right?
<dnkl> that's at least part of the problem. That's what the PR I linked tries to fix
<dnkl> but since neovim just recently started enabling it, there may very well be bugs in neovim too
<kraftwerk28> tbh it's neovim which should have some option for disabling this behavior. Or is it there?
<dnkl> correct, neovim is where a potential option should go. Don't know if there is - I don't use neovim as my main editor
<dnkl> the commit linked from the foot issue (https://github.com/neovim/neovim/commit/b81c310d4) mentions this: ext.enable_extended_keys. Perhaps that tells you something?
<dnkl> alebastr: "packager's fedora" :D
<dnkl> didn't get that one until now...
<dnkl> my brain just got a parse error the first time I read it :|
Arnavion has quit [Ping timeout: 260 seconds]
Arnavion has joined #foot
<kraftwerk28> dnkl, built from the branch you mentioned, works like a charm :+1:
<kraftwerk28> (at least I didn't find any bugs yet)
<dnkl> kraftwerk28: great, thanks for testing. I'll wait for more testers and feedback for a couple of days before merging
cvmn has joined #foot
cvmn has quit [Ping timeout: 240 seconds]
<kraftwerk28> dnkl, regarding this issue: https://codeberg.org/dnkl/foot/issues/828. Why storing underline bit/it's colour per each cell instead of making a separate struct which would hold an array of lines with their "coordinates", colours, lengths etc? The for each frame, draw the characters then lines on top. Sorry if this sounds mindless, I'm just looking into implementing such feature
rj1 has quit [Ping timeout: 260 seconds]
rj1 has joined #foot