From: Christopher Schmidt <christopher@ch.ristopher.com>
To: ding@gnus.org
Subject: Re: mml-insert-tag: insert closing tag
Date: Wed, 30 Jan 2013 08:55:13 +0000 (GMT) [thread overview]
Message-ID: <87wquvt5hq@ch.ristopher.com> (raw)
In-Reply-To: <b4mr4l3t5xo.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 30 Jan 2013 17:45:39 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Christopher Schmidt wrote:
>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>> Because at least I get used to start writing at the end of a message
>>> buffer whatever exists above, so I'll simply move the point to the
>>> end indiscreetly. Anyway, Gnus does well in encoding an
>>> unterminated part. What is necessary in the end of a part is the
>>> buffer's end, or an open tag of the next part, I believe.
>
>> This will not help if the users wants to put the part inline. At the
>> same time, it is not only about Gnus recognising the bounds of the
>> individual parts - the end tag is an important visual marker for the
>> user.
>
> I see. So, how about putting a closing tag only when it is in
> the middle of a message buffer?
I don't know. I guess this is a reasonable default behaviour. I
(personally) always want an end tag, though.
Christopher
next prev parent reply other threads:[~2013-01-30 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 17:49 Christopher Schmidt
2013-01-29 22:49 ` Katsumi Yamaoka
2013-01-30 7:28 ` Christopher Schmidt
2013-01-30 8:30 ` Katsumi Yamaoka
2013-01-30 8:37 ` Christopher Schmidt
2013-01-30 8:45 ` Katsumi Yamaoka
2013-01-30 8:55 ` Christopher Schmidt [this message]
2013-01-30 9:35 ` Katsumi Yamaoka
2013-01-30 9:57 ` Christopher Schmidt
2013-01-30 10:43 ` Katsumi Yamaoka
2013-01-30 10:53 ` Christopher Schmidt
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=87wquvt5hq@ch.ristopher.com \
--to=christopher@ch.ristopher.com \
--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).