From: edgar@openmail.cc
To: help-gnu-emacs@gnu.org
Subject: Re: dir-locals.el process-environment
Date: Sat, 03 Mar 2018 05:40:03 +0000 [thread overview]
Message-ID: <57387a6264a5181af16b0dab2381fead@openmail.cc> (raw)
In-Reply-To: <mailman.23.1520010004.25009.help-gnu-emacs@gnu.org>
> Date: Fri, 02 Mar 2018 09:13:07 -0500
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> To: help-gnu-emacs@gnu.org
> Subject: Re: dir-locals.el process-environment
> Message-ID: <jwv4llybm7s.fsf-monnier+gmane.emacs.help@gnu.org>
>
> Maybe `compile` should take its process-environment from the buffer
> from
> which it is invoked, rather than from the buffer in which the command
> is run.
>
>
> Stefan
It's not a bad idea Stefan, but I am not a fan of buffer-local variables
(if that is what you mean). I find it intrusive for other users. Thanks
for the suggestion.
I still have to check if the debugging will use those environmental
variables :P .
-------------------------------------------------
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
next parent reply other threads:[~2018-03-03 5:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.23.1520010004.25009.help-gnu-emacs@gnu.org>
2018-03-03 5:40 ` edgar [this message]
2018-05-17 19:55 dir-locals.el process-environment edgar
[not found] <mailman.23.1519923605.5908.help-gnu-emacs@gnu.org>
2018-03-02 2:25 ` edgar
2018-03-02 14:13 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2018-02-28 22:18 edgar
2018-03-01 3:32 ` Eli Zaretskii
[not found] <mailman.25.1519750804.23377.help-gnu-emacs@gnu.org>
2018-02-28 5:47 ` edgar
2018-02-28 16:37 ` Eli Zaretskii
2018-02-26 4:30 edgar
2018-02-26 19:15 ` Eli Zaretskii
2018-02-19 18:44 edgar
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=57387a6264a5181af16b0dab2381fead@openmail.cc \
--to=edgar@openmail.cc \
--cc=help-gnu-emacs@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 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.