Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Unable to access nndraft:drafts in recent version of Gnus
Date: 02 Oct 2000 18:23:03 -0400	[thread overview]
Message-ID: <lt3dielw6w.fsf@asfast.com> (raw)
In-Reply-To: <vafg0mftucg.fsf@lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> On 01 Oct 2000, Lloyd Zusman wrote:
> 
> > Any ideas about how a `load-path' change could affect the ability
> > for gnus to recognize the `nndrafts:drafts' folder? ... especially
> > given that the only path component I change is the one which points
> > to gnus directory tree, which contains nothing at all but the
> > byte-compiled gnus release ... ???
> 
> How exactly did you change your load-path?  I always install the new
> version of Gnus in some directory, then (add-to-list 'load-path
> "/some/directory/"), and this works nicely.  I don't replace the
> normal Gnus load-path entry, though, I just tack on a new one in front
> of load-path.

I do it just like you do.  I just conditionally use either
"/some/directory1" or "/some/directory2", depending on whether I want
the newest or older version.

And remember, this worked just fine for around a year, and only with
recent CVS downloads did I start having the problem I was reporting.

-- 
 Lloyd Zusman
 ljz@asfast.com



  reply	other threads:[~2000-10-02 22:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-16 22:30 Lloyd Zusman
2000-10-01 12:18 ` Matthias Wiehl
2000-10-01 23:37   ` Lloyd Zusman
2000-10-02 10:23     ` Kai Großjohann
2000-10-02 22:23       ` Lloyd Zusman [this message]
2000-10-03 13:47         ` Kai Großjohann
2000-10-04  3:32           ` Solved! (Was: Unable to access nndraft:drafts in recent version of Gnus) Lloyd Zusman
2000-10-18 14:46   ` Unable to access nndraft:drafts in recent version of Gnus Jari Aalto+mail.emacs

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=lt3dielw6w.fsf@asfast.com \
    --to=ljz@asfast.com \
    /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).