Classic polls: vi or emacs?

Submitted by Anonymous on Thu 18 Jan 2007

Tags: , , ,

 

The vi family (vi, vim, elvis, etc)  <-> 67%888 votes
The emacs family  <-> 16%218 votes
Something else  <-> 15%209 votes
Total 1315 votes

Posted by Steve (80.68.xx.xx) on Thu 18 Jan 2007 at 16:00
[ Send Message | View Steve's Scratchpad | View Weblogs ]

For serious editing, (working on code, writing articles, etc), I use emacs exclusively.

But I do use vim as my editor when composing/replying to mail within mutt.

Steve

[ Parent ]

Posted by Arthur (66.28.xx.xx) on Fri 19 Jan 2007 at 04:11
[ Send Message | View Weblogs ]
I spend my days flipping between XEmacs and vim. Some tasks are always in one or the other, most tasks end up in one or the other essentially arbitrarily.

[ Parent ]

Posted by chris (213.187.xx.xx) on Fri 19 Jan 2007 at 06:16
[ Send Message ]
All coding and developing I use emacs. System admin changes within the changecontrolled config files on my local box also in emacs. But - if I remote shell in to make a quick admin change - then that will tend to be vi.

However - emacs I can use quite a lot of it - vi - just the basics - so for this poll - emacs.

[ Parent ]

Posted by Anonymous (128.130.xx.xx) on Fri 19 Jan 2007 at 11:52
Help! I'm afraid I've caught an inferiority complex.

[This comment was written using nano.]

[ Parent ]

Posted by ajt (195.112.xx.xx) on Sat 20 Jan 2007 at 12:10
[ Send Message | View Weblogs ]
I don't care, I use nano and I'm proud of it!

Vi and emacs are powerful complex tools that are evil to learn. I have used emacs in the past and at work on our AIX antiques I use vi but on any half-modern system I use nano. I took the path of least resistance, learning nano was easy and it does what I want.

I don't doubt that Vi or emacs are powerful and may offer more than nano but I don't need a text editor that much; nano is good enough for config files, xhtml, css, Perl and emails.

--
"It's Not Magic, It's Work"
Adam

[ Parent ]

Posted by JulienV (90.6.xx.xx) on Sun 21 Jan 2007 at 10:07
[ Send Message | View Weblogs ]
I do use nano as well for configuration files editing etc.

I tend to use it also for HTML/CSS/JavaScript, but generally prefer a GUI like gedit which does what everything I need.

I wouldn't mind using emacs or vi but simply do not need their advanced features.

Cheers,
Julien

[ Parent ]

Posted by redbeard (64.218.xx.xx) on Fri 19 Jan 2007 at 20:57
[ Send Message | View redbeard's Scratchpad | View Weblogs ]
I started using JED on DOS ages and ages ago, with the Emacs bindings. I chose it because it was cross platform, small, had a C-like scripting language (I was maintaining DOS-based C programs at the time), and had Emacs bindings. I didn't want to use Emacs (too big for me) but I was used to an commercial editor called Epsilon that had Emacs bindings. And I found JED. Haven't left it since. I've used it on DOS, OS/2, Windows (3.1, 95, 98, 2000, XP) and Linux. I even carry it around on my USB key for when I have to edit stuff in Windows.

Michael

[ Parent ]

Posted by Anonymous (68.186.xx.xx) on Sat 20 Jan 2007 at 03:16
I have to Pico now ?

[ Parent ]

Posted by kamaraju (128.253.xx.xx) on Mon 22 Jan 2007 at 19:37
[ Send Message ]
For things involving text only, I use vim or gvim.

For things involving typesetting, I use texmacs (which has a lot of key bindings from emacs).

So, strictly speaking, I think I belong to all three choices but I have chosen "The vi family" as my answer!

[ Parent ]

Posted by Anonymous (81.224.xx.xx) on Mon 22 Jan 2007 at 23:01
Serious work, always Emacs.
That's becouse it is so easy to teach it to do the stuff my way. But usally I don't need to teach it anything. And it suprices me with easy to use integrations (like editing files through ssh or ftp like it are local files, editing files in archives, smooth integration with CVS et al. etc). If I only need tp change one line or so in a config file, I usally use a simple, but fast starting, no good for nothing else editor, like vim or (vi).
Nano is not for me, at all.

But as allways. YMMV.

[ Parent ]

Posted by Anonymous (128.193.xx.xx) on Wed 24 Jan 2007 at 02:14
Let's not forget ne, "the nice editor". It truly lives up to its name.

[ Parent ]

Posted by Anonymous (67.86.xx.xx) on Wed 24 Jan 2007 at 04:06
Emacs. And when it's just for editing config files on a remote overworked machine, zile (a tiny and fast emacs-alike written in C).

I've learned and used vi/vim in the past, but even after getting pretty well accustomed to it, I still found myself sometimes trashing files by accidentally hitting a series of commands (in command mode) when I thought I was in the regular typing mode.

Also, never actually figured out how to handle multiple buffers in vim. In Emacs it's wonderfully easy.

[ Parent ]

Posted by Anonymous (82.181.xx.xx) on Wed 24 Jan 2007 at 10:58
It's funny how the graph shows that vi won, but mostly the emacs guys cared of commenting :)

--
Vi user.

[ Parent ]

Posted by Anonymous (69.205.xx.xx) on Sat 27 Jan 2007 at 23:55
ibecause most of us vi people hate using editors that dont have vi commands :wq

:-)

[ Parent ]

Posted by Anonymous (89.102.xx.xx) on Wed 24 Jan 2007 at 18:29
vim for administration, for everything else emacs.

[ Parent ]

Posted by Anonymous (71.135.xx.xx) on Wed 24 Jan 2007 at 23:09
vi itself is small, is available in one form or another in the command-line on liveCds, and is fast as blazes for quick abcd's! no compilation either, and better than the 'ol one-liner 'ed'

[ Parent ]

Posted by Anonymous (71.241.xx.xx) on Thu 25 Jan 2007 at 04:44
MC and MCEDIT.

[ Parent ]

Posted by Anonymous (213.164.xx.xx) on Thu 25 Jan 2007 at 10:36
Does it support utf-8 yet?

[ Parent ]

Posted by nycace36 (71.135.xx.xx) on Thu 25 Jan 2007 at 07:19
[ Send Message | View Weblogs ]
Agree pretty much with #6-#8, #10 and #14-#16.
vi/vim/elvis for quickness and brevity, emacs for thoroughness and full-featuredness, MCEDIT when using the ncursive MC, pico or nano for more limited easy-to-use editing at the CLI.
MCEDIT reminds me of the old DOS's EDIT (based upon QBASIC).
pico reminds me of the "original" 3rd-party wordprocessor for DOS, WordStar.
Now in the X11-world, there are all the _edit's such as nedit, kedit, gedit... as well as gvim, xemacs, ...etcetera.
nycace36

[ Parent ]

Posted by lpenz (201.15.xx.xx) on Thu 25 Jan 2007 at 13:44
[ Send Message ]
For quick editing, VIM.
For serious work, VIM.
Seriously, VIM got all I need for code editing and more. Besides, it's a productivity dream for touch typists.

[ Parent ]

Posted by Anonymous (213.224.xx.xx) on Thu 25 Jan 2007 at 19:01
I see no reason to learn Emacs. I can use graphical office suites, Eclipse, and Vim. Vi is standard on all Unixes, so wanting Emacs means a lot of hassle to get started I think, and the other products are quite strong for duties other than configuration file editing.

Having said this, I am interested in a poll concerning LaTeX vs DocBook... (Seems like DocBook is getting more of a standard nowadays).

[ Parent ]

Posted by andreas (62.38.xx.xx) on Thu 25 Jan 2007 at 21:59
[ Send Message ]
vim because exist everywhere, is the one i learned first and it really powerfull

[ Parent ]

Posted by Anonymous (202.108.xx.xx) on Fri 26 Jan 2007 at 02:34
me too. and I always mistype 'emacs', when I want to have a try.

[ Parent ]

Posted by JohnMG (67.86.xx.xx) on Sat 27 Jan 2007 at 21:21
[ Send Message ]

Having said this, I am interested in a poll concerning LaTeX vs DocBook... (Seems like DocBook is getting more of a standard nowadays).

Oooh. Sounds like an interesting poll. I use Texinfo, so would like to see that in there as well (Plain TeX too!). As for DocBook, I'm not <diagnosis>crazy</diagnosis> about <quantity>all</quantity> those <expletive>darn</expletive> <radians>angle</radians> <delimiter>brackets</delimiter>. Seems way too verbose to read and write in my editor. For those who've never used it, Texinfo source docs look like this.

[ Parent ]

Posted by kiguar (83.131.xx.xx) on Fri 26 Jan 2007 at 09:53
[ Send Message ]
Emacs whenever it's possible (available on the machine).
In the case of emergency, it's still necessary to know how to use Vi.

[ Parent ]

Posted by yogi4yu (202.141.xx.xx) on Sat 27 Jan 2007 at 14:34
[ Send Message ]
vi rules
vim rocks
--
There is no point in knocking the "closed Windows" when the door is "Open". Open your eyes, use open source software.

PLEASE VISIT & REGISTER @ "www.ossrc.org.in "

Regards,
Yogesh

[ Parent ]

Posted by naldy (222.124.xx.xx) on Sat 27 Jan 2007 at 15:30
[ Send Message | View naldy's Scratchpad | View Weblogs ]
I usually use vi for text editing especially in console.
It's great.

[ Parent ]

User Login

Username:

Password:

[ Advanced Login ]

Register Account

Quick Site Search

Poll Archive

View Prior Polls