Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: <ding@gnus.org>
Subject: Re: message.el dependency in mm-uu.el
Date: Sat, 10 Dec 2005 11:12:42 +0100	[thread overview]
Message-ID: <v9fyp1gt0l.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <v9ek4lsvxe.fsf_-_@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sat, 10 Dec 2005 00:16:45 +0100")

[ Cc-ing ding ]

On Sat, Dec 10 2005, Reiner Steib wrote:

> On Fri, Dec 09 2005, Romain Francoise wrote:
>
>>> +    (message-marks
>>> +     ,(concat "^" (regexp-quote message-mark-insert-begin))
>>> +     ,(concat "^" (regexp-quote message-mark-insert-end))
>>> +     (lambda () (mm-uu-verbatim-marks-extract 0 -1 1 -2))
>>
>> This causes a problem with MH-E, which uses mm-uu.el for one of its
>> functions, but doesn't load message.el first.  See the following Debian
>> bug:
>>
>>     <URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342521>
>>
>> A possible solution would be to make mm-uu.el require message.el.
>> I'm not too comfortable with that because the dependency is needed for a
>> very small part of mm-uu and could probably be avoided.  What do you
>> think?
>
> Thanks for pointing this out.
>
> MML (mml*.el and mm-*.el) is supposed to be independent from Gnus.
> Most probably also independent from message.el (which should in turn
> be independent from Gnus).
>
> I'm trying to document the dependencies in `texi/gnus-coding.texi'.
> Any help with improving this document and remove existing dependencies
> would be very welcome.
>
> The most simple solution would be to hard-code the values of
> message-mark-insert-begin/end (and add a comment to both places
> referring to each other).  Or do you have a better solution in mind?
>
> --- message.el	27 Nov 2005 18:15:17 +0100	7.112
> +++ message.el	10 Dec 2005 00:12:25 +0100	
> @@ -335,6 +335,9 @@
>  
>  ;;; marking inserted text
>  
> +;; If `message-mark-insert-begin' or `message-mark-insert-end' are changed, we
> +;; should also change the `message-marks' element of `mm-uu-type-alist' in
> +;; `mm-uu.el'.
>  (defcustom message-mark-insert-begin
>    "--8<---------------cut here---------------start------------->8---\n"
>    "How to mark the beginning of some inserted text."
>
> --- mm-uu.el	06 Dec 2005 15:47:44 +0100	7.20
> +++ mm-uu.el	10 Dec 2005 00:10:39 +0100	
> @@ -165,8 +165,16 @@
>       nil
>       mm-uu-diff-test)
>      (message-marks
> -     ,(concat "^" (regexp-quote message-mark-insert-begin))
> -     ,(concat "^" (regexp-quote message-mark-insert-end))
> +     ;; Don't use `message-mark-insert-begin' and `message-mark-insert-end'
> +     ;; here to avoid dependency on `message.el'.
> +     ,(concat
> +       "^"
> +       (regexp-quote
> +	"--8<---------------cut here---------------start------------->8---\n"))
> +     ,(concat
> +       "^"
> +       (regexp-quote
> +	"--8<---------------cut here---------------end--------------->8---\n"))
>       (lambda () (mm-uu-verbatim-marks-extract 0 -1 1 -2))
>       nil)
>      ;; Omitting [a-z8<] leads to false positives (bogus signature separators

Maybe the following mm-uu.el patch would be better:

#v+
--- mm-uu.el	06 Dec 2005 15:47:44 +0100	7.20
+++ mm-uu.el	10 Dec 2005 10:38:29 +0100	
@@ -165,8 +165,10 @@
      nil
      mm-uu-diff-test)
     (message-marks
-     ,(concat "^" (regexp-quote message-mark-insert-begin))
-     ,(concat "^" (regexp-quote message-mark-insert-end))
+     ;; Don't use `message-mark-insert-begin' and `message-mark-insert-end'
+     ;; here to avoid dependency on `message.el'.
+     "^-\\{2,\\}[8<>]*-\\{9,\\}[a-z ]+-\\{9,\\}[a-z ]+-\\{9,\\}[8<>]*-\\{2,\\}$"
+     "^-\\{2,\\}[8<>]*-\\{9,\\}[a-z ]+-\\{9,\\}[a-z ]+-\\{9,\\}[8<>]*-\\{2,\\}$"
      (lambda () (mm-uu-verbatim-marks-extract 0 -1 1 -2))
      nil)
     ;; Omitting [a-z8<] leads to false positives (bogus signature separators
#v-

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



       reply	other threads:[~2005-12-10 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1EUTwG-0005SS-00@quimby.gnus.org>
     [not found] ` <87slt2jcu2.fsf@pacem.orebokech.com>
     [not found]   ` <v9ek4lsvxe.fsf_-_@marauder.physik.uni-ulm.de>
2005-12-10 10:12     ` Reiner Steib [this message]
2005-12-10 10:34       ` Romain Francoise

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=v9fyp1gt0l.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).