From: "Sébastien Kirche" <sebastien.kirche.no@spam.free.fr.invalid>
Subject: Re: [XEmacs] problem with date
Date: Fri, 07 Oct 2005 13:44:08 +0200 [thread overview]
Message-ID: <m2irw94kmv.fsf@seki.fr> (raw)
In-Reply-To: <b4m64sbr361.fsf@jpl.org>
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
prev parent reply other threads:[~2005-10-07 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 15:59 Sébastien Kirche
2005-10-05 1:17 ` Katsumi Yamaoka
2005-10-05 22:48 ` Katsumi Yamaoka
2005-10-07 11:44 ` Sébastien Kirche [this message]
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=m2irw94kmv.fsf@seki.fr \
--to=sebastien.kirche.no@spam.free.fr.invalid \
--cc=sebastien.kirche@free.fr \
/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).