Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Olson <mwolson@gnu.org>
To: ding@gnus.org
Subject: Re: [PATCH] mml.el: Make sure that <#part> sections are at beginning of line.
Date: Mon, 19 May 2008 10:51:44 -0700	[thread overview]
Message-ID: <87d4niyyfj.fsf@grepfind.mwolson.org> (raw)
In-Reply-To: <v9fxsew60c.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 19 May 2008 19:36:19 +0200")

[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> I'm not sure if it's correct.  AFAICS, the specification doesn't say
> that the tags are at the beginning of line, cf. (info "(emacs-mime)MML
> Definition").

I guess it doesn't mention the beginning of the line.  Is MML some sort
of widely-used standard, or is it specific to Message Mode / Gnus?  If
it's local to Gnus, it might be nice to modify the definition to say
that tags must occur at the beginning of a line.

> Maybe instead, we should check if there's a closing `<#/part>' or
> `<#/multipart>' tag.  If not, suggest to run `mml-quote-region' on the
> body:

The problem is that this creates ambiguity if both "<#part>" and
"<#/part>" are next to each other (like in this email message!).  This
patch would completely remove the ambiguity.

-- 
|       Michael Olson  |  FSF Associate Member #652     |
| http://mwolson.org/  |  Hobbies: Lisp, HCoop          |
| Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner |
`-------------------------------------------------------'

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2008-05-19 17:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 16:08 Michael Olson
2008-05-19 17:36 ` Reiner Steib
2008-05-19 17:51   ` Michael Olson [this message]
2008-05-19 20:53     ` Reiner Steib
2008-05-19 21:12       ` Michael Olson

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=87d4niyyfj.fsf@grepfind.mwolson.org \
    --to=mwolson@gnu.org \
    --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).