9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Hack for acme
Date: Wed,  5 Mar 2003 20:18:38 +0100	[thread overview]
Message-ID: <25258ea5fee1d8a6d19f2d0e6f7b8f79@plan9.escet.urjc.es> (raw)
In-Reply-To: <d2708caf4df164a10d01adbc3aa1cf1f@plan9.bell-labs.com>

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

What we do is to make our changes and after experience says if
we are using them or not, we keep them or delete them. I just deleted
the Ignore command I added time ago to acme because we found that we
have seldom used it.

Regarding 3-1, paurea is using it a lot on directories, I've used it
several times these days, but I still don't know if that's really useful
for me or not. If after some time we find that we seldom use it, we'll
delete that feature; but I think that we'll be using it a lot (at least
paurea is doing so, and I think I'm going the same way).

On files, I *never* used 3-1. Well, I used it once when I first tried
acme, just to play with undoing buttons. I don't know for sure, but I
think paurea never used it either.

Most times, I notice that I used 3 to open a wrong file (eg /dev/zero and
alike) after I released the button (which makes 3-1 no longer useful as
a cancel).

On the other hand, we had 2 on directories instead of 3-1 some time ago.
It was confusing because some directories correspond to program names in
/bin. That's why we decided to move to 3-1 instead of keep on using 2.

[-- Attachment #2: Type: message/rfc822, Size: 2070 bytes --]

From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Hack for acme
Date: Wed, 5 Mar 2003 12:52:21 -0500
Message-ID: <d2708caf4df164a10d01adbc3aa1cf1f@plan9.bell-labs.com>

We did not include the 3-1 change in our acme, mainly because 3-1
cancels a 3 that you've started and want to back out.  In other
words, as Rob pointed out before, 3-1 is already taken.

It might be reasonable to use 2 to ``exec'' a directory by opening it
in the same window, but then there is the inconsistency that 2 on a
directory and 2 on a file behave differently.  

I think that if I had the ability to open a directory in the same window,
I might use it a fair amount.  I'm not sure how much I would use the
open a file in the same window capability.  I'm still thinking about 2.
But 3-1 won't happen.

Paurea and Nemo, how much do you use your 3-1 on files vs. directories?

Russ

  parent reply	other threads:[~2003-03-05 19:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 17:23 paurea
2003-03-05 17:52 ` Russ Cox
2003-03-05 18:17   ` Sam
2003-03-05 18:24   ` Skip Tavakkolian
2003-03-05 19:18   ` Fco.J.Ballesteros [this message]
2003-03-06  9:41     ` Douglas A. Gwyn
2003-03-06  9:51   ` paurea
  -- strict thread matches above, loose matches on Subject: below --
2003-03-06 11:39 peter a. cejchan
2003-03-07 12:39 ` paurea
2003-03-06  6:32 peter a. cejchan
2003-03-03 11:56 [9fans] hack " paurea

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=25258ea5fee1d8a6d19f2d0e6f7b8f79@plan9.escet.urjc.es \
    --to=nemo@plan9.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).