From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: npostavs@users.sourceforge.net, 23779@debbugs.gnu.org,
schwab@linux-m68k.org, eggert@cs.ucla.edu
Subject: bug#23779: 25.0.95; consing "SHELLVAR" onto process-environment doesn't remove it from subprocess env
Date: Fri, 17 Jun 2016 23:10:37 +0300 [thread overview]
Message-ID: <83mvmjbmpu.fsf@gnu.org> (raw)
In-Reply-To: <54d442d1-0053-6966-9cd6-9540448eb31f@yandex.ru> (message from Dmitry Gutov on Fri, 17 Jun 2016 22:01:19 +0300)
> Cc: eggert@cs.ucla.edu, schwab@linux-m68k.org,
> npostavs@users.sourceforge.net, 23779@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Fri, 17 Jun 2016 22:01:19 +0300
>
> On 06/17/2016 08:06 PM, Eli Zaretskii wrote:
>
> > Now that 'push' works, why do we need setenv for that?
>
> So that the user doesn't have to (push "VAR=value"), or (push "VAR="),
> or know the difference between the latter and (push "VAR").
>
> setenv is a better abstraction. In fact, if you use it, you don't even
> have to know the format of process-environment.
We will have to agree to disagree on this one.
> >> So, what are the downsides?
> >
> > That there's no way of changing the environment permanently?
>
> The environment is changes as a result. It just doesn't modify the
> original list, and, as such, contains duplicate values for the changed
> variables.
What do I do if I do want to change the original one?
> > I'm not sure I see why that is nicer.
>
> Do you know what value "PAGER=" assigns to the variable PAGER?
Not sure what that means, or why do you ask that.
next prev parent reply other threads:[~2016-06-17 20:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 3:33 bug#23779: 25.0.95; consing "SHELLVAR" onto process-environment doesn't remove it from subprocess env Noam Postavsky
2016-06-17 7:11 ` Eli Zaretskii
2016-06-17 12:17 ` Dmitry Gutov
2016-06-17 14:01 ` Eli Zaretskii
2016-06-17 14:12 ` Dmitry Gutov
2016-06-17 14:19 ` Eli Zaretskii
2016-06-17 14:47 ` Dmitry Gutov
2016-06-17 16:52 ` Andreas Schwab
2016-06-17 16:55 ` Dmitry Gutov
2016-06-17 17:06 ` Eli Zaretskii
2016-06-17 19:01 ` Dmitry Gutov
2016-06-17 20:10 ` Eli Zaretskii [this message]
2016-06-17 21:26 ` Dmitry Gutov
2016-06-18 7:51 ` Eli Zaretskii
2016-06-18 1:36 ` Noam Postavsky
2016-06-18 1:44 ` Dmitry Gutov
2016-06-19 2:27 ` Paul Eggert
2016-06-19 15:01 ` Eli Zaretskii
2016-06-19 22:53 ` Paul Eggert
2016-06-20 14:21 ` Eli Zaretskii
2016-06-21 13:53 ` Dmitry Gutov
2016-06-21 15:21 ` Eli Zaretskii
2016-06-21 15:24 ` Dmitry Gutov
2016-06-21 16:12 ` Eli Zaretskii
2016-06-21 23:05 ` Dmitry Gutov
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=83mvmjbmpu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23779@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=npostavs@users.sourceforge.net \
--cc=schwab@linux-m68k.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 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).