From: Eli Zaretskii <eliz@gnu.org>
To: Arthur Miller <arthur.miller@live.com>
Cc: michael.albinus@gmx.de, arstoffel@gmail.com,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [PATCH] Buffer-local process environments
Date: Sat, 28 Aug 2021 18:38:31 +0300 [thread overview]
Message-ID: <83o89hmvew.fsf@gnu.org> (raw)
In-Reply-To: <AM9PR09MB4977BC02912D4917099C527596C99@AM9PR09MB4977.eurprd09.prod.outlook.com> (message from Arthur Miller on Sat, 28 Aug 2021 17:27:18 +0200)
> From: Arthur Miller <arthur.miller@live.com>
> Cc: arstoffel@gmail.com, michael.albinus@gmx.de, monnier@iro.umontreal.ca,
> emacs-devel@gnu.org
> Date: Sat, 28 Aug 2021 17:27:18 +0200
>
> >> (defun emacs-vision--get-date ()
> >> (let ((lang (concat "LANG=" emacs-vision-locale))
> >> (lctime (concat "LC_TIME=" emacs-vision-locale)))
> >> (with-temp-buffer
> >> (insert
> >> (shell-command-to-string
> >> (concat lang lctime " date +'%A, %B %d'")))
> >> (goto-char (- (point-max) 1))
> >> (buffer-substring-no-properties
> >> (line-beginning-position) (line-end-position)))))
> >>
> >> Do I understand correctly, this patch will let me have separate process
> >> environment, so I could use separate environment variables in subprocess?
> >
> > Yes, but that's not what you were asking about, I believe.
>
> Now you make me confused again :). I want my process to use different env for
> LANG and LC_TIME, but Emacs should continue to work with old values. Concretely
> I want english date string, but my Emacs should continue to use swedish for it's
> normal use.
>
> So if I let-bind, it will be reflected only localy in that let scope, and the
> subprocess will inherit that local environment too? That is what I want, and why
> I went via shell command. Forgive me if I am confused. I hope what you said
> above is what I want :-).
The code above changes the environment only of that single shell
command. Moreover, it's non-portable: it only works with Posix
shells, and only for commands invoked via those shells. Local
modifications of process-environment are free from these limitations.
next prev parent reply other threads:[~2021-08-28 15:38 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
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 [this message]
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=83o89hmvew.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arstoffel@gmail.com \
--cc=arthur.miller@live.com \
--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).