From: Russ Allbery <rra@stanford.edu>
Subject: Re: Quoted material manipulation commands
Date: Tue, 09 Aug 2005 19:39:17 -0700 [thread overview]
Message-ID: <87mznqy0q2.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <87br4ekaxm.fsf@Jesper-Harders-Computer.local> (Jesper Harder's message of "Wed, 03 Aug 2005 22:44:21 +0200")
Jesper Harder <harder@phys.au.dk> writes:
> Russ Allbery <rra@stanford.edu> writes:
>> C-c C-z now trims one fewer blank line. This is driving me nuts, as
>> it's destroying my finger memory. Is there a way to get back to the
>> previous behavior, or do I need to revert back to my own private
>> implementation of that feature?
> Does this work the way you want?
Yes, that does exactly what I want. Thank you! I see it's also already
been committed.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
prev parent reply other threads:[~2005-08-10 2:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 18:15 Russ Allbery
2005-08-03 20:30 ` Jesper Harder
2005-08-10 2:45 ` Russ Allbery
2005-08-03 20:44 ` Jesper Harder
2005-08-10 2:39 ` Russ Allbery [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=87mznqy0q2.fsf@windlord.stanford.edu \
--to=rra@stanford.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).