From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: RE: [9fans] acme
Date: Wed, 13 Jun 2007 09:49:01 +0100 [thread overview]
Message-ID: <13a03c71ddfc2b24c807b97d83773e53@hamnavoe.com> (raw)
In-Reply-To: <20070612145745.B2C641E8C4C@holo.morphisms.net>
>> 'Snarf' in a frame's window DOES NOT snarf that frame's dot, the
>> last one dot persists. Maybe the one that was gathered using
>> mouse-2-3?? I'll try later.
>
> if you can post a very detailed step-by-step account
> with every click and keystroke from starting acme
> that reproduces the problem, that would be helpful.
1. acme -c1 /rc/bin/termrc /rc/bin/cpurc
2. Highlight the second line of termrc (# terminal startup)
3. Highlight the second line of cpurc (# cpu server start up)
4. 2-click Snarf in the termrc tag line
5. mouse-1-3 to paste into the termrc tag line
You will see that Snarf in the termrc window grabbed the
highlighted text from the cpurc window.
acme(1) is ambiguous -- it simply says:
Snarf
Place selected text in snarf buffer.
But which selected text? We seem to be assuming it means the selected
text in the window where you clicked Snarf. Otherwise why have a
Snarf in every window's tag? But in fact it seems to be the text
which was most recently selected, regardless of which window or tag
line it is in.
next prev parent reply other threads:[~2007-06-13 8:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 11:28 cej
2007-06-05 11:39 ` Federico Benavento
2007-06-05 12:01 ` Gabriel Diaz
2007-06-05 12:11 ` erik quanstrom
2007-06-05 11:59 ` erik quanstrom
2007-06-05 14:42 ` [9fans] not acme Russ Cox
2007-06-05 15:00 ` [9fans] acme Russ Cox
2007-06-05 15:09 ` ron minnich
2007-06-06 12:12 ` cej
2007-06-05 17:55 ` lucio
2007-06-05 19:30 ` ron minnich
2007-06-05 18:00 ` lucio
2007-06-12 12:29 ` cej
2007-06-12 8:57 ` Russ Cox
2007-06-13 8:49 ` Richard Miller [this message]
2007-06-13 5:13 ` Russ Cox
2007-06-15 4:12 ` Russ Cox
2007-06-13 23:50 ` [9fans] usenix Charles Forsyth
2007-06-14 0:01 ` Uriel
2007-06-14 0:45 ` ron minnich
2007-06-14 8:04 ` Francisco J Ballesteros
2007-06-14 18:08 ` ron minnich
2007-06-14 20:56 ` Francisco J Ballesteros
2007-06-14 21:18 ` Latchesar Ionkov
2007-06-14 21:47 ` john
2007-06-14 22:33 ` ron minnich
2007-06-14 22:55 ` john
2007-06-14 0:42 ` ron minnich
2007-06-14 1:18 ` Eric Van Hensbergen
2007-06-14 1:31 ` ron minnich
-- strict thread matches above, loose matches on Subject: below --
2010-11-27 12:39 [9fans] acme Kenji Arisawa
2010-11-27 18:12 ` ron minnich
2010-11-28 11:17 ` Kenji Arisawa
2004-01-10 7:01 [9fans] Sam's protocol description? Rob Pike
2004-01-10 15:46 ` [9fans] acme vdharani
2004-01-10 16:07 ` rob pike, esq.
2002-05-10 2:24 rob pike, esq.
2002-03-20 6:58 [9fans] Acme forsyth
2002-03-20 3:30 rob pike
2002-03-11 0:15 [9fans] samuel Geoff Collyer
2002-03-20 3:26 ` [9fans] Acme Tharaneedharan Vilwanathan
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=13a03c71ddfc2b24c807b97d83773e53@hamnavoe.com \
--to=9fans@hamnavoe.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).