skim VS Mosh

I really like using something like fuzzy search for menus like these. https://github.com/Cloudef/bemenu is pretty cool in that it works both in a terminal, X11 and on Wayland, so if you want to do something graphical later you can easily migrate. There's also fzf and skim, which work similarly but are only for the terminal.

Current profiles (to be improved upon): | Profile | Details | | ---------------- | ------------------------------------------ | | default | fzf-lua defaults, uses neovim "builtin" previewer and devicons (if available) for git/files/buffers | | fzf-native | utilizes fzf's native previewing ability in the terminal where possible using bat for previews | | fzf-tmux | similar to fzf-native and opens in a tmux popup (requires tmux > 3.2) | | max-perf | similar to fzf-native and disables icons globally for max performance | | telescope | closest match to telescope defaults in look and feel and keybinds | | skim | uses skim as an fzf alternative, (requires the sk binary) |

There’s also a variety of fuzzy finders like https://github.com/lotabout/skim or fzf. Basically the same thing, but different interface.

Have you ever tried sk? skim is an fzf re-write in 🦞. While I use it occasionally, I never really incorporated fzf into my workflow so I'd be interested to hear your opinion.

I’m not familiar at all with fzf, but I do know that skim supports this.

You state that as a blank and white fact, but there's nuance.

https://github.com/lotabout/skim/issues/317#issuecomment-652...

fzf skim

Agreed, but use skim instead

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.