Recent commits to dotfiles.git (3e90e2af17b488d35d9a6049b95a7f5a31a09d2e)

tmux and vim to set terminal title

2024-04-27T11:54:08-07:00

</pre>

Add alacritty.toml to dotfiles to install

2024-04-27T00:20:10-07:00

</pre>

Alacritty to use DejaVu Sans Mono for Powerline

2024-04-27T00:13:43-07:00

For the git branch character  in the vim status bar.
https://wiki.dlma.com/linux#dejavu-sans-for-powerline-font
</pre>

Set $TERMINAL=alacritty for C-i vs Tab

2024-04-26T22:01:24-07:00

I want vim to keep C-o/C-i jump pairs and map Tab/Shift-Tab oo :bn/:bp,
and gnome-terminal can't distinguish between C-i and Tab.

So I need to install Alacritty where gnome-terminal comes default
and tell i3-sensible-terminal to use Alacritty.
</pre>

Add link to install tmux-256color database in macOS

2024-04-26T20:48:09-07:00

</pre>

tmux $TERM "tmux-256color" for visidata dot plots

2024-04-25T23:34:56-07:00

If $TERM is only "tmux" then VisiData (vd) doesn't
use as many colors as it can, easily demonstrated with
AirPassengers.csv
</pre>

When Tab distinguished from C-i, map it Buffer Next

2024-04-24T12:47:02-07:00

When in 'xterm' it seems like Neovim can distinguish between Tab and
Ctrl-i. But when in 'tmux' it can't. We always want to preserve
the C-i/C-o jump pairs, so only map Tab to :bn if it's different.

References:
https://vi.stackexchange.com/questions/16161/how-to-map-c-i-separate-from-tab/23344#23344
https://www.reddit.com/r/tmux/comments/114kzoo/tmux_cant_tell_ci_and_tab_apart/
https://github.com/tmux/tmux/issues/2705
</pre>

Clarify comment 'Shift-Tab'

2024-04-20T09:40:34-07:00

</pre>

Restore Ctrl-i (Tab) to mean "go to next jump pos"

2024-04-19T23:30:05-07:00

I had remapped Tab and Shift-Tab to mean next/prev buffer.
Didn't realize that Tab was Ctrl-i and I'd lost next jump pos.
(Funny, because it always jumped me to the other buffer, and
seemed mostly working.)

Now Ctrl-o and Ctrl-i are really working together again.
</pre>

Add commands SynStack and Hi for easier colorscheme edits

2024-04-16T09:08:04-07:00

Since I'm apparently going to be tweaking color themes, may as well
add a "Hi" (highlight) command to display the current syntax/highlight
info.
</pre>