9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Acme 3-1
Date: Tue, 18 Feb 2003 12:12:42 +0000	[thread overview]
Message-ID: <bb33387ba10c28c1509365297565d34f@vitanuova.com> (raw)

> 3-1 and 2-1 are already defined: they cancel button 3 and button 2 actions.
> I would object to giving them another meaning.

i thought 2-1 appended the most recently selected text as an argument
to the executed command (and 2-3 cancels the b2 action).  i use this
for Edit commands (and was confused a moment ago because it doesn't
work in Mail windows).

as far as i can see 3-1 is the only button chord that's currently
redundant (has the same meaning as 3-2):

	1	select
	2	execute
	3	look
	1-2	cut
	1-3	paste
	2-1	execute with args
	2-3	cancel execute
	3-1	cancel look
	3-2	cancel look

that's not an argument for giving it a new meaning!

i do sometimes wish for a way to express plumbing preferences
dynamically (e.g.  when starting a new copy of acme and wishing that
a) text files would open in the new copy and b) that other plumbing
would still work).

i wondered if perhaps it might make sense for an application to be
able to write a "priority" message to the plumbing "send" file -
plumbing messages would be then routed to that app in preference to
others (a plumbing message would be sent to only one app, rather than
fanning out as currently).

an application could send the "priority" message when its window was
raised.  this might provide behaviour that seemed reasonably natural.

what currently depends on the fan-out behaviour of plumbing?
(mail/fs, i guess, when messages are deleted, but that's very slow,
and works without plumbing anyway).



             reply	other threads:[~2003-02-18 12:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18 12:12 rog [this message]
2003-02-18 12:19 ` Russ Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-02-19  1:12 okamoto
2003-02-18 19:41 rog
2003-02-18 13:21 rog
2003-02-18 13:38 ` Russ Cox
2003-02-18 17:04 ` rob pike, esq.
2003-02-18  8:05 peter a. cejchan
2003-02-18  1:48 rob pike, esq.
2003-02-18 12:19 ` paurea
2003-02-18 14:10   ` Sam

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=bb33387ba10c28c1509365297565d34f@vitanuova.com \
    --to=rog@vitanuova.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).