Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <kai@emptydomain.de>
Subject: netrc trouble: conflict between Gnus and Emacs version
Date: Sat, 20 Nov 2004 17:46:17 +0100	[thread overview]
Message-ID: <866540wjs6.fsf@ketchup.de.uu.net> (raw)

I use Emacs from CVS and Gnus from CVS.  I have the following code in
~/.emacs to set up load-path and suchlike:

;; Gnus
(when (file-directory-p "~/work/gnu/gnus/")
  (add-to-list 'load-path "~/work/gnu/gnus/lisp/")
  (require 'gnus-load)
  (require 'gnus-namazu "../contrib/gnus-namazu")
  (add-to-list 'Info-default-directory-list "~/work/gnu/gnus/texi/"))

Further Gnus configuration is in ~/.gnus.

I recently had to add (load "netrc") to the beginning of that file to
make things work.

I think a similar issue was discussed in the thread "Problems with
reading mail via imap".

Shouldn't gnus-load arrange for the right netrc to be loaded?

[time passes]

Ah!  It turns out that I require dired and dired-x earlier on in my
~/.emacs file.  Never thought that those would interfere.

So is it pilot error after all?

Kai



             reply	other threads:[~2004-11-20 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-20 16:46 Kai Grossjohann [this message]
2004-11-20 22:56 ` Simon Josefsson

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=866540wjs6.fsf@ketchup.de.uu.net \
    --to=kai@emptydomain.de \
    /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).