From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] home, end ^h^j^k^l
Date: Mon, 21 May 2001 16:23:59 +0000 [thread overview]
Message-ID: <3B093634.CDBFDDE3@null.net> (raw)
In-Reply-To: <200105191707.KAA00509@tammananny.tiger>
Quinn Dunkan wrote:
> Deleting text with backspace replaces the snarf buffer. I often cut out
> something I want, and then do some editing to prepare a place for it, and wind
> up deleting a space or something, at which point my paste doesn't give what I
> expected. I don't think the snarf buffer should be quite so ephemeral, but it
> probably also has something to do with how I work (i.e., if I want to snarf
> something, I snarf, and if I want to delete it, I delete).
It's not just you; I keep running into this problem using "sam".
Partly it's coupled to the behavior of backspace for a highlighted
region: to exactly delete what is highlighted, one has to cut it,
which overwrites the snarf buffer.
I would actually prefer an array of snarf buffers (a la TECO's
Q-registers), but then the complexity starts to overwhelm the
user. I doubt it is possible to design a *small* interface that
best fits all usage patterns.
next prev parent reply other threads:[~2001-05-21 16:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 10:18 Matt H
2001-05-18 19:26 ` Chris Locke
2001-05-18 19:34 ` Scott Schwartz
2001-05-19 7:54 ` Re[2]: " Matt H
2001-05-19 17:07 ` Quinn Dunkan
2001-05-19 16:00 ` Re[4]: " Matt H
2001-05-19 20:46 ` Boyd Roberts
2001-05-21 16:24 ` Douglas A. Gwyn
2001-05-21 16:23 ` Douglas A. Gwyn [this message]
2001-05-19 20:19 ` Re[2]: " Boyd Roberts
2001-05-18 22:28 ` Boyd Roberts
2001-05-18 15:17 Russ Cox
2001-05-21 8:38 ` Douglas A. Gwyn
2001-05-18 20:23 rog
2001-05-19 15:39 Re[4]: " rob pike
2001-05-21 16:24 ` Douglas A. Gwyn
2001-05-22 6:25 nemo
2001-05-22 6:35 ` Scott Merrilees
2001-05-22 8:31 ` Boyd Roberts
2001-05-22 7:17 nemo
2001-05-22 12:36 rob pike
2001-05-22 14:42 nemo
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=3B093634.CDBFDDE3@null.net \
--to=dagwyn@null.net \
--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).