From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Emacs 17+gnus and comments
Date: Thu, 03 May 2018 09:40:41 -0700 [thread overview]
Message-ID: <87zi1gu1yu.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <878t90j37b.fsf@mat.ucm.es>
Uwe Brauer <oub@mat.ucm.es> writes:
> Hi
>
> I receive sometimes messages like this
>
>>>> "Uwe" == Uwe Brauer <oub@mat.ucm.es> writes:
>
>> This is a test of the
>> comment structure
>>
>> We have an empty line
>>
>> And another one.
>
> Now, please note that the empty lines start with a > without a space!
Right, and `message-yank-prefix' (which gets used as the value of
`comment-start') has a space, meaning those lines aren't recognized as
comments.
Maybe try setting `message-yank-empty-prefix' to "> "? For your own
citations, anyway, that ought to ensure the space is there. I don't know
about other people's citations, though...
next prev parent reply other threads:[~2018-05-03 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 13:09 Uwe Brauer
2018-05-03 16:40 ` Eric Abrahamsen [this message]
2018-05-04 20:18 ` Uwe Brauer
2018-05-04 21:45 ` Eric Abrahamsen
2018-05-05 9:43 ` Uwe Brauer
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=87zi1gu1yu.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@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).