Gnus development mailing list
 help / color / mirror / Atom feed
From: "Łukasz Stelmach" <lukasz.stelmach@iem.pw.edu.pl>
To: ding@gnus.org
Subject: Re: [BUG] yanking base64 encoded e-mail is a fail
Date: Thu, 25 Nov 2010 00:02:13 +0100	[thread overview]
Message-ID: <87vd3mba16.fsf@kotik.lan> (raw)
In-Reply-To: <m3pqtu5ucp.fsf@quimbies.gnus.org>

<#secure method=pgpmime mode=sign>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Julien Danjou <julien@danjou.info> writes:
>
>> I've re-reverted with a fix. Does this seems good to you?
>
> It should really return the point where the body starts, which it does
> now, but, on the other hand, if you have a <#secure thing in there,
> it'll return a different value from where it's putting point, so it
> seems inconsistent...

IMHO if it makes any difference whether message-goto-body returns point
right after mail-header-separator or after <#secure then there is
something wrong. My mistake was not to return the point from the
mssage-goto-body at all. Take a look at <87wro2babo.fsf@kotik.lan>, I
think there is a fix.

> I'm not sure what the <#secure thing is trying to fix, but I think it
> sounds like that is being done in the wrong place, perhaps.

OK, so I made a mess. 

-- 
Miłego dnia,
Łukasz Stelmach




  reply	other threads:[~2010-11-24 23:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 22:52 Łukasz Stelmach
2010-11-24 19:50 ` Lars Magne Ingebrigtsen
2010-11-24 19:54   ` Lars Magne Ingebrigtsen
2010-11-24 20:01     ` Lars Magne Ingebrigtsen
2010-11-24 20:02       ` Lars Magne Ingebrigtsen
2010-11-24 20:16         ` Lars Magne Ingebrigtsen
2010-11-24 20:28           ` Julien Danjou
2010-11-24 20:38             ` Sven Joachim
2010-11-24 20:39             ` Lars Magne Ingebrigtsen
2010-11-24 23:02               ` Łukasz Stelmach [this message]
2010-11-24 20:17   ` Julien Danjou

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=87vd3mba16.fsf@kotik.lan \
    --to=lukasz.stelmach@iem.pw.edu.pl \
    --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).