Just use sublime text (anti-vim rant)
-
crazy obscure just-woke-up-from-the-80ies collect-pee-in-glass-bottles style of coding
Looks like my instinct of "save in my Watch-Later list so I can appreciate the insanity later" instinct was dead-on.
-
fun fact, when i switch from linux to windows for about an hour whatever i type gets littered with the occasional ESC:wRETURN sequence.
Which just exits dialogue window (if any), writes ":w" in place of cursor and breaks line. Much less destructive than what happens when you forget to enter insert mode before typing in vim.
-
-
That's not really a fair description of what he was doing, which was customizing the way they're highlighted.
Look, most editors are scriptable now, not just vi. So you can do pretty much anything in any of them.
resurrect linux servers - both professionally and as a hobby.
Who the fuck makes a hobby out of that?
Filed under: that was a rhetorical question, please
-
Who the fuck makes a hobby out of that?
Some people just want to see the servers burn.
-
Look, most editors are scriptable now, not just vi. So you can do pretty much anything in any of them.
I'm not sure I'd agree on how scriptable editors are generally, but your statement is agreeing with my larger point, so thanks.
-
Some people just want to see the servers burn.
and then putting the fires out and resurecting them.
so we can set them on fire again. :-D
-
@@ does or what :v/\v does
I have no idea what those do and I'm using vim just fine. I may not be the most efficient, and I might not use hjkl, but when I need it to do awesome stuff I can.
-
s/vim/notepad.exe/g and it's still applicable.
-
Since when does notepad.exe do awesome stuff?
-
@gaska must have visited NotepadConf.
-
-
i've done that too. [forget to enter insert mode before typing in vim]
Usually undoable though...
-
Usually undoable though...
almost always, depending on how long you go and what you type before you realize of course. ;-)
-
I've been using vim off and on for years and I have no idea what
@@
does.
-
I've been using vim off and on for years and I have no idea what @@ does.
E748: No previously used register
Well, that's useful... I guess :P
-
I've been using vim off and on for years and I have no idea what
@@
does.
It runs the last used macro another time without having to think which character you assigned it to.
-
Since when does notepad.exe do awesome stuff?
It's not about what notepad.exe can do, but what you can do with notepad.exe. And you can do anything. Being able to type in any letter is text editor equivalent of Turing-completeness.
-
-
If you go to www.vim.org, the first photo you will see is:
So, Vim is also able to be used as a drill?
-
Vim is also able to be used as a drill?
It is, but you'll find that you slip slightly and what happens is that the wall you're drilling suddenly has 17 holes in it, before disappearing for good before you can figure out whatever the key combination for stop is.
-
It is, but you'll find that you slip slightly and what happens is that the wall you're drilling suddenly has 17 holes in it, before disappearing for good before you can figure out whatever the key combination for stop is.
And that causes you to lose networking, so now you need Vim skills to get it back online because that is why you learned Vim in the first place and you are using the one obscure distro that does not have Nano installed by default and you never bothered to type:
sudo apt-get install nano
...or whatever your package manager of choice is?
-
:help iccf
-
TIL vim people are very concerned with how small their .vimrc is. Settle down guys, I believe you, no need to wave it around.
-
-
-
It is, but you'll find that you slip slightly and what happens is that the wall you're drilling suddenly has 17 holes in it, before disappearing for good before you can figure out whatever the key combination for stop is.
That's a feature.
-
Also, I cannot remember the last time I had a server so ■■■■■■■-ed that networking was not working...but did not require recovering from backup. It is a pretty narrow use-case where Vim skills are necessary.
"So, we had an eight hour outage last night. What happened?"
"A switch failed and I needed to move the management network connection from eth3 to eth5. It was either go in through the remote console and use vi to edit two files in /etc/sysconfig or reinstall the entire thing from scratch."
"Sounds like you did what you had to do. On to the next item..."
-
Yeah, I would just use Nano for that. Beyond that though, it would be pretty simple to just Google the little bit you need to know if Nano is not available.
-
It was either go in through the remote console and use vi to edit two files in /etc/sysconfig
Which took 8 hours?
;)
-
Which took 8 hours?
...and borked it even worse because Vim is as arcane as the necronomicon.
-
Even "ed" or "cat" would do the job there. I only said that because:
a) This is the wrong forum for reasoned, sensible agreement on minor differences of opinion, and
b) The last time I had to restore a server from its backup, I learned far more than I ever wanted to know about the level of professionalism exhibited at my workplace, and I still have horrific flashbacks to it.
-
Vi is arcane.
vim is fine. Just press i before you start typing, then Esc :w to save :q to quit or :q! to quit without saving. Undo even works correctly (unlike vi)
-
Ah, this brings bad memories of when I had to use vi on AIX running on some IBM Power machinery.
Arrows? We don't do those.
Backspace? The cursor just moves to the left and you have to overwrite what was there.
Visual mode? Nope, that would be too straining even though our hardware can hit a few jiggaflops.
-
-
compromise?
-
Definitely recommended, even though it misses a few niche things.
-
-
That's what
:quitwithextremeprejudice!!1eleven
is for.Or just use
:qa!
.
-
Or unplug the machine entirely. If it's running vi, it's probably not worth keeping turned on.
-
Then this happens:
( 0:31, and cheesy as Belgium )
-
And yet, you are supposed to use visudo to edit the sudoers file.
Thankfully, it respects EDITOR
-
-
And yet, you are supposed to use visudo to edit the sudoers file.
Thankfully, it respects EDITOR
Shit. I forgot about that one as I have not deployed a CentOS machine for a while.
-
Am I wooshing on this or is this just a comment?
-
What does
It stands for "all buffers", and thea
do here?!
will make it ignore any unsaved changes.
-
Just a comment. Last time I had to muck about in the sudoers file was when I was running a CentOS machine. I think that was it anyway.
-
-
I see. I never used more than one buffer, so I didn't know.
-
Am I wooshing on this or is this just a comment?
Oh, maybe a sort of a whoosh? I was the one earlier in the thread that said you would never need to use anything but nano, etc. You gave a solid reason where you have to use Vi in some cases, with no workaround.
I still don't see Vim as being an IDE though.