[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: setenv
From: |
Andreas Schwab |
Subject: |
Re: setenv |
Date: |
20 Sep 2001 12:02:35 +0200 |
User-agent: |
Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.0.106 |
tfb@conquest.OCF.Berkeley.EDU (Thomas F. Burdick) writes:
|> In Emacs 20 (and 21), setenv modifies process-environment. But it's
|> named after a C function that affects the current process, not just
|> child processes. While it's documented as such, I think it's a
|> misfeature because its name implies other behavior (that it acts like
|> the C function of the same name). This also means there's no way to
|> affect the environment of the currently running Emacs from Elisp.
|>
|> My solution: getenv should be renamed to get-environment, setenv
|> renamed to set-environment, and getenv and setenv changed to behave as
|> their C namesakes.
In which way would get/setenv be different from get/set-environment from
the Lisp programmer's point of view? AFAIK there is no way to directly
access the environment of the Emacs process.
Andreas.
--
Andreas Schwab "And now for something
Andreas.Schwab@suse.de completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
- setenv, Thomas F. Burdick, 2001/09/14
- Re: setenv,
Andreas Schwab <=
- Re: setenv, Eli Zaretskii, 2001/09/20
- Re: setenv, Andreas Schwab, 2001/09/20
- Re: setenv, Eli Zaretskii, 2001/09/20
- Re: setenv, Andreas Schwab, 2001/09/20
- Re: setenv, Eli Zaretskii, 2001/09/20
- Re: setenv, Eli Zaretskii, 2001/09/20
- Re: setenv, Miles Bader, 2001/09/20
- Re: setenv, Eli Zaretskii, 2001/09/20
- Re: setenv, Andreas Schwab, 2001/09/21
- Re: setenv, Richard Stallman, 2001/09/21