StarDestroyer.Net BBS

Let's see how SD.net stands on the issue!

I vote: neither. It's like trying to decide between a Ford Model T and an old Mack truck. I prefer almost any windowized editor (gedit, kedit, windows notepad, whatever). For old-style editors, pico and dos edit are the least bad (i've never tried joe, so I can't say about that).

ed is, of course, a 1901 Oldsmobile, complete with tiller. Pico is more a 1950's Ford Fairlane. Edit is a Henry J (1950's compact, cute, worked well, but didn't have a trunk). Notepad is sort of a grungy 1972 Dodge Colt. gedit and kedit are late-1970's-era Toyota Corolla and Honda Civic, respectively.

I started with vim, tried emacs, went back to vim for some reason. (I use the arrows in edit mode, so vi standard is still a problem for me.)

Pico is fine for regular text editing, but horrid for programming.

I do a lot of programming on remote Unix machines. I use the university's computer science Unix systems to do most of my assignments, so my code is up to date no matter where I'm physically editing from. So using terminal-based editors are a necessity.

I've never run into a problem with pico, to be honest.

I like Notepad

as much as i've worked in linux i've never had the pleasure of using either. I always used openoffice for everything and that seems to work just fine.

I never got used to either, but I use pico.

ggs wrote:I like Notepad

-grabs his bat-

Blah, it's all about emacs. Anyone who does programming should look into emacs simply for the formatting and code highlighting abilities (mostly with XEmacs). This is expecially true when programming in Lisp/Scheme since I've never seen any editor do a better job at dealing with Lisp than emacs (helps that emacs is written in Lisp).

That said, I normally use JEdit these days since it has the nice code formatting like Emacs, but also tons of plugins for all kinds of development task such as function/member name completion, source control support, class browsing, and all the other goodies that make life SO much easier while dealing with large amounts of code.

Miles Teg

Vi(m). HJKL rules.

Vim also has formatting and highlighting.

I have never used Pico, though I did use nano for awhile- vim was the first editor I used, then switched to nano when using LFS, then emacs. When I switched to Debian I used gedit, then I switched to gvim, then just straight vim, due to the pointlessness of the GUI, and the fact that I can use GNU screen with console apps.

Besides, I've heard about problems with RSI due to using emacs.

Terr Fangbite wrote:as much as i've worked in linux i've never had the pleasure of using either. I always used openoffice for everything and that seems to work just fine.

If you need to do something over a low-bandwidth SSH connection or on a machine whose graphics driver you've fucked up during an upgrade of some sort, you need a barebones text editor like vi. I use vi all the time.

Also Emacs takes a couple seconds longer to load, and I'm rather impatient. For something as lightweight as a text editor, I expect it to load almost instantly to allow me to change a few lines and exit.

I used vi to write C programs on Sun OS and SINIX machines in the late eighties.

I don't particularily like either (I use NEdit for most of my heavy tasks and nano for those situations where I need to work in console mode.) However, given the choice between the two, I'd chose vi. Better to have a small, unobtrusive program that I don't like than a bloated monstrosity of a program that I don't like.

I can't stand vi, and I've never used emacs so I'm shooting for the neither category until I get a chance to use emacs.

Pico! I know people who use vi, and frankly, they're insane. Emacs in a GUI shell is pretty nice, but not plain old console-window/terminal based emacs.

vi for sure, but neither is really useful for any serious amount of editing. Sure, emacs is highly customizable, but in a useless way - everyone customizes it differently, so you can't do anything on someone else's machine! Pico was ok, but I disqualify it since it isn't installed with the basic OS installation

Emacs is just plain awful.

vi just... works. It can annoy the hell out of you if you're not used to its totally fucked-up usage of the keyboard as well as the edit modes, but once you get used to that they sort of become transparent.

EMACS is basically the kitchen sink (isn't that in the code somewhere?) of editors. I've never really had much use for it, and anyway, some versions of vim include syntax highlighting.