Vi vs Emacs: Discuss
-
Vim IDE? Manwhatareyousmokingandcanihavesomeplease
-
Vim: IsitanIDE? Maybeonoppositeday.
-
Of course it is. It's got code completion, code navigation, integrated help (shift-K in command mode opens the relevant man page, perldoc, etc. Probably decides based on active hightlighting mode). Can invoke your compiler and is reasonable at finding error locations (:make, not to be condused with :!make).
There are probably plugins for boilerplate snippets, but I've never bothered to look.
-
I'm going to have that quoted out of context for the rest of this thread, aren't I?
well if you're doing that may i fan the flames higher and also point out that i also said
VS is a terrible IDE
?
-
I couldn't find any way to download a Nuget package in Verily It's Maintainedbyidiotsthatitsanide, so VS wins again
-
I'm going to have that quoted out of context for the rest of this thread, aren't I?
well if you're doing that may i fan the flames higher and also point out that i also said
VS is a terrible IDE
?
But you were talking about Go in the same sentence, so were obviously not in a stable frame of mind
-
I'm going to have that quoted out of context for the rest of this thread, aren't I?
well if you're doing that may i fan the flames higher and also point out that i also said
?
You said no such thing. Discourse confirms it.
-
i.... but.....what?
/me sits down slowly and starts muttering
it puts the lotion on its face....it puts the lotion on its face....it puts the lotion on its face....it puts the lotion on its face....
<YOU BROKE ACCALI! YOU BASTARDS! ;-)
-
Then we're agreed
That's not how to troll.
I thought the vim acronym made that clear: Vim Is Mostlyterribleandnotanide
This is trolling the right way.
-
I'm scared to fully troll @accalia in case she sets her army of foxes and furrys on me
-
I'm scared to fully troll @accalia in case she sets her army of foxes and furrys on me
hmm... i'd have to get @RaceProUK to let me borrow his army to get both groups to attack.
i don't think he'd agree so you're probably safe. ;-)
-
-
Isn't @RaceProUK your lieutenant?
-
-
-
Yes - masochist is what I meant.
-
vim isn't that bad - it's just not something a sane person would use as an IDE.
-
I did learn a bit of vim several years back. It seemed OK for the case when you're constrained to a CLI and need advanced text editing, but when running it through PuTTy on a computer with Office and Notepad++ installed, it seemed pretty pointless
-
vim isn't that bad - it's just not something a sane person would use
Genocide really isn't a bad thing, it's just not something a sane person would do.
-
vim isn't that bad - it's just not something a sane person would use as an IDE.
/me waves
Hi! that's me! i use it for my PHP work and it works just fine than you very much. syntax hightlighting LINT checks, on demand documentation, intelligent code completetion, and an interface that says "i'm here if you need me but other than that i'm going to get out of your way and let you work"
i flipping love it.
I also like to pretend i'm a fox for the lulz so there may be something wrong with my brain...
-
-
-
may?
what? May's hereβ½
Of course she visits on the day i forgot my pokedex so we can't battle....
-
-
-
when running it through PuTTy on a computer with Office and Notepad++ installed, it seemed pretty pointless
Quite. Occasionally it's faster to make a quick edit than it is to copy the file back to Windows and chuck it in NP++ or Eclipse, but otherwise I agree.
-
-
and an interface that says "i'm here if you need me but other than that i'm going to get out of your way and let you work"
Wait... it has an interface?
-
That recursive backronym suggests otherwise.
many sane things have recursive acronyms...
Wait... it has an interface?
it does! a very nice one too!
-
-
Used mostly for code cleanup.
-
I find vim highlighting of PHP can be terribly slow. May be something to do with our multiple-thousand-line files.
IMNSHO, however, there are very few reasons to have a file that long.
-
I find vim highlighting of PHP can be terribly slow. May be something to do with our multiple-thousand-line files.
depends on the file, but over 1k to 1.5k LOC things get problematic on more than one front
IMNSHO, however, there are very few reasons to have a file that long.
i'd argue there are exactly 0 valid reasons myself.
-
Occasionally it's faster to make a quick edit than it is to copy the file back to Windows and chuck it in NP++ or Eclipse
Not once you factor in the time to google "how to exit vim"
-
ESC
:q!
ENTER
-
If I'm in vim it's because I'm editing something - best not go for
q!
there :)
-
Not once you factor in the time to google "how to exit vim"
Press Ctrl + C (the usual shortcut for "get me the fuck out of this" on Unix/Linux) and it reminds you the correct command.
-
well, fair enough.
force quit (lose edits)
ESC:q!
ENTERquit, but remind me if i havent saved
ESC:q
ENTERSave:
ESC:w
ENTERsave even if file is marked readonly (will only work if you are owner of file)
ESC:w!
ENTERsave and quit
ESC:wq
ENTER
-
Not once you factor in the time to google "how to exit vim"
If it's really your first time using vim, you should follow the advice given on the startup screen and type
:help
. If you've used vim before and still don't know how to exit, you have bigger problems than having to google it.
-
like the fact you're willingly using vim a second time?
-
If you unexpectedly land in vim, it is probably some tool that provided a template for you to fill in, so the start screen (with :help and :q and the poor children) is not shown.
-
The evil ideas thread is over there.
-
you should follow the advice given on the startup screen and type :help.
you get that screen if you enter
vim
as the command, you don't get it forvim filename
-
There are plenty of tools that do this. Some of them because the configured editor resolves to
vi
by default, which usually aliases to some build of vim, but some tools throw you in vim even if it's not your configured editor.
-
Some of them because the configured editor resolves to vi by default,
i'm glad that in ubuntu the default is
nano
and that that is a per-user configurable setting.....nano has it's own problems but it is easier to escape if one ends up in it unexpectedly
-
In my experience, CentOS is the usual culprit for unexpectedly tossing you into vim. Eventually I learned a few basic commands but getting a text editor without an obvious "quit" function chucked in your face is pretty scary.
-
you can easily quit by opening a new terminal and typing rm -r /*
-
It's per-session actually - it uses the values of the VISUAL (when an X display is available) and EDITOR (always) environment variables.
vi
is the default if both of those are unset.Ubuntu's move to set nano by default is probably a wise one.
-
It's per-session actually - it uses the values of the VISUAL (when an X display is available) and EDITOR (always) environment variables. vi is the default if both of those are unset.
. i knew that already but was trying to keep discussion simplified... ;-)
-
I will just leave this here.