From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Tad <tadfisher@gmail.com>
Cc: 44726@debbugs.gnu.org
Subject: bug#44726: 28.0.50; [feature/native-comp] Provide a mechanism to populate comp-eln-load-path from the environment
Date: Thu, 19 Nov 2020 19:52:15 +0000 [thread overview]
Message-ID: <xjfwnyh9lao.fsf@sdf.org> (raw)
In-Reply-To: <CA+BndftK0Z_-QzTCfaPVXsf4nb2qWgN9VZGz++zrdbeHfYbreA@mail.gmail.com> (Tad's message of "Wed, 18 Nov 2020 13:45:01 -0800")
Tad <tadfisher@gmail.com> writes:
> On Wed, Nov 18, 2020 at 1:41 PM Andrea Corallo <akrl@sdf.org> wrote:
>
>> Other question, shouldn't we use ":" as separator as in PATH? I'm
>> asking because I see in your snippet you don't so I was wondering if
>> that's intentional.
>
> That's not intentional, and thanks for catching that! Yes, ":" should
> be used as the separator.
Last question, what is specific need to filter out empty strings after
splitting?
Andrea
next prev parent reply other threads:[~2020-11-19 19:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 21:05 bug#44726: 28.0.50; [feature/native-comp] Provide a mechanism to populate comp-eln-load-path from the environment Tad
2020-11-18 21:15 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-18 21:20 ` Tad
2020-11-18 21:41 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-18 21:45 ` Tad
2020-11-19 19:52 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-11-19 22:50 ` Tad
2020-11-20 10:03 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-30 23:25 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-20 14:43 ` Stefan Monnier
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=xjfwnyh9lao.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=44726@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=tadfisher@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.