statuscol.nvim VS Mosh

Especially for the appearance such as the fold icons, you can tweak it via statuscol.nvim or change neovim source code (no worries just a few lines) and build it by yourself, and please refer to this issue for details.

I just installed and configured statuscol.nvm. Everything is working great, however it's using a different highlight group for line numbers on lines where the text has been edited. I've tried many ways to find the highlight group that needs to be fixed, but I just can't find it. Is there a way to get the highlight group used in the statuscolumn?

I know that https://github.com/luukvbaal/statuscol.nvim has click handlers in case that code could help

2) Neovim offers that by default (although it isn't very sexy). We call that folding. You can use za, zo, zc to toggle (alternate), open and close folds respectively. There are built-in mappings to open and close all folds and so on (check :h zo). If you want to use your mouse though, you can also configure that using this plugin. I mentioned it isn't very sexy because, by default, folds aren't highlighted (something you can achieve with this plugin).

If you want to add a dependency to your config and use Neovim 0.9 or later, you can use statuscol.nvim.

Yes, my bad. I am using gitsigns, though I tried to set up statuscol.nvim without much success.

I see on your screenshot that you are manually handling file types with the statuscol plugin in order to hide the status column. That is fixed now and the plugin itself should do it correctly.

what aboug making a plugin or extend https://github.com/luukvbaal/statuscol.nvim ?

If you haven’t already, and I know this doesn’t hold up for GUI emacs or vim, but consider running them through https://mosh.org/

FWIW, I wouldn't try to parse escape sequences "directly" from the input bytestream -- it's easy to end up with annoying bugs. Longer-term it's probably better to separate the logic e.g.:

- First step (for a UTF-8-input terminal emulator) means "lexing" the input bytestream as UTF-8 into a stream of USVs, which involves some subtleties (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- Second step is to run the DEC parser/FSM logic on the sequence of USVs, which is independent of the escape sequences (https://vt100.net/emu/dec_ansi_parser ; https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- And then the third step is for the terminal to execute the "dispatch"/"execute"/etc. actions coming from the FSM, which is where the escape sequences and control chars get implemented (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

Without this separation, it's easier to end up with bugs where, e.g., a UTF-8 sequence or an ANSI escape sequence is treated differently when it's split between multiple read() calls vs. all in one call.

Btw, you can use mosh to hide the latency of SSH. https://mosh.org/

I've been using Kitty's SSH features for as long as I can remember but I recently setup Mosh and I really like how it doesn't drop connections and supports roaming.

I am surprised many people write about ssh into a server. Mosh[1] feels more responsive and it also supports longer sessions.

[1] - https://mosh.org/

Also they support Mosh which I install on my servers. It's way better than plain ssh when you're on mobile networks and wifi, especially with connections that are unreliable or bandwidth-constrained.

I’ve recently been experimenting with MoSH (Mobile Shell). Basically think SSH but with UDP - so more resilient to shoddy network conditions, roaming access points, etc.

If it is not for production (e.g. running as a daemon or a server) and you only care about the development, another ad-hoc way is using screen/tmus-like software incl. byobu, and combine it with mosh.