The rootwork v0.2 blog posted about the author's journey through text editors, from classics such as vi(m) and Emacs to tools I've never heard of. They explain what they use the editors for and why.
Well, with 100 million more users, we had to expect a lot more influx of social media farmers.
It is a fortunate/unfortunate thing: #ActivityPub is becoming a very large mass, thereby attracting ever more attention both good and bad.
But as its mass approaches ∞, more and more people will have the ability to block/opt-out of everything outside their chosen community, and to migrate.
We should build a #VI-centric ActivityPub instance with @chris, maybe a Diaspora or something.
@spinningthoughts Thanks. Yep, figured it out about 10 mins after posting that, despite Google not being any help at all. "Navigation mode" is the term. I clicked outside the text and was like g h constantly and nothing. Then I learned you can press esc while typing and get into this diff mode. g h again did absolutely nothing. Until I realised that Go Home took me to where I was already and that's why it "did nothing". Look at #Logseq trying to be #vi. Huh. Thanks again though!
10 Things You Probably Didn’t Know You Could do With Nano Editor
OK, you probably do know at least one or two of these, but I’ve added the auto backup, line numbers, mouse support, and scroll bar to an alias for every time I start up nano.
At work I have to do a lot of development in an on browser based IDE, which means no nice #emacs movement shortcuts like I'm used to, and moving around the code is painfully slow. The IDE does support #vi movements though, which I've been trying as a 'better than nothing' solution, and yeah, it's still hard. I don't think I'll ever get used to the logic of: if "h" is left/back, then "j" is down, and not up. Arghhh.
@hl Not that it will help but the logic was that C-h was backspace so h moves left and C-j was linefeed so j moves down. Doesn't, of course, explain k and l... 🤪 #emacs#vi
Ouch ! A lot of people actually tend to suggest that also, while I only tried vim once, I just uninstalled it after I had to google “how to exit vim” :| ! It was way to much of a hassle to just edit text :/. But as I read above, and as you said, just learning the basic stuff is enough to begin to like it and get comfortable.
vi and vim take a little getting used to. There’s no shame in needing a cheatsheet; I used one when I was getting used to it (and the first time I had to use it in an emergency, I was looking up what I needed pretty much every minute). This looks like it might have something useful.
Ultimately, what got me used to vi was using it every day to write blog entries (because, at the time, it was still hand-crafted HTML). I just had to use it a little every day.
I think it would be helpful if you used vi a little bit to get used to how it feels. It couldn’t hurt to use Micro for a week, also, for the same reason. There’s no rush, there’s no deadline, give yourself a week of each to play around with them.
As for updating the keybindings, I don’t think it’s a good idea, because the minute you find yourself on a system that doesn’t have them installed you’re back to square one. And, if you’re in the middle of fixing something you probably won’t have time to import them (and you may not even be able to, depending on what’s wrong).
…doesn’t nano still have the menu bar at the bottom by default? I know pico (its predecessor) used to.
The #hacker/detective in #MurderAtTheEndOfTheWorld tested to see if another person was a hacker by asking them if they preferred #emacs or #vi. Apparently any hacker would have an uncontrollable reaction to that question.
This might sound silly, but I installed virt-manager to make things a little easier when using qemu, then created a new virtual machine with debian 12 on it... then installed qemu on that.
The actual reason for this is to make github account separation a little easier...
If you get virt-manager set up properly, it definitely makes using qemu easier, though. I practically just had to tell it to make a new virtual machine using this iso with this much memory and this big of a hard drive, and it was right at the debian install screen. (Set it up with xfce...).
Main tricky parts were that I had to install libvirt first, make myself a member of the libvirt user group, enable the service, and install dnsmasq. Not great, but could've been worse...
Used debian on the virtual box just for a little variety. I like to keep my hand in on different distributions a bit.
Been on BlueSky a few months and only have 16 posts. Someone’s already called me a dipshit.
Been on Mastodon well over a year and have yet to be called a dipshit.
I have however been called an ableist asshole for commenting on someone’s ADHD rant declaring his hostility for neurotypical people ruining his life, despite that I also have ADHD and grew up being told my only problem was my poor personal habits when I tried to get help.🤦♂️
The ablest asshole comment was a lot more insulting given the context, but I think I prefer that as at least I know why someone’s so pissed… and it’s kinda funny.
Vi is a text editor with no menu/mouse, so everything is done by keystrokes. Keypresses are commands, so typing "hi" triggers the 'h' command (Move Left) and the 'i' command (Insert Text).
People who don't know Vi end up typing strange things when trying to issue commands, e.g. to quit Vi to go back to a program with which they are more familiar.
Your bio said "IT guy" so you'd be expected to know this.
Oh, on est 2 à pas s'être décidés à migrer de #tcsh....?
Bon après si je pouvais scripter le velouté ce serait en #bash. C'est que pour la cuisine interactive que j'ai pas le courage de recoder mes p'tits raccourcis qui vont bien pour sortir la poêle en fonte ou éditer le réglage du four en #vi.
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.
[Q] Terminal navigation and Editors
Hi everyone :)...