From: Lars Ingebrigtsen <larsi@gnus.org>
To: lars@nocrew.org
Cc: 13924@debbugs.gnu.org
Subject: bug#13924: 24.2; Recompile and compile-environment
Date: Wed, 14 Aug 2019 23:09:16 -0700 [thread overview]
Message-ID: <878srvyn77.fsf@mouse.gnus.org> (raw)
In-Reply-To: <85y5dufge9.fsf@junk.nocrew.org> (lars@nocrew.org's message of "Mon, 11 Mar 2013 10:13:34 +0100")
lars@nocrew.org writes:
> This lisp code starts a compilation with the provided environment:
>
> (let ((compilation-environment '("FOO=BAR")))
> (compile "printenv"))
>
> Typing 'g' or 'M-x recompile' in the *compilation* buffer starts
> another compilation with the same environment. This is evident since
> the printenv output includes FOO=BAR.
>
> However, typing 'M-x recompile' in some other buffer will not use the same
> environment as the first compilation. FOO=BAR is no longer present.
>
> This behaviour may be a bug or a feature. However, in my opinion it
> renders the combination of 'compilation-environment' and 'recompile'
> somewhat useless.
I think this behaviour is probably as intended. As the doc string to
`recompile' says:
--
If this is run in a Compilation mode buffer, re-use the arguments from the
original use. Otherwise, recompile using ‘compile-command’.
--
I think that implies that the `compilation-environment' isn't reused,
either.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-15 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 9:13 bug#13924: 24.2; Recompile and compile-environment lars
2019-08-15 6:09 ` Lars Ingebrigtsen [this message]
2019-08-15 6:17 ` Lars Brinkhoff
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=878srvyn77.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=13924@debbugs.gnu.org \
--cc=lars@nocrew.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.