From: Harry Putnam <reader@newsguy.com>
Subject: Re: Ill-behavior when making follow-ups
Date: Tue, 26 Mar 2002 16:33:08 -0800 [thread overview]
Message-ID: <m14rj2alyz.fsf@reader.newsguy.com> (raw)
In-Reply-To: <ofhboun4.fsf@random.localnet.UnwiredUniverse.com> (Derrell.Lipman@UnwiredUniverse.com's message of "Tue, 26 Mar 2002 17:02:07 -0500")
Derrell.Lipman@UnwiredUniverse.com writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>> At a minimum there should be a key combo to `unselect', to restore the
>> normal functioning of `F' where all but the headers is yanked.
>
> How about 'f C-c C-y'?
Yup.. that helps
Doesn't really solve the problem of runaway grabbing of text, but at
least provides a way to get to a normal situation.
prev parent reply other threads:[~2002-03-27 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-26 20:24 Jens Müller
2002-03-26 21:48 ` Harry Putnam
2002-03-26 22:02 ` Derrell.Lipman
2002-03-27 0:33 ` Harry Putnam [this message]
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=m14rj2alyz.fsf@reader.newsguy.com \
--to=reader@newsguy.com \
/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).