[juneau-lug] Re: Editors
- From: Matt Heavner <matt@xxxxxxxxxxxxxxxxxxxxx>
- To: juneau-lug@xxxxxxxxxxxxx
- Date: Tue, 31 Jan 2006 22:07:27 -0900
I think you have to know some vi. But if you have to edit alot, you
should learn emacs. I use emacs for "real editing." My uses include
LaTeX (manuscripts, presentations, and posters; physics homework--I'm
sure there is a vi way for adding macros (maybe you use m4 in combo
with vi?), but I like having the entire greek alphabet at two key
strokes away) perl and python code (the modes within emacs are great);
matlab and idl modes; wiki mode, etc.. etc.. And in my experience,
the emacs calc-mode is amazingly, insanely great--it is hands down the
best calculator I've ever used. RPN, symbolic manipulation, yanking
and pasting from LaTeX buffers, column and matrix math, and that is
really just the beginning.
I use vi almost daily as well, for a quick config file edit or
something similar.
So I'd say some time on vi, and more time on emacs...
Matt
On 1/31/06, deadcats <deadcats@xxxxxxxxx> wrote:
> Being relatively new to the shell, I prefer the enchanced vim that SuSE
> offers--and Gawd forgive the person mentioning Edlin...may it rot in hade=
s.
> ;)
> -dc
>
> On 1/31/06, Stephen E. Bodnar <sbodnar@xxxxxxx> wrote:
> >
> > If I'm out in the shell somewhere, I always use vi. Except that
> > linux distributions will often substitute an enhanced version of vi.
> >
> > But I agree with Jacob. Nedit is my favorite in a GUI.
> >
> > Stephen
> >
> > >I like nano. It was a free as in speech rewrite of pico. But Larry i=
s
> > >probably right. Vi is almost a standard on *nix machines. That being
> > >said my favorite GUI text editor is nedit.
> > >
> > >Talley family wrote:
> > >
> > >>But if you are bouncing around on different Linux/Unix hosts,
> > >>seems to me that vi or ed are the only things you can count
> > >>on finding....
> > >>
> > >>For that reason I think a student should learn vi.
> > >>
> > >>Eat it, its good for you.
> > >>
> > >>Larry
> > >>
> > >>
> > >>
> > >>>-----Original Message-----
> > >>>From: juneau-lug-bounce@xxxxxxxxxxxxx
> > >>>[mailto:juneau-lug-bounce@xxxxxxxxxxxxx] On Behalf Of Kevin Miller
> > >>>Sent: Tuesday, January 31, 2006 6:10 PM
> > >>>To: juneau-lug@xxxxxxxxxxxxx
> > >>>Subject: [juneau-lug] Re: Editors
> > >>>
> > >>>
> > >>>Eric M. Niewoehner wrote:
> > >>>
> > >>>
> > >>>>I am about to teach a section on editors and I was curious
> > >>>>
> > >>>>
> > >>>as to which
> > >>>
> > >>>
> > >>>>text editor you all preferred. While I am on my local
> > >>>>
> > >>>>
> > >>>workstation, I
> > >>>
> > >>>
> > >>>>always use the GUI, but shell sessions require a plain-text
> > >>>>
> > >>>>
> > >>>editor. The
> > >>>
> > >>>
> > >>>>author of the text I am using is keen on vi.
> > >>>>
> > >>>>
> > >>>If I'm in KDE I usually use Kate. If at the CLI, I like the midnigh=
t
> > >>>commander editor (if mc is installed). Otherwise I flip/flop
> > >>>between vi
> > >>>and pico. Not overly fluent in vi, and not overly impressed
> > >>>with pico.
> > >>>
> > >>>Way back in the DOS days I used to use an editor called TED (Tiny
> > >>>EDitor) which was a PC Mag. utility. Small, fast, and beat the pant=
s
> > >>>off edlin. The mc editor is similar. Best thing since sliced beer.
> > >>>Um, bottled bread. Er, whatever.
> > >>>
> > >>>If I'm doing more than just a quick edit of a .conf file the
> > >>>color and
> > >>>nesting in Kate is quite handy. Don't do much scripting or
> > >>>programming
> > >>>so my needs are pretty humble...
> > >>>
> > >>>...Kevin
> > >>>--
> > >>>Kevin Miller
> > >>>http://www.alaska.net/~atftb
> > >>>Juneau, Alaska
> > > >>Registered Linux User No: 307357
--
| Matt Heavner, Assistant Professor of Physics
| University of Alaska Southeast
| 11120 Glacier Highway, Juneau, AK 99801
| Phone: (907) 796-6403 Fax: (907) 796-6406
| If Heisenberg was uncertain, why are you so sure?
------------------------------------
This is the Juneau-LUG mailing list.
To unsubscribe, send an e-mail to juneau-lug-request@xxxxxxxxxxxxx with the
word unsubscribe in the subject header.
Other related posts:
