Gnus development mailing list
 help / color / mirror / Atom feed
From: dsg@linus.mitre.org (David S. Goldberg)
Subject: push order in dgnushack
Date: 06 Oct 1997 14:39:05 -0400	[thread overview]
Message-ID: <m1bg1qelos6.fsf@blackbird.mitre.org> (raw)

I submit that the following in dgnushack.el:

(push "." load-path)
(push "~/lisp/custom" load-path)
(require 'lpath)

is backwards.  The push lines should be reversed.  Even if someone can
prove to me that the broken compilation with the above order and good
compilation after changing the order was coincidence, it's clear that
the desired lpath.el is in "." and therefore "." should be first on
the load path.  I suspect that this is a problem for anyone who is
using custom as a third party package.  I realize this won't be an
issue for me when I finally find time to install Emacs 20, but I can't
be the only one whose going to be stuck at 19.34 for at least a few
more weeks.

--
Dave Goldberg
Post: The Mitre Corporation\MS B305\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org


             reply	other threads:[~1997-10-06 18:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-06 18:39 David S. Goldberg [this message]
1997-10-12 19:26 ` Lars Magne Ingebrigtsen

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=m1bg1qelos6.fsf@blackbird.mitre.org \
    --to=dsg@linus.mitre.org \
    --cc=dsg@mitre.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).