9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Carlos Eduardo Lenz <lenz@inf.ufsc.br>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /acme/edit
Date: Fri, 12 Oct 2001 02:49:02 -0300	[thread overview]
Message-ID: <Pine.GSO.4.10.10110120221030.14974-100000@venus> (raw)
In-Reply-To: <20011011101952.6D28719A4D@mail.cse.psu.edu>

I've used vi for so much time, I fear to become brain-damaged.
Now seriously, ok, the command language is the definitive way of doing
some things, but acme was the first mouse editor that won me.
And I'm happy with that.

I've read the manuals (how came I haven't seen that part on Edit before?)
and now maybe the only use vi will have from now will be in /etc/fstab!
Good Bye TTY!

As everybody is asking (demanding?!?) something recently, I have a little
sugestion:

There are some commands that do not appear in the per buffer menu nor in
the per column menu, but some of them I use all the time:
2button mouse(so chord doesnt work), and "Cut Paste" are far away at the
top of the column (very distant).

Proposal:
It would be nice to configure the default menu for both coulmn and
buffer setting the environment variables.

I don't know the overhead of doing this, as file operations, but
I guess the cost is some context switching with the /env fs.

Just in case nobody had already that idea.

Carlos E Lenz
lenz@inf.ufsc.br

On Thu, 11 Oct 2001 rog@vitanuova.com wrote:

> lenz@inf.ufsc.br wrote:
> > BTW, I dont think I'll learn sam just to do it.
> 
> as you've probably found out by now, acme implements almost the entire
> sam command language, so learning sam is probably the best course of
> action!  (it's well worth it IMO, as it's very powerful, and also
> useful to use along with "sam -d" to make changes across many files at
> once.)
> 
>   rog.
> 



  parent reply	other threads:[~2001-10-12  5:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11 10:32 rog
2001-10-11 11:17 ` Boyd Roberts
2001-10-12  5:49 ` Carlos Eduardo Lenz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-15 19:14 David Gordon Hogan
2001-10-15  1:21 rsc
2001-10-15  1:09 okamoto
2001-10-13 20:16 Russ Cox
2001-10-14  1:54 ` Lyndon Nerenberg
2001-10-14  2:51   ` William Josephson
2001-10-12 19:54 Russ Cox
2001-10-12  7:03 Russ Cox
2001-10-12  6:09 Russ Cox
2001-10-12  6:27 ` Carlos Eduardo Lenz
2001-10-12 16:11 ` Gene Garbutt
2001-10-12 16:24   ` William Josephson
2001-10-12 16:28   ` Boyd Roberts
2001-10-12 18:33   ` Dan Cross
2001-10-12 18:50     ` Boyd Roberts
2001-10-15  7:43     ` Boyd Roberts
2001-10-15 15:53     ` Boyd Roberts
2001-10-15  9:11   ` Douglas A. Gwyn
2001-10-13 20:02 ` Lyndon Nerenberg
2001-10-11  7:26 forsyth
2001-10-11  5:29 Russ Cox
2001-10-11  4:30 Carlos Eduardo Lenz
2001-10-11 13:21 ` Ish Rattan

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=Pine.GSO.4.10.10110120221030.14974-100000@venus \
    --to=lenz@inf.ufsc.br \
    --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).