9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Hack for acme
Date: Wed,  5 Mar 2003 13:17:27 -0500	[thread overview]
Message-ID: <Pine.LNX.4.30.0303051307570.3513-100000@athena> (raw)
In-Reply-To: <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.

Not to be argumentative, but so does 3-2.  Not including a seemingly
useful feature because you don't want to change the behaviour of your
fingers under a seldom used mechanism seems foolish.  If you want
1 to cancel a 3 click then it should be across the board and cancel
a 2 click as well.  Regularity shouldn't be an option.

Since 1 is useful for X with args, it can be useful for open with args.
Suppose the concept whereby the user highlights a string
representative of the window he/she wants the open to occur in.
If you highlight, say, `.' you mean ``open here.''  Otherwise,
you could open all docs in one particular window.  Perhaps there
are other uses.

I'm not certain of acme's internal window naming organisation,
but this seems doable.

Sam



  reply	other threads:[~2003-03-05 18:17 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 [this message]
2003-03-05 18:24   ` Skip Tavakkolian
2003-03-05 19:18   ` Fco.J.Ballesteros
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=Pine.LNX.4.30.0303051307570.3513-100000@athena \
    --to=sah@softcardsystems.com \
    --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).