5 ms·
The (arcane) tricks to make vim or any editor work well is: * export TERM=xterm-256color * Use tmux attach -2 (-2=256color) * In tmux <c-b>:set -g escape-tim
by stonewareslord 5y ago
The (arcane) tricks to make vim or any editor work well is:
* export TERM=xterm-256color
* Use tmux attach -2 (-2=256color)
* In tmux <c-b>:set -g escape-time 0
* In vim, :set t_Co=256
If your terminal is the issue, use rxvt-unicode256color as it is the best terminal emulator (kitty is too slow (Python), urxvtd can segfault, xterm lacks features), or iTerm2 for Mac (Terminal.app recently broke colors and haven't figured out how to fix them, plus it lacks panes which I use to simulate an i3 environment). On Mac you have to enable option as meta key to make alt work as well
- deleted 5y ago[deleted]
- d_tr 5y agoI use kitty and I have not experienced any slowness. What is slow about it?
- stonewareslord 5y agoI use i3 and win+enter is bound to spawn a new terminal. I had read that kitty was supposed to be super fast, but I tried it out and spawning a terminal was taking .5-1 second! I looked it up and found https://github.com/kovidgoyal/kitty/issues/330 https://github.com/kovidgoyal/kitty/issues/330 where the dev says: > that's just python interpreter startup time So... The answer is just "yeah it's slow". When you're used to a few milliseconds for terminal spawn, .5s is eons.
- d_tr 5y agoI use --single-instance and it spawns much faster (and eats way less memory). Even without this switch it does not take this long on my machine (certainly less than half a second), but yes it takes noticeably longer than, say, urxvt.