|
|
| Author |
Message |
veek
|
|
Fav editors
| 
Dec 10 11:24 UTC 2010 |
The thread to discuss your favourite editor and suggest cool tips and
tricks.
I like Kate :p I've used emacs and vi a bit but i flipped for Kate.
Some mornings I'd get up happy thinking I could type in Kate (no
kidding). I liked the color schemes a lot.. she/it made Perl look
beautiful! I'd get a lot of satisfaction from typing 10 lines and
admiring all the lines neatly indented with the curlies just so and
stuff :p I'd never used/seen colors before in an editor! I've always
stuck with vi, and in xterm there's only black b0ring text.
Trouble is, when i bumped into CSS.. I like X11 color-names to my CSS,
unfortunately writing color: AliceBlue; isn't exactly standards
compliant.. so i wanted to continue to type in X11 color but have that
converted for me into #ffff00 crud. I also wanted the color-name to be
commented and to the extreme right.. ouch! not easy to do in Kate!
So i decided to go back to emacs.. which sucks because:
1. I was using XEmacs which is unusually sucky!
2. Hard to configure!
Well.. it's done.. nothing fancy really.. it's just figuring out stuff
in Unix involves shit loads of googleing and reading and ircing and
trying out in vi and a million restarts BECAUSE to do it the right way
(slightly shorter way) would involve learning eLisp! Grr! an obscure
programming language which I have not the slightest! desire to learn..
oh and figuring out how to use the Emacs debugger which is different
from gdb (*grumbles furiously*).
------------------------------------
So, what is your favourite editor, and why? How long have you been
using it for? What editors have you used prior to this one? What
features would you like to see? What irritates you, how do you feel
typing in them??
|
| 32 responses total. |
nharmon
|
|
response 1 of 32:
|
Dec 10 14:24 UTC 2010 |
My favorite editor is jEdit (http://www.jedit.org/), because I can run
it on Linux and Windows, and it has a ton of plug-ins for all kinds of
things, from integrated ssh/scp to syntax checking for different languages.
|
bellstar
|
|
response 2 of 32:
|
Dec 10 14:26 UTC 2010 |
Vim/gVim on UNIX-likes and Windows. SciTE on Windows at times. Notepad++ on
Windows, rarely. NFOPad on Windows, for nfo's. Microsoft Visual Studio
DevEnv's built-in editor(s), whenever I happen to be working on VS projects.
I found Emacs' overhead too much for my purposes many years ago and never
learned to really use it anywhere as fluently as I do vi-clones. At times I
feel an itch to fill that gap but it seems I'll need to get a grasp of at
least some Lisp dialect beforehand (you mentioned that).
I find vi clones--Vim in particular, and nvi when I'm working on some BSD--a
joy to tap away in. And, admittedly, the amentities DevEnv's editors provide,
like IntelliSense, are quite addictive.
|
keesan
|
|
response 3 of 32:
|
Dec 10 17:13 UTC 2010 |
I use JIm's 4K text editor in DOS (or Windows) and pico/nano in linux.
Jim's editor works in Russian, split screen, it prints, etc., and it is
super fast on any PC. He has an older version for 8086 to 386 too.
Written in assembly language over many years.
|
jep
|
|
response 4 of 32:
|
Dec 10 17:27 UTC 2010 |
I'm a vi guy. I use it when I can, and have vi-clone vim on the PCs I
use regularly. The search and replace functionality is unmatched in the
editing world. I very rarely want to use any kind of enhanced text,
like bold or font sizes or colors, so vi does everything I want. I wish
I could use it as the editor in Backtalk, and in Lotus Notes at work.
|
cross
|
|
response 5 of 32:
|
Dec 10 18:17 UTC 2010 |
Acme, sam, wily, TextMate, in that order.
Emacs if I'm programming in Lisp.
Vi if I'm stuck with it (or stuck with a command-line login to Unix).
Ed and "sam -d" for non-interactive, in-place editing of files.
|
bellstar
|
|
response 6 of 32:
|
Dec 10 18:29 UTC 2010 |
I manually construct 9P messages and cat them to acme :-P (just kidding)
|
nharmon
|
|
response 7 of 32:
|
Dec 10 18:55 UTC 2010 |
:P http://xkcd.com/378/
|
cross
|
|
response 8 of 32:
|
Dec 10 19:12 UTC 2010 |
Some brief notes on the development of ed and Unix text editors:
http://cm.bell-labs.com/cm/cs/who/dmr/qed.html
I think it's one of the Salus books that goes into the details of the history
of vi, and other similar editors from that era.
|
tod
|
|
response 9 of 32:
|
Dec 10 19:13 UTC 2010 |
I like VI
For word processing, I like WordPad though would LOVE to use NotePad if I
could get it to wrap appropriately.
|
keesan
|
|
response 10 of 32:
|
Dec 10 20:42 UTC 2010 |
Isn't there a computer software conference some place?
|
kentn
|
|
response 11 of 32:
|
Dec 10 20:52 UTC 2010 |
Can't we link this item?
|
cross
|
|
response 12 of 32:
|
Dec 10 23:06 UTC 2010 |
Linked to systems.
|
remmers
|
|
response 13 of 32:
|
Dec 11 16:52 UTC 2010 |
Mostly I use the response entry form in Backtalk as my text editor.
Just kidding.
For serious editing work in a Unix environment, mostly vim. I've been a
vi user for a quarter of a century; the command keystrokes are hardwired
in my brain now.
For larger projects that involve editing multiple files, I'll sometimes
use emacs, but *ONLY* if vi-emulation is turned on. (See keystrokes
comment above.)
|
veek
|
|
response 14 of 32:
|
Dec 11 17:28 UTC 2010 |
GNU-Emacs is slow! It's slower in many ways than KDE's Kate! With colors
on, if i try to scroll up using C-p (Ctrl p) it pauses every 10 lines
and my CPU usage skyrockets to 90% - and this is on Lenny, which is old
and stable!! But it looks very nice and elegant when you have the Gnome2
color themes turned on. And! you can save/restore desktop using
desktop.el (which I suspect is buggy - i had to edit some statement in
it to get it to work). Emacs also has dired mode :) You can M-x d and
browse your file-system which is nice. It also has image browsing but I
didn't like that much.. All in all, I strongly approve of KDE and Kate
(v 3.xx), unfortunately for all concerned, KDE 4.xx is utterly horrid!
*sigh* I think I should pick more intellectual pursuits.
|
kentn
|
|
response 15 of 32:
|
Dec 11 18:22 UTC 2010 |
I use Vim/gVim as well because I've used vi and vi-work-alikes for
many years now. As bellstar says, it works on both Unix-likes and
Windows (and Mac) so I can use it on just about any system I'm on in
my normal work day. It works just fine from a usb drive, as well (see
http://portableapps.com/news/2010-09-20_-_gvim_portable_7.3 for one
such version).
Vim has its own internal scripting language and also can link to other
languages, like perl, python and ruby if compiled with that support,
so those languages can be used to operate on the files being edited.
The GUI version (there are several, including GTK) of vim has pull
down menus, syntax highlighting, built-in diff/compare capabaility,
etc. You can add your own functions to the menus quite easily. A
reasonably large community of users has formed around vim and this has
resulted in a lot of scripts, color schemes, usage tips, etc. See
http://www.vim.org/ which is also the place to get the latest version.
The classic Internet editor war is between emacs and vi and there's
really no winner, although some people find ways of counting users to
show their editor is the winner. The most useful position is use what
you like and what you can effectively use to do your work.
In the last 10 years many other editors have been developed that are
also usable. At the same time, some editor projects cease development
if they don't get enough support. Thus, it can be quite confusing
looking at editors if you don't have a favorite already, and you can
spend a lot of time finding one you like. There's quite often some
feature you'd like to have that's not in your current editor & that
leads you to try something else. And of course, if you work for someone
else, you possibly are required to use an editor that is different from
what you like. This is where having an editor that will run off a usb
drive is handy, if there is no prohibition against that form of usage.
A lot depends on how you got started in computing, whether on command
line or GUI or Windows/Mac or Unix. Not all editors are cross-platform,
so if that is a criterion for you, you'll be somewhat limited in your
choice of a single editor (else, you'll switch editors when you switch
platforms which can be confusing).
|
tsty
|
|
response 16 of 32:
|
Dec 11 19:25 UTC 2010 |
This response has been erased.
|
cross
|
|
response 17 of 32:
|
Dec 11 22:06 UTC 2010 |
resp:13 I thought you were an emacs user?
resp:15 I agree completely: the right tool for the right job. Frankly,
I've always found it a little silly that people get into religious arguments
about things like text editors.
|
