From: Quinn Dunkan <quinn@cruzeiro.ugcs.caltech.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Emacs
Date: Mon, 10 Jun 2002 10:13:01 -0700 [thread overview]
Message-ID: <20020610171306.B4ABF88036@cruzeiro.ugcs.caltech.edu> (raw)
In-Reply-To: Your message of "Mon, 10 Jun 2002 14:10:13 GMT." <ug9cjbrjn91kd0@news.supernews.com>
> I think one of main problems is that, in spite of the fact that I
> have a quality video board, Plan 9 comes up in a low
> resolution. It's so low that if I open up an RC window and
> do a man on a command the text partially wraps and is difficult
> to read. If I could fix that problem I'd feel a lot better.
Posting about editors is not likely to get you much help on that one.
> Things I commonly use in emacs:
Most of these are directly supported. One thing that I've been having fun with
in vim is text folding, but it's a toss up between that and opening another
window.
> Undo
> Query replace
Yes.
> Scroll one line at a time (up or down)
> Put current line at top of screen
Yes. You can put any line at the top of the screen.
> Save ALL modified buffers command
Yes.
> Be able to switch back and forth between two buffers without having to
> select it each time
Yes. Any more than two.
> Find matching paren, brace, etc.
Yes, by double clicking.
> intelligent Keyboard macros
You can perform an arbitrary transformation on any selected text with a click,
and you can assign arbitrary meaning to middle or right clicking on any text.
Not exactly the same, but it fills the same need for me.
> intelligent auto indent
The only place I find autoindent timesaving is lisp, and I can't really use
acme/wily for lisping. Which is too bad since I'd prefer an acme style
inferior mode to ilisp or whatever.
> Narrow region
Not sure what this is.
> Assign blocks of text to registers (cut and paste more than one block)
acme makes it so easy to open more windows and to cut and paste, I've never
wanted this.
> repeat command n number of times
No, but that's what Edit is for.
> Don't wrap lines on display
> Push, pop, and remember locations
> Abbreviations
No, no, and no. I use the second two in vim, but never missed any of them in
acme. Pressing return every once and a while solves the first one, and right
clicking and plumbing mostly subsumes the second one. Not using insanely
long identifiers helps with the last one.
next prev parent reply other threads:[~2002-06-10 17:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 9:35 nigel
2002-06-10 9:53 ` Blake McBride
2002-06-10 17:00 ` Steve Kilbane
2002-06-11 9:08 ` Don
2002-06-11 18:55 ` Vladimir G. Ivanovic
2002-06-12 8:54 ` Don
2002-06-11 9:09 ` Douglas A. Gwyn
2002-06-10 10:02 ` Douglas A. Gwyn
2002-06-10 14:10 ` Blake McBride
2002-06-10 17:13 ` Quinn Dunkan [this message]
2002-06-10 18:15 ` Fariborz Tavakkolian
2002-06-10 20:43 ` FJ Ballesteros
2002-06-11 9:08 ` Don
2002-06-11 9:09 ` Douglas A. Gwyn
2002-06-12 8:54 ` Joel Salomon
2002-06-10 15:47 ` James A. Robinson
2002-06-11 15:27 ` Blake McBride
2002-06-11 17:36 ` Digby Tarvin
2002-06-11 17:44 ` James A. Robinson
2002-06-11 20:43 ` Digby Tarvin
-- strict thread matches above, loose matches on Subject: below --
2002-06-12 17:56 anothy
2002-06-12 9:18 nigel
2002-06-12 9:07 forsyth
2002-06-12 10:08 ` John Murdie
2002-06-13 9:29 ` Don
2002-06-12 7:49 Fco.J.Ballesteros
2002-06-11 10:08 forsyth
2002-06-12 8:54 ` Don
2002-06-10 10:31 nigel
2002-06-10 10:31 nigel
2002-06-10 10:21 Fco.J.Ballesteros
2002-06-10 10:10 forsyth
2002-06-07 9:06 Blake McBride
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020610171306.B4ABF88036@cruzeiro.ugcs.caltech.edu \
--to=quinn@cruzeiro.ugcs.caltech.edu \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).