From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: M-RET in message mode: don't reformat?
Date: Sat, 12 Apr 2003 21:50:46 +0200 [thread overview]
Message-ID: <m3brzbpka1.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <843cl2twq5.fsf@lucy.is.informatik.uni-duisburg.de>
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> I think (1)+(2) is useful even in the absence of (3).
Currently, `C-u M-RET' justifies the text. Is that useful, at all?
If not, we could just switch the prefix to inhibit (3).
A different approach would be to set an undo boundary before doing
(3), so that you could just say `M-RET C-_' to get the desired
effect...
What do you think?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2003-04-12 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 14:20 Kai Großjohann
2003-03-31 16:40 ` Lars Magne Ingebrigtsen
2003-04-01 9:04 ` Kai Großjohann
2003-04-01 10:58 ` Niklas Morberg
2003-04-01 12:56 ` Kai Großjohann
2003-04-12 19:50 ` Lars Magne Ingebrigtsen [this message]
2003-04-12 21:29 ` Kai Großjohann
2003-04-12 21:46 ` Lars Magne Ingebrigtsen
2003-04-12 22:24 ` François Pinard
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=m3brzbpka1.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).