From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Acme 3-1
Date: Tue, 18 Feb 2003 19:41:14 +0000 [thread overview]
Message-ID: <b116f18f5ccf0ab7e5bcea73d7631427@vitanuova.com> (raw)
> Of course, you could take a tip from plumbing's relatives in
> other systems and provide a UI for selecting where it goes,
> but 99% of plumbing's value is its automation.
that's why i thought it might be nice to have it go automatically to
the window you've most recently interacted with (or some approximation
thereof).
the rule could also specify fan-out or not (e.g. "plumb toall edit")
then you'd have your UI for selecting whether it fans out (plumb
/mnt/plumb/rules).
it doesn't look hard to do in the code. i'll experiment with it.
next reply other threads:[~2003-02-18 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 19:41 rog [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 1:12 okamoto
2003-02-18 13:21 rog
2003-02-18 13:38 ` Russ Cox
2003-02-18 17:04 ` rob pike, esq.
2003-02-18 12:12 rog
2003-02-18 12:19 ` Russ Cox
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=b116f18f5ccf0ab7e5bcea73d7631427@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).