From: Quinn Dunkan <quinn@envy.ugcs.caltech.edu>
To: 9fans@cse.psu.edu
Subject: Re: Re[2]: [9fans] home, end ^h^j^k^l
Date: Sat, 19 May 2001 10:07:30 -0700 [thread overview]
Message-ID: <200105191707.KAA00509@tammananny.tiger> (raw)
In-Reply-To: Your message of "Sat, 19 May 2001 08:54:40 BST." <150144503394.20010519085440@proweb.co.uk>
> CL> What are other peoples most common acme 'gotchas'?
>
> my other one is one I'm learning to deal with
>
> in windows if you select some text and press backspace you delete the
> selected text. If you select some text in acme it replaces the current
> text with a backspace so it also deletes the character to the left of
> your selected text. So, as you must do, I select one less then the
> ones I want to delete.
Nowadays, I get surprised by Linux and Windows when backspace doesn't
delete backwards like it's supposed to. Plan9's behaviour works nicely
for deleting words. Otherwise, I've learned to use a cut chord, which
only removes that which is selected. Since you're using the mouse
for selecting anyway, it's easy to just cut out your text.
> functioning cursor keys would still be a speed benefit.
They do function! Oh, you mean functioning *your* way ;)
My acme gotchas:
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).
New windows rarely appear where I want them. I gather the heuristic is
optimized for a particular pattern of use, and I recall seeing that
documented somewhere, but can't find it now.
next prev parent reply other threads:[~2001-05-19 17:07 UTC|newest]
Thread overview: 12+ 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 [this message]
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
2001-05-19 20:19 ` Re[2]: " Boyd Roberts
2001-05-18 22:28 ` Boyd Roberts
2001-05-19 8:29 Re[2]: " Russ Cox
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=200105191707.KAA00509@tammananny.tiger \
--to=quinn@envy.ugcs.caltech.edu \
--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).