From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
michael.albinus@gmx.de, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: [PATCH] Buffer-local process environments
Date: Mon, 06 Sep 2021 08:17:49 -0700 [thread overview]
Message-ID: <867dftspgi.fsf@stephe-leake.org> (raw)
In-Reply-To: <874kb378km.fsf@gmail.com> (Augusto Stoffel's message of "Thu, 02 Sep 2021 09:14:33 +0200")
Augusto Stoffel <arstoffel@gmail.com> writes:
> On Wed, 1 Sep 2021 at 15:38, Stephen Leake <stephen_leake@stephe-leake.org> wrote:
>
>>>> The GNU ELPA package wisi takes an intermediate approach; it maintains a
>>>> list of project-specific environment variables in the project object,
>>>> and let-binds them in process-environment whenever it runs a process for
>>>> the project.
>>>
>>> If I understand correctly, this works only when launching the WisiToken
>>> program, am I correct?
>>
>> No, any process. In ada-mode, that includes the compiler and the cross
>> reference tool.
>
> Okay, I've found wisi-prj.el, but I can't find any documentation for the
> process environment aspect of it. Therefore it's still not clear to me
> how it relates with this discussion.
The cl-defstruct wisi-prj has these slots (among others):
compile-env
;; List of strings NAME=VALUE for `compilation-environment'; used
;; when running the compiler or makefile. Also prepended to
;; `process-environment' when the project file is parsed, or when
;; the project file is used by a tool in an external process.
file-env
;; Environment (list of strings NAME=VALUE) set in project file;
;; prepended to `process-environment' running tools in an external
;; process.
> Wisi claims to be a code-parsing tool.
Actually it's an elisp interface to an external generated parser,
allowing Emacs to take advantage of the parser.
> Are there any new ideas in it that pertain to project-wise process
> environments specifically and could be adopted more broadly, say by
> project.el?
file-env (probably renamed to project-env) would make sense in any
project that uses environment variables.
compile-env would make sense in any project that runs a compiler, or
uses compilation-mode to run a tool.
I guess both would be cl-defgeneric functions, with default
implementation returning nil.
--
-- Stephe
next prev parent reply other threads:[~2021-09-06 15:17 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 10:56 Buffer-local process environments Augusto Stoffel
2021-04-29 12:30 ` Eli Zaretskii
2021-04-29 12:40 ` Augusto Stoffel
2021-04-29 12:52 ` Eli Zaretskii
2021-04-29 13:06 ` Augusto Stoffel
2021-04-29 14:02 ` Stefan Monnier
2021-04-29 17:26 ` Augusto Stoffel
2021-04-29 17:34 ` Michael Albinus
2021-04-30 7:29 ` Augusto Stoffel
2021-04-30 7:48 ` Michael Albinus
2021-04-30 15:19 ` Augusto Stoffel
2021-04-30 15:51 ` Michael Albinus
2021-05-02 6:13 ` Augusto Stoffel
2021-05-08 17:51 ` Michael Albinus
2021-05-09 5:06 ` Augusto Stoffel
2021-05-09 16:38 ` Michael Albinus
2021-08-28 12:28 ` [PATCH] " Augusto Stoffel
2021-08-28 12:37 ` Eli Zaretskii
2021-08-28 12:55 ` Augusto Stoffel
2021-09-01 10:42 ` Stephen Leake
2021-09-01 10:56 ` Augusto Stoffel
2021-09-01 22:38 ` Stephen Leake
2021-09-02 7:14 ` Augusto Stoffel
2021-09-06 15:17 ` Stephen Leake [this message]
2021-08-28 14:06 ` Arthur Miller
2021-08-28 14:33 ` Eli Zaretskii
2021-08-28 15:27 ` Arthur Miller
2021-08-28 15:38 ` Eli Zaretskii
2021-08-28 16:48 ` Arthur Miller
2021-08-28 15:39 ` Augusto Stoffel
2021-08-28 16:43 ` Arthur Miller
2021-08-28 12:47 ` Michael Albinus
2021-08-28 12:59 ` Augusto Stoffel
2021-08-28 13:18 ` Michael Albinus
2021-08-28 13:54 ` Augusto Stoffel
2021-08-28 14:05 ` Stefan Monnier
2021-08-28 15:19 ` Augusto Stoffel
2021-04-30 15:32 ` Augusto Stoffel
2021-04-30 15:55 ` Michael Albinus
2021-04-29 15:37 ` Michael Albinus
2021-04-29 17:31 ` Augusto Stoffel
2021-04-29 17:44 ` Michael Albinus
2021-04-30 7:00 ` Augusto Stoffel
2021-04-30 7:25 ` Michael Albinus
2021-05-02 13:45 ` Stephen Leake
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=867dftspgi.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=arstoffel@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=monnier@iro.umontreal.ca \
/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).