9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: FJ Ballesteros <nemo@gsyc.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Emacs
Date: Mon, 10 Jun 2002 22:43:50 +0200	[thread overview]
Message-ID: <3D050F86.9A3CE7@gsyc.escet.urjc.es> (raw)
In-Reply-To: <ug9cjbrjn91kd0@news.supernews.com>

As I said in a previous message, I think I could be considered as
an "advanced emacs user" (sic, don't blame me); but since I tried
acme I found that most of the things I was doing in a complex way with
emacs could be done in a much simpler way with tiny scripts and acme.

Why don't you just try it, until you learn how to use it well, and then
decide?


Blake McBride ha escrito:
>
> 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.
>
> Things I commonly use in emacs:
>
> intelligent Keyboard macros
> intelligent auto indent
> repeat command n number of times
> Undo
> Query replace
> Scroll one line at a time (up or down)
> Put current line at top of screen
> Narrow region
> Don't wrap lines on display
> Push, pop, and remember locations
> Assign blocks of text to registers (cut and paste more than one block)
> Be able to switch back and forth between two buffers without having to
> select it each time
> Save ALL modified buffers command
> Find matching paren, brace, etc.
> Abbreviations
>
> Can sam or acme do these?  I think these are powerful capabilities.
> Surely I can write whatever I want in ed but these features make my
> life a lot easier and more productive.
>
> --------------
> Download source code to my Dynace Object Oriented
> Extension to C and Windows Development System from:
> http://algorithms.us
> Blake McBride (blake@algorithms.us)
> Algorithms Corporation - 615-791-1636 - USA


  parent reply	other threads:[~2002-06-10 20:43 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
2002-06-10 18:15     ` Fariborz Tavakkolian
2002-06-10 20:43   ` FJ Ballesteros [this message]
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=3D050F86.9A3CE7@gsyc.escet.urjc.es \
    --to=nemo@gsyc.escet.urjc.es \
    --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).