These are public posts tagged with #vim. You can interact with them if you have an account anywhere in the fediverse.
Let's Learn Linux: Basic file editing
IMO if any programming language needs a specific IDE, someone has made a terrible mistake.
The best IDE is the Unix (#GnuLinux) shell and all the workflow tools available there, with a powerful *general-purpose* programmer's editor like #Vim or #Emacs.
Because programming typically involves writing *many* different languages in a single project. So we need the powerful shell and editor that has a huge community contributing features regardless of what language I'm editing.
@ploum pour ma config sway ergol elle est ici : https://github.com/vjousse/dotfiles/blob/master/sway/ergol-shortcuts incluse ici : https://github.com/vjousse/dotfiles/blob/master/sway/config#L75
Pour #vim tout est ici : https://github.com/vjousse/dotfiles/blob/master/nvim-lazy/lua/core/keymaps.lua#L9
My very own dotfiles (sway, neovim, zsh, wezterm).…
GitHubIt's been a long time since I havent posted a #FollowFriday
Here it goes !
#mechanicalKeyboards
@keyboards
@keyboardkit
@KeyboardMaestro
#Ink #art #sketch #pen #FountainPens
@pbmoj
@jimp
@Autumn
@jezlyn
#vim #neovim
@aerique
@NebulaTide
The more I think about it, the more it seems to me that in this day and age with all the modern threats having a text editor that is capable to not only connect to the Internet, but also install some code packages from repositories (and probably do dependency resolving) is a recipe to catastrophe. Sooner or later.
It's probably one thing when you use a curated list of half a dozen addons that you can even personally peruse (or even contribute to). It's a whole other thing when you use some huge "distro" with probably hundreds of packages that also receive constant updates you cannot possibly control.
It's mostly about #Emacs, of course, but #vim is fully capable of it too. I won't even mention the likes of #VSCode.
We had a fair share of supply chain attacks in the recent years (npm, pip, even xz in some way). No reason to think no one's gonna use this channel of attack.
Maybe it's just my fibs. But there is some uneasy feeling about the fact that you edit, perhaps, extremely private, personal or sensitive texts while your editor runs some background code doing who knows what. It's one thing to trust people who wrote vim or Emacs and a whole other thing to trust a hundred other unknown parties at the same time.
Great suggestion by @gjherbiet: Binding the up and down arrow keys in Vim to gk and gj to move up and down a _display_ line.
In other words, when you have line wrapping enabled (:set wrap) and a single line in the file spans across multiple lines in your terminal, the up and down keys will now move based on the lines in your terminal instead of the lines in the file.
https://mamot.fr/@gjherbiet/114536390274795464
Stealing this for my dotfiles.
https://codeberg.org/scy/dotfiles/commit/d1e5cd95e86471e8faeb9e1517a9ad80fd538327
@adele@social.pollux.casa ˋgjˋ and ˋgkˋ allow you to…
Mamot - Le Mastodon de La Quadrature du NetIf you're interested in #retrocomputing I've been experimenting with running my #RaspberryPi 3 as a console only (terminal) system to do modern work.
Browsing the web is possible with elinks, and I'm exploring different editors than just #vim including #micro which has a modern feel.
I'm able to write with markdown and view high quality PDF output (at the frame buffer) just like I normally would.
Do you know why most sysadmins & experienced DevOps folks like to use #Vim ? It's because learning all of Vim's (A-Z) commands actually grants the user temporary telepathic abilities. You see it all the time. All hardcore Vim users, like those sysadmins, often seem to anticipate your needs before you even type them. They can practically fix server /cloud issues by editing text config files or deploy Ansible playbook before they even happen! Vim gives them superpower. I have spoken #unix #linux
If you ever accidentally end up inside vi or vim or neovim by reading some tutorials online, you can quit it by pressing Escape, colon ( : ), q (q), bang (!) and pressing return. It is simple as that. Modern version of VIM even tells you that on welcome screen. No need to panic.