Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: "Daiki Ueno" <ueno@unixuser.org>
Cc: ding@gnus.org
Subject: Re: PGG: "NotDashEscaped: You need GnuPG to verify this message"
Date: Sun, 06 Jan 2008 15:10:53 +0100	[thread overview]
Message-ID: <v963y7hwnm.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <54a15d860801060423k4b75fad8g69df9b1f1c52ed1d@mail.gmail.com> (Daiki Ueno's message of "Sun, 6 Jan 2008 21:23:48 +0900")

On Sun, Jan 06 2008, Daiki Ueno wrote:

> 2008/1/6, Reiner Steib <reinersteib+gmane@imap.cc>:
>> ,----[ gnus-buttonized-mime-types -> nil ]
>> | NotDashEscaped: You need GnuPG to verify this message
>> `----
> [...]
>> According to the thread "NotDashEscaped, what?" in August 2007 [2]
>> the change [3] should have fixed this.  I'm not sure if "fixed"
>> includes _not_ displaying the line "NotDashEscaped: You need GnuPG to
>> verify this message", but I think Gnus should hide it (same as hiding
>> "Hash: SHA1") in the normal display.
>
> As I recall, I did fix it for the EasyPG backend of mml2015 but didn't
> touch the behavior of the PGG backend.

I don't known.  The OP in, Michaël Cadilhac, didn't mention that he
uses EasyPG and the ChangeLog says you changed `mml2015-pgg-clear-verify'
as well.

Anyhow, I think it should be fixed for PGG as well (in v5-10/Emacs_22
and trunk/Emacs_23).  Could you fix it, please?

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



  reply	other threads:[~2008-01-06 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06  9:58 Reiner Steib
2008-01-06 12:23 ` Daiki Ueno
2008-01-06 14:10   ` Reiner Steib [this message]
2008-01-07  3:22     ` Daiki Ueno
2008-01-07 22:02       ` Reiner Steib
2008-01-08  9:42         ` Daiki Ueno

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