Re: sourcing environment

[Giorgos Keramidas <keramida@ceid.upatras.gr>]

On 2006-10-11 09:07, Tak Ota <Takaaki.Ota@am.sony.com> wrote:
> Thanks for the suggestion.  I understand what you do but in my case I
> don't prepare the shell scripts but they come as a part of software
> development kit from system silicon vendors.  I used to hand translate
> those shell scripts into custom elisp functions like you show below
> but that soon got too cumbersome to maintain for multiple platforms.
> What I want to automate is the following process without loosing the
> currently opened buffers.
> 
> M-x kill-emacs
> $ source env-xxx.sh
> $ emacs

It looks like you would have to spawn a subshell, save its environment
somewhere, source the script, save the new environment, diff the two
environments and 'translate' the diff output to appropriate

    (setenv "FOO" "bar")

or

    (setenv "FOO" nil)

calls :(