Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: gnus-dired-mode / gnus-load.el
Date: Thu, 07 Feb 2002 17:09:53 -0500	[thread overview]
Message-ID: <2nwuxp7xla.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <v9bsf10xxs.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 07 Feb 2002 22:44:15 +0100")

Reiner Steib <4uce.02.r.steib@gmx.net> writes:

> Hi,
>
> I tried to use gnus-dired-mode with a very recent Gnus:
>
> | Oort Gnus v0.06 [CVS, Thu Feb  7 18:52:27 CET 2002]
> | GNU Emacs 21.1.1 (i586-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
>
> The commentary section of gnus-dired.el says:
>
> ,----[ gnus-dired.el ]
> | ;; This package provides utility functions for intersections of gnus
> | ;; and dired.  To enable the gnus-dired-mode minor mode which will
> | ;; have the effect of installing keybindings in dired-mode, place the
> | ;; following in your ~/.gnus:
> | 
> | ;; (require 'gnus-dired) ;, isn't needed due to autoload cookies
> | ;; (add-hook 'dired-mode-hook 'turn-on-gnus-dired-mode)
> `----
>
> So I just put the add-hook line in my ~/.gnus and typed `C-x d RET'
> after starting gnus. But I got `void-function turn-on-gnus-dired-mode'
> (see below [1] for a complete backtrace).
>
> AFAICS, it should be autoloaded from gnus-load.el:
>
> ,----[ gnus-load.el ]
> | (autoload (quote turn-on-gnus-dired-mode) "gnus-dired" "\
> | Convenience method to turn on gnus-dired-mode." nil nil)
> `----
>
> But apparently gnus-load.el is not loaded when gnus is started [2].
> After a `(require 'gnus-dired)' it works fine. 

I suggest to put (require 'gnus-load) into ~/.emacs when using oGnus
or future development version.

ShengHuo



  reply	other threads:[~2002-02-07 22:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07 21:44 Reiner Steib
2002-02-07 22:09 ` ShengHuo ZHU [this message]
2002-02-07 23:07   ` Reiner Steib
2002-02-07 23:32     ` ShengHuo ZHU
2002-02-08  1:48   ` Benjamin Rutt
2002-05-04 19:06     ` Amos Gouaux

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=2nwuxp7xla.fsf@zsh.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    /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).