unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: esq@lawlist.com, andlind@gmail.com, 21104@debbugs.gnu.org
Subject: bug#21104: 25.0.50; relative paths are added to load-path without -nsl (bug#21104)
Date: Tue, 08 Dec 2015 12:54:52 -0500	[thread overview]
Message-ID: <6z4mfsu8pf.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83h9jtc4eo.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 08 Dec 2015 18:05:03 +0200")

Eli Zaretskii wrote:

> Does the patch below solve the problem?

If I read configure correctly, the same issue will occur on any platform
if configured with --enable-locallisppath=no, so you could try it out.

Which suggests this (undocumented?) option has never worked properly,
so one option is simply to remove that alternative and not allow
locallispath to be empty, and choose a better default on OS X.
One can always call emacs --no-site-lisp for the same effect.

> (Does anyone know why we call decode_env_path with last argument zero
> in this case? 

The last argument is a relatively new addition. Before it existed
decode_env_path behaved like it was zero. So when adding the new
argument the default was to use zero. Again, this suggests empty
locallispath never worked as intended.

But like Andreas, my guess would be that "." and nil are equivalent here.
Maybe you could just special-case it so that PATH_SITELOADSEARCH empty
acts like no_site_lisp is set?





  parent reply	other threads:[~2015-12-08 17:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 17:26 bug#21104: 25.0.50; relative paths are added to load-path without -nsl Sam Steingold
2015-07-21 17:41 ` bug#21104: workaround for the bug Sam Steingold
2015-07-22 18:02 ` bug#21104: 25.0.50; relative paths are added to load-path without -nsl Glenn Morris
2015-07-22 18:26   ` Sam Steingold
2015-07-22 18:37     ` Glenn Morris
2015-07-22 19:41       ` Sam Steingold
2015-07-22 21:58         ` Glenn Morris
2015-12-07 19:00 ` bug#21104: 25.0.50; relative paths are added to load-path without -nsl (bug#21104) Anders Lindgren
2015-12-07 19:33   ` Eli Zaretskii
2015-12-07 22:09     ` Anders Lindgren
2015-12-08  1:22       ` Glenn Morris
2015-12-08  1:32         ` Glenn Morris
2015-12-08 16:05         ` Eli Zaretskii
2015-12-08 17:06           ` Andreas Schwab
2015-12-08 17:40             ` Eli Zaretskii
2015-12-08 18:16               ` Andreas Schwab
2015-12-08 17:54           ` Glenn Morris [this message]
2015-12-08 18:20             ` Eli Zaretskii
2015-12-08 19:16               ` Anders Lindgren
2015-12-08 19:21                 ` Glenn Morris
2015-12-08 20:03                   ` Anders Lindgren
2015-12-09  8:49                     ` Andreas Schwab
2015-12-08 20:05                   ` Eli Zaretskii
2015-12-08  3:35       ` Eli Zaretskii
2015-12-09 10:33 ` bug#21104: Don't add "." to load-path -- fixed Anders Lindgren

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=6z4mfsu8pf.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=21104@debbugs.gnu.org \
    --cc=andlind@gmail.com \
    --cc=eliz@gnu.org \
    --cc=esq@lawlist.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.
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).