unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Should lisp/Makefile.in custom-deps be using EMACS or emacs?
Date: Tue, 9 Jul 2002 12:52:03 -0600 (MDT)	[thread overview]
Message-ID: <200207091852.g69Iq3A13934@aztec.santafe.edu> (raw)
In-Reply-To: <87k7o86ycp.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Sat, 06 Jul 2002 21:55:18 -0500)

    >From an strace it looked like this arrangement was causing my
    /usr/share/... custom-deps.el to shadow the newer one in ./lisp

The information you omitted with that "..." is crucial information.
Precisely what directory was that file in?  And what exactly was the
value of load-path?

      I had just
    presumed that the build process would prefer the source tree versions
    of the .el files, and so was surprised when my changes to
    ./lisp/custom-deps.el didn't have any (immediate) effect.

Indeed, for an uninstalled Emacs the files in your source tree should
take precedence over installed files.  Only the site-lisp directories
should take precedence over your source tree.  If that is working
properly, the problem won't happen.  So we need to see if it is
not properly set up.

  parent reply	other threads:[~2002-07-09 18:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-07  2:55 Should lisp/Makefile.in custom-deps be using EMACS or emacs? Rob Browning
2002-07-08 13:56 ` Eli Zaretskii
2002-07-08 14:23   ` Rob Browning
2002-07-08 16:06     ` Eli Zaretskii
2002-07-09 18:52 ` Richard Stallman [this message]
2002-07-23 17:10   ` Rob Browning
2002-07-25 18:07     ` Richard Stallman
2002-07-25 19:45       ` Rob Browning
2002-07-26 18:44         ` Richard Stallman
2002-07-26 19:57           ` Rob Browning
2002-07-27 20:28       ` Rob Browning
2002-07-29  1:12         ` Richard Stallman
2002-07-30 23:01           ` Rob Browning

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200207091852.g69Iq3A13934@aztec.santafe.edu \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).