From: Dave Abrahams <dave@boostpro.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 12351@debbugs.gnu.org
Subject: bug#12351: 24.1; parse-colon-path turns empty paths into nil
Date: Sun, 30 Dec 2012 22:08:57 -0500 [thread overview]
Message-ID: <m21ue6apfa.fsf@cube.luannocracy.com> (raw)
In-Reply-To: <m2bodb8a7r.fsf@igel.home> (Andreas Schwab's message of "Sun, 30 Dec 2012 23:08:08 +0100")
on Sun Dec 30 2012, Andreas Schwab <schwab-AT-linux-m68k.org> wrote:
> Dave Abrahams <dave@boostpro.com> writes:
>
>> The following function is buggy because of the original bug:
>>
>> (defun osx-plist-update-exec-path ()
>> "Update `exec-path' from the PATH environment variable."
>> (let ((path (getenv "PATH")))
>> (mapc (lambda (dir)
>> (add-to-list 'exec-path dir))
>> (parse-colon-path path)))
>> exec-path)
>
> In which way is this buggy, apart from the fact that it reverses the
> path (which has nothing to do with the behaviour of parse-colon-path)?
It puts nils in exec-path when PATH contains empty elements.
--
Dave Abrahams
BoostPro Computing Software Development Training
http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
next prev parent reply other threads:[~2012-12-31 3:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 18:58 bug#12351: 24.1; parse-colon-path turns empty paths into nil Dave Abrahams
2012-09-16 15:57 ` Chong Yidong
2012-12-30 18:52 ` Glenn Morris
2012-12-30 19:53 ` Dave Abrahams
2012-12-30 20:22 ` Eli Zaretskii
2012-12-30 20:37 ` Dave Abrahams
2012-12-30 22:08 ` Andreas Schwab
2012-12-31 3:08 ` Dave Abrahams [this message]
2012-12-31 7:14 ` Glenn Morris
2012-12-31 12:59 ` Dave Abrahams
2012-12-31 10:07 ` Andreas Schwab
2012-12-31 1:40 ` Wolfgang Jenkner
2012-12-31 3:11 ` Dave Abrahams
2012-12-31 6:56 ` Glenn Morris
2012-12-31 7:07 ` Glenn Morris
2012-12-31 12:58 ` Dave Abrahams
2012-12-31 16:10 ` Wolfgang Jenkner
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=m21ue6apfa.fsf@cube.luannocracy.com \
--to=dave@boostpro.com \
--cc=12351@debbugs.gnu.org \
--cc=schwab@linux-m68k.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).