https://git.dlma.com/dotfiles.git/tree/f3a703a2a266d735171f18752a4e3b8317d9bd14 Recent commits to dotfiles.git (f3a703a2a266d735171f18752a4e3b8317d9bd14) 2025-06-23T10:11:41-07:00 tag:gitlist.org,2012:commit/f3a703a2a266d735171f18752a4e3b8317d9bd14 Update comment in .vimrc: Add Ghostty 2025-06-23T10:11:41-07:00 dblume david.blume@gmail.com <pre>Oops, this tiny tweak to nvim's init file didn't make it to .vimrc. &lt;/pre&gt; tag:gitlist.org,2012:commit/e1ae87aa9f2d21c01114b437b47a87a1cd9fe908 vim documentation tweaks 2025-06-23T09:06:52-07:00 dblume david.blume@gmail.com <pre>Decided to remove a "Will remove this section" bit, and clean some formatting. May as well mention Ghostty where I mention Alacritty. &lt;/pre&gt; tag:gitlist.org,2012:commit/4d07a5c5d3cad6c57c08705a6596514dcdceaea1 Vim deletes go to a useful register again. 2025-06-10T22:18:07-07:00 dblume david.blume@gmail.com <pre>Argh. Turns out my muscle memory does rely on deletes going to a register. Writing a note to myself that really the only way to do puts (pastes) that overwrite is to do so over visual selections, not deletes (d,D) or changes (c,C). &lt;/pre&gt; tag:gitlist.org,2012:commit/5ddadd027a3a3ab2a50c91c09b6fc4f5ae383bef vim delete won't affect clipboard; claude-sonnet-4 2025-06-10T14:37:42-07:00 dblume dblume@roku.com <pre>&lt;/pre&gt; tag:gitlist.org,2012:commit/e5c165cddb0492867dbfe53cbe74235f6b1119f7 <leader>v to move window to right, show prev on left 2025-06-04T21:59:34-07:00 dblume david.blume@gmail.com <pre>Usually when I want to move the current window to the right, I want to see another buffer on the left. Go ahead and just do that Now, <leader>v does: 1. <C-w>v make a vertical split 2. :bp show previous buffer here on left 3. <C-w>l make the right window active &lt;/pre&gt; tag:gitlist.org,2012:commit/16ad8dc715065a7c824bc4c0754fe12bb4ae7021 Make ghostty match my catppuccin mocha overrides 2025-05-22T09:10:06-07:00 dblume david.blume@gmail.com <pre>Even though I now dynamically set terminal colors via the script bin/set_colorscheme. Using the terminal's settings now is a fallback. &lt;/pre&gt; tag:gitlist.org,2012:commit/f5fe4773bdaec5e2607b955abfda1683bb029caf dark teal float windows; lsp clangd only if it exists 2025-05-20T20:08:59-07:00 dblume dblume@roku.com <pre>&lt;/pre&gt; tag:gitlist.org,2012:commit/decdb842840a0471cb2ecfc16500045f37799581 Add clangd LSP support 2025-05-20T13:24:26-07:00 dblume dblume@roku.com <pre>This is a feature in progress. Hopefully it fails gracefully when clangd is not available. LSP uses floating windows, so had to add styles for them. I'm not done with settings or they keymaps. &lt;/pre&gt; tag:gitlist.org,2012:commit/16b1d2c4d8b28f08f428aae1e3213ac0117ab0be Very slightly fade blue and darken background. 2025-05-13T07:16:15-07:00 dblume david.blume@gmail.com <pre>Thought I could live with it, but such a light blue background affects how other gray terminal apps look, so make the background a little less blue, and darken it a touch. &lt;/pre&gt; tag:gitlist.org,2012:commit/50e5cb0149dd6741022aa0d56badd4a731b8aefa Lower blue saturation on "white" 2025-05-12T23:44:42-07:00 dblume david.blume@gmail.com <pre>Moving from the "white" on the main screen to some vim themes made actual grays look ugly spoiled grey. 1. Use Paint.net to reduce saturation of blue 2. Make Foreground be same as white. This allows some terminals to fake "bold" by using bright-color of foregorund. 3. Reduce saturation of bright white too. &lt;/pre&gt;