[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sourcing environment
From: |
Giorgos Keramidas |
Subject: |
Re: sourcing environment |
Date: |
Wed, 11 Oct 2006 22:00:12 +0300 |
On 2006-10-11 09:07, Tak Ota <address@hidden> 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 :(