I haven’t been able to find all the right groups of people on the fediverse. And this makes me sad. I follow a group of people in my field of work and a large # of people in the Apple development ecosystem.
Wenn du noch nicht viel über die Themen weißt oder noch unschlüssig bist, solltest du dir das mal anhören - gibt einen guten Überblick über diese ziemlich ausgereiften Powertools.
cd - goes back to your previous directory. Also see pushd, popd if you want to treat the directory history as a stack. Nevertheless, excessively typing commands for navigating just gets you repetitive strain injury. I use ranger as a TUI file manager. Hopping in/out of the shell is as easy as S or Ctrl+D.
vim has an inbuilt diffing tool, vimdiff. It opens the two files side by side with color highlighting. It might not be provided by your default vim package. On Arch it's provided by gvim.
git rebase -i HEAD~5 is imo a better way to hack at your last 5 commits than (rebase, reorder, squash, edit, etc) than what I've seen GUI git tools do.
git add -p, git checkout -p(for "patch") runs the command on one chunk at a time, allowing you to inspect each one before doing anything. It's useful if you want to commit or undo only part of yout work. -p works for other commands too.
Experimenting with #vim-lsp + #rust and I think I need to dig into the colorscheme options for these 'hover' style 'windows’, because ouchie ouchie, my eyes.
People often talk about Emacs vs Vim. Every developer I’ve met uses Vim. Occasionally, some of the vim users will say they have previously emacs, but switched to vim.
So where are all the people who are currently using Emacs?
I’m not trolling or looking for an argument. I legit want to know!
Sometimes #postgresql feels like the #emacs of #databases. It has so many crazy features and yet I've never had comfortable muscle memory in it, so it always takes me longer to do about anything vs some flavor of #mysql (or #vim, depending on which tract you followed to get here).
Bon, après des essais de config pour Neovim via Flathub, j'ai dû casser un truc et je m'arrache les cheveux : en console, je ne peux même plus éditer un fichier avec « vim monfichier.txt» (oui, j'ai tjrs Vim), mais ça passe avec «sudo vim monfichier.txt» 😲
Je n'ai aucune idée comment rétablir tout ça et j'y ai passé 1 soirée… (no comment…).
Si quelqu'un peut me conseiller, ce serait formidable.
For anyone else configuring Ctrl at the position where on IBM keyboards Capslock is, just like God^WSun intended, on #GNOME you can use #Tweak tools in Keyboard & Mouse, Caps Lock behavior and select Make Caps Lock an additional Ctrl. Similar methods work on different compositors as well, as everybody uses xkb in the backend AFAIK.
This is not only useful to #Emacs users but also #Vi/#Vim, since that's also the position where it was on Bill Joy's keyboard, when he invented vi. Esc was where nowadays Tab is, however, remapping this is painful since Tab is very useful outside of vi. But using Ctrl+[ for Esc works wonders, so you don't need to reach up there. Of course, also use Ctrl+T and Ctrl+D for (un-)indentation in insert mode.
I also set Ctrl position to Left Ctrl as Meta which basically just gives me a huge two-button Meta key :-p
It also inhibits me from accidentally triggering caps lock from re-training. I'd love to actually just completely "disable" that button (combining "Caps Lock is disabled" with "Swap Ctrl and Caps Lock" does not achieve that :|)
I’m thinking of writing a small plugin that defines a cmdline mapping to insert the first-level heading, if the current buffer contains a #Markdown document. The idea is that you have something in the file like
2023-09-25 Meeting Notes
and then, later on, do
:w <some-mapping>.md
which expands to
:w 2023-09-25 Meeting Notes.md
Questions:
• Does such a plugin already exist?
• What would be a good key for that? I’m thinking of <C-R><C-T>, see :h c_CTRL-R
Speaking of QoL, I think I am finally going to try experimenting with making my #vim slightly more IDE-like, via experimentations w/ language servers and/or just additional plugins.
Eg, last night I refactored my oversized util module in babby's first Rust project, and did the usual (in this case, ack-driven) projectwide search-into-jumplist, + a per-buffer search-n-replace (repeated via command history each time).
Not /hard/, but still poorly-scaling mild drudgery.
radical idea for vim config: do it like the config.d folders in /etc -- split a monolithic init.vim/init.lua into a bunch of files that get sourced in alphabetical order
RIP Bram Moolenaar, the author of vim text editor (groups.google.com)
Here is a message from his family