Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: <ding@gnus.org>
Cc: David Kastrup <dak@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: message-yank-original issue
Date: Mon, 28 Mar 2011 14:05:40 -0500	[thread overview]
Message-ID: <877hbjkquz.fsf@lifelogs.com> (raw)
In-Reply-To: <87ei5tzneu.fsf@turtle.gmx.de> (Sven Joachim's message of "Sat, 26 Mar 2011 20:34:17 +0100")

On Sat, 26 Mar 2011 20:34:17 +0100 Sven Joachim <svenjoac@gmx.de> wrote: 

SJ> On 2011-03-15 10:34 +0100, Ted Zlatanov wrote:
>> On Mon, 14 Mar 2011 14:13:15 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 
>> 
TZ> On Mon, 14 Mar 2011 11:11:47 +0100 David Kastrup <dak@gnu.org> wrote: 
DK> It has now been about two weeks that message-yank-original has stopped
DK> being functional for installations that don't have cl loaded permanently
DK> (namely standard Emacs installations).
>> 
TZ> I posted a fix on the bug list, can you reply there if it worked?
>> 
>> Since I didn't hear back I've pushed this patch.

SJ> Alas, this patch was reverted later that day in commit 5edabb7b1 (Author
SJ> Stefan and committed by Katsumi, apparently in merging changes between
SJ> Gnus and Emacs), so as of now message-yank-original still requires cl to
SJ> be loaded at runtime. :-(  Could you please restore the message.el
SJ> version from commit 698d90df ?

I'm not sure what's going on with message.el.  It clearly says 

(eval-when-compile
  (require 'cl))

so it should not be erroring out.  Stefan wanted to go back to using
`case' instead of `cond' so I'll defer to him.

Ted



  reply	other threads:[~2011-03-28 19:05 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 10:11 Gnus bugfixing is broken David Kastrup
2011-03-14 14:47 ` Lars Magne Ingebrigtsen
2011-03-14 15:17   ` David Kastrup
2011-03-14 16:12     ` Adam Sjøgren
2011-03-14 17:47       ` Sivaram Neelakantan
2011-03-14 16:22     ` Lars Magne Ingebrigtsen
2011-03-14 19:13 ` message-yank-original issue (was: Gnus bugfixing is broken.) Ted Zlatanov
2011-03-14 19:38   ` message-yank-original issue Antoine Levitt
2011-03-14 19:47     ` Ted Zlatanov
2011-03-14 21:02       ` Antoine Levitt
2011-03-14 22:04         ` Ted Zlatanov
2011-03-15  0:36         ` Michael Welsh Duggan
2011-03-15 15:30         ` Lars Magne Ingebrigtsen
2011-03-15 15:29       ` Lars Magne Ingebrigtsen
2011-03-15 15:49         ` Ted Zlatanov
2011-03-15 15:56           ` Lars Magne Ingebrigtsen
2011-03-15  9:34   ` Ted Zlatanov
2011-03-15  9:48     ` David Kastrup
2011-03-15 10:01       ` Ted Zlatanov
2011-03-26 19:34     ` Sven Joachim
2011-03-28 19:05       ` Ted Zlatanov [this message]
2011-03-28 19:57         ` Sven Joachim
2011-03-28 20:06           ` Ted Zlatanov
2011-03-28 20:35         ` Stefan Monnier
2011-03-29  5:37           ` Antoine Levitt
2011-03-28 20:41         ` Stefan Monnier
2011-03-29 14:55           ` Ted Zlatanov
2011-03-29 15:08             ` David Kastrup
2011-03-29 15:20               ` Gnus compatibility with the lexical binding branch (was: message-yank-original issue) Ted Zlatanov
2011-03-29 20:16                 ` Gnus compatibility with the lexical binding branch Stefan Monnier
2011-03-29 20:53                   ` Ted Zlatanov
2011-03-30  0:42                     ` Stefan Monnier
2011-04-08  5:51                       ` Ted Zlatanov
2011-03-15 10:06 ` Gnus bugfixing is broken Ted Zlatanov
2011-03-15 13:31   ` Didier Verna
2011-03-15 13:52     ` Ted Zlatanov
2011-03-15 15:23       ` Lars Magne Ingebrigtsen
2011-03-15 15:56         ` Ted Zlatanov
2011-03-15 16:09           ` Lars Magne Ingebrigtsen
2011-03-15 17:01             ` Didier Verna
2011-03-15 13:58     ` Michael Albinus
2011-03-15 14:46       ` Didier Verna
2011-03-15 14:57         ` Ted Zlatanov
2011-03-15 15:08         ` Michael Albinus

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=877hbjkquz.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=dak@gnu.org \
    --cc=ding@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=yamaoka@jpl.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).