[XEmacs] problem with date

[XEmacs] problem with date

[Sébastien Kirche]

Hi,

I am currently giving a try with XEmacs while i am a regular GNU/Emacs
user and i have a problem with the Date: header.

As you can see, instead of having the timezone at the end of the field
(I am currently in +0200) i have a weird 'z' letter.

This result in displaying the date of the message in the summary buffer
2 hours later than the actual date.

My Gnus is from CVS, updated yesterday.

-- 
Sébastien Kirche

Re: [XEmacs] problem with date

[Katsumi Yamaoka]

>>>>> In <m28xx9xu0y.fsf@seki.fr> Sébastien Kirche wrote:

> Hi,

> I am currently giving a try with XEmacs while i am a regular GNU/Emacs
> user and i have a problem with the Date: header.

> As you can see, instead of having the timezone at the end of the field
> (I am currently in +0200) i have a weird 'z' letter.

> This result in displaying the date of the message in the summary buffer
> 2 hours later than the actual date.

> My Gnus is from CVS, updated yesterday.

My best guess is that it is caused by the message-make-date
function defined in message.el.  It is for only Emacs[1] but
should be replaced by message-xmas-make-date for XEmacs defined
in messagexmas.el.  message.elc seems to certainly load
messagexmas.elc and replace it by running the following section:

(when (featurep 'xemacs)
  (require 'messagexmas)
  (message-xmas-redefine))

Even if message.elc is reloaded, it should work.  So, I don't
see why such a problem occurs.

[1] The %z spec which XEmacs doesn't support is given to the
format-time-string function there.

Re: [XEmacs] problem with date

[Katsumi Yamaoka]

>>>>>> In <m28xx9xu0y.fsf@seki.fr> Sébastien Kirche wrote:

>> I am currently giving a try with XEmacs while i am a regular GNU/Emacs
>> user and i have a problem with the Date: header.

>> As you can see, instead of having the timezone at the end of the field
>> (I am currently in +0200) i have a weird 'z' letter.

>> This result in displaying the date of the message in the summary buffer
>> 2 hours later than the actual date.

>> My Gnus is from CVS, updated yesterday.

>>>>> In <b4mek704va1.fsf@jpl.org> Katsumi Yamaoka wrote:

> My best guess is that it is caused by the message-make-date...

Another guess is that you failed to fully install CVS Gnus.
messagexmas.el is essential to make XEmacs run Gnus, however it
won't be installed for Emacs.  I suspect you installed CVS Gnus
using Emacs first and recompiled them using XEmacs.  You will
probably need to know where message.elc and messagexmas.elc come
from.  To do that:

M-x locate-library RET message RET
M-x locate-library RET messagexmas RET

If message.elc comes from CVS Gnus and messagexmas.elc comes
from the XEmacs package, it will naturally happen.  Otherwise,
you can simply grep the messagexmas.el file for the string
`message-xmas-make-date'.

Re: [XEmacs] problem with date

[Sébastien Kirche]

At 00:10 on Oct 6 2005, Katsumi Yamaoka said :

[date problem with XEmacs]

> > My best guess is that it is caused by the message-make-date...
> 
> Another guess is that you failed to fully install CVS Gnus.
> messagexmas.el is essential to make XEmacs run Gnus, however it
> won't be installed for Emacs.  I suspect you installed CVS Gnus
> using Emacs first and recompiled them using XEmacs. 

Bingo. That's a clever description of my situation.

Indeed I duplicated my gnus  directory installed for emacs to the xemacs
packages, and byte-recompiled the whole thing.

> You will  probably need to know where  message.elc and messagexmas.elc
> come from. To do that:
> 
> M-x locate-library RET message RET
> M-x locate-library RET messagexmas RET
> 
> If message.elc comes from CVS Gnus and messagexmas.elc comes
> from the XEmacs package, it will naturally happen. 

That's it.

> Otherwise, you can simply grep  the messagexmas.el file for the string
> `message-xmas-make-date'.

I tried  to reinstall a fresh Gnus  from the configure, but  I have some
problems :  even with  the --with-xemacs the  configure script  keeps on
configuring  for emacs.  The point  is that  I am  under OSX  and XEmacs
executable is actually  within a XEmacs.app bundle. I  have to study how
the configure script is looking for  the executable to tell him where to
look. 

I tried several --xxxdir settings, but i didn't foind the right one yet.

Unless someone with OSX can tell me ?

Thank you for you advices.
-- 
Sébastien Kirche