03:53 <feinedsquirrel> Another question, if I may. In Termite I am able to set the cursor location in vim (I'm on arch linux) by clicking at the desired location. Foot does not let me do that. I read through the foot and foot.ini man pages, but can't figure out if what I need is in there. Is this just something that isn't possible in foot?

03:55 <manio> feinedsquirrel: fwiw just also tested it in neovim now and I my main cursor is still in previous place

03:56 <manio> it seems it is because the text is selected and probably it was not a good idea to move the cursor when selecting text

03:56 <manio> one way or another i think dnkl will tell you more...

04:02 <feinedsquirrel> manio: thanks for verifying, yeah, that makes sense, not moving cursor during selection. Hope there's a way to make it happen

08:24 <dnkl> feinedsquirrel: manio: I don't use vim myself... But, what does the mouse cursor look like while inside vim? An I-beam, or a pointer (arrow)?

08:27 <dnkl> In any case, I suspect the issue is that vim, before enabling many features, checks the name of the terminfo against a pre-defined list. If you're not on that list, tough luck. Last time I checked, foot was not on that list

08:28 <dnkl> So, you could try running vim with TERM=xterm-256color, and see if that works better

08:29 <dnkl> If it does, you can set term in your vimrc (rather than changing TERM for *all* applications in e.g foot.ini)

08:29 <dnkl> FWIW, I use neovim myself when I want a vim-like editor

08:36 <manio> dnkl: the mouse cursor inside vim is I-beam for me

08:37 <manio> dnkl: I am also using neovim here btw

08:37 <dnkl> manio: ok, then it looks like vim hasn't enabled mouse capturing. And then clicking-to-move the cursor obviously will not work

08:38 <dnkl> Let me check my own vim/neovim configs later, when I'm at a computer

08:38 <manio> oh and I have set xterm-256color currently

09:40 <dnkl> feinedsquirrel: manio: for vim (not neovim), you need 'set ttymouse=sgr' and 'set mouse=a' in your vimrc

09:40 <dnkl> not sure what you need for neovim. My conf is empty, and mouse just works...

09:42 <dnkl> perhaps it depends on which version of neovim you're on (0.5.1 here)

09:44 <manio> same version here (I use arch btw ;)

09:45 <manio> dnkl: let's see what feinedsquirrel will find out... I personally don't need a mouse in neovim, frankly this is why I am using vim (to use it with keyboard only) :)

09:46 <manio> I was only trying to help/diagnose in my env

09:46 <dnkl> manio: got it, and thanks! :)

10:21 <brocellous> neovim mouse works fine for me in foot

15:42 <feinedsquirrel> I hope y'all live in a very different time zone than I do. :) First off, using the default vimrc for Arch, I have an I-beam mouse cursor (not a pointer). If I set TERM=xterm-256color, or, if I manually assign ttymouse=sgr, or, if I do both, I have a pointer mouse cursor, and I am able to click to place the input cursor. ...

15:45 <dnkl> feinedsquirrel: great! Must likely, vim doesn't want to enable mouse capturing automatically when running in a terminal emulator it doesn't recognize. Xterm it knows supports it, but "foot".... Never heard of it :D

15:45 <feinedsquirrel> ... reading the ":help ttymouse", looks like xterm, screen, tmux, and "st" terminals are on that short list you mentioned. It also says if compiled in, and "t_RV is set to the escape sequence to request xterm version", the ttymouse is set to sgr by default. Am I to read that as conditional on if "TERM=xterm*"? Arch xterm version is 369, so I'm assuming that extra condition must be met.

15:46 <feinedsquirrel> Haha, yeah, thanks for pointing me in the right direction. I assume termite worked by default because its terminfo file is called xterm-termite.

15:48 <dnkl> feinedsquirrel: probably the exact reason it's called "xterm-termite"...

15:48 <dnkl> Which leads to terminal applications going to (greater) lengths to try to differentiate the real xterm from terminals pretending to be xterm...

15:49 <dnkl> Because only xterm supports *all* features of xterm

15:50 <feinedsquirrel> yeah, I'd bet. There are probably a lot of tools written with xterm in mind, easy hack to get basic behavior.

15:50 <feinedsquirrel> makes sense

16:05 <dnkl> European timezone here, btw