Gnus development mailing list
 help / color / mirror / Atom feed
From: Jack Twilley <jmt+usenet@twilley.org>
Subject: Re: message keymap not loading
Date: Fri, 05 Oct 2001 11:29:00 -0700	[thread overview]
Message-ID: <863d4yrleb.fsf@duchess.twilley.org> (raw)
In-Reply-To: <vafitduo6j8.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>

>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

Kai> What happens when you M-x load-library RET message RET, then go
Kai> to a new buffer and do M-x message-mode RET (check the key C-c
Kai> C-c)?  And after M-x load-library RET message.el RET, then
Kai> another new buffer, then M-x message-mode RET, then C-h k C-c
Kai> C-c?

Jack>  The first sequence gives me nothing useful.

Kai> I presume that means that C-c C-c is undefined.

Yes, you presume correctly.

Jack> The second one fails because no library named message.el is in
Jack> the path.  I am doing all of these with my current XEmacs
Jack> session where I'm also running Gnus, if that matters.

Kai> You don't have message.el?  This is bad.  Who knows what might be
Kai> the problem in this case.  If you had the *.el file, you could
Kai> look at it to see whether it contains garbage, but that's not so
Kai> easy if you only have the *.elc file.

Kai> How did you install XEmacs and Gnus?  Do you think there is a way
Kai> to get at the *.el files?  Maybe just reinstall Gnus...

I installed XEmacs out of ports.  I mentioned earlier in the thread
how I installed Gnus.  Here's the current script I use to install CVS
Gnus into my ~/.xemacs/packages directory:

--begin script--
#!/bin/sh
make distclean
cvs update
./configure --with-xemacs --infodir=/home/jmt/.xemacs/packages/info/gnus --with-lispdir=/home/jmt/.xemacs/packages/lisp/gnus --with-etcdir=/home/jmt/.xemacs/packages/etc/gnus
gmake
(cd lisp && for pkg in gnus message smiley; do xemacs -batch -eval \("setq autoload-package-name \"$pkg\""\) -f batch-update-directory . ; done && xemacs -batch -f Custom-make-dependencies ./)
rm -rf /home/jmt/.xemacs/packages/*/gnus
gmake install
--end script--

Kai> kai -- Abort this operation?  [OK] [Cancel]

Jack.
(updating Gnus now)
-- 
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash



  reply	other threads:[~2001-10-05 18:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03 18:34 Jack Twilley
2001-10-03 18:50 ` Simon Josefsson
2001-10-03 18:56   ` Jack Twilley
2001-10-04  5:03     ` Amos Gouaux
2001-10-04  8:04 ` Kai Großjohann
2001-10-04 16:42   ` Jack Twilley
2001-10-04 17:08     ` Kai Großjohann
2001-10-04 17:28       ` Jack Twilley
2001-10-04 18:01         ` David S. Goldberg
2001-10-04 19:35           ` Jack Twilley
2001-10-04 21:16         ` Kai Großjohann
2001-10-04 21:50           ` Jack Twilley
2001-10-05  8:06             ` Kai Großjohann
2001-10-05 18:29               ` Jack Twilley [this message]
2001-10-05 19:07                 ` Kai Großjohann
2001-10-08  8:13 ` Didier Verna
2001-10-08 22:24   ` Jack Twilley
2001-10-09  8:38     ` Didier Verna
2001-10-09 17:32       ` Jack Twilley
2001-10-09 17:57         ` ShengHuo ZHU

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=863d4yrleb.fsf@duchess.twilley.org \
    --to=jmt+usenet@twilley.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).