m5l.eu is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Kennt ihr die bash Option checkjobs?
Ich selber habe es noch nicht benutzt, aber hört sich ganz Interessant an, wenn man viel mit Jobs arbeitet.
Vielleicht sollte ich mal ein Hintergrundprozess erstellen, der in ein fifo schreibt. Ich komme bei #vim immer durcheinander, ob ich in der shell oder in der "vim shell". Mit checkjobs müsste das Terminal ja mit einem schreiben in ein fifo in der bash bleiben. 🤔
#!/bin/shCC: @mms@bsd.cafePLUGIN_DIR="${HOME}/.vim/pack"
echo "Updating all plugins in ${PLUGIN_DIR}"
for directory in ${PLUGIN_DIR}/*; do
for subdir in "$directory"/start/* "$directory"/opt/*; do
if [ -d "${subdir}" ]; then
plugin=$(basename "${subdir}")
echo "Updating ${plugin}"
git -C "${subdir}" pull
fi
done
done
CC: @mms@bsd.cafe
Because I realized that all of the thing that I truly needed to do were part of Vim's Core Functionality. And, that many of the plugins I had installed just re-implemented core Vim features in slightly different ways.https://www.reddit.com/r/vim/comments/16cdbyd/comment/jziruaw/So, I got myself used to the native Vim way of doing things, and dumped all of the plugins one by one. And now, I just open Vim and get work done with very little left to tweak in a streamlined vimrc.
Advanced Programming in the Unix Environment
Week 5: The Editor
In this video lecture, we look at the required feature for a full-fledged programmer's editor and illustrate some of the core functionality by example of vim(1). This includes basic motion commands, setting and moving to markers, using folds, and the use of the ':make' and quick fix lists to address compiler errors efficiently.
(Don't worry, we'll talk about ed(1) later.)
@mms Though I'm biased since I was a tech reviewer on Practical Vim, I'd still put it as the best #vim book out there. Even when weighed against Modern Vim (the follow-up book by the same author, which I also did technical review for). In the "Not shabby" department, you have the O'Reilly classic "Learning the vi and Vim Editors" (now in its 8th Edition, IIUC) which is pretty solid. There are a couple others in the market, but I've found most of them lacking in content, depth, or editing.
Why do #vim users tend to use gd for go to definition when using LSP, when c-] (or g]) is a standard go to for ctags?
I there a good book on #vim script 9? The "learn vim scrpt the hard way" assumes vim 7, and it seem script 9 is quite of a different beast.
Although familiarity with usual vim still comes in handy on the school computer 😅