Re: Reset Emacs state

[Lennart Borgman]

The easiest and most portable is to write a temporary file and load
that file with the -l pararater. The function nxhtmltest-run-Q does
something similar.


On Tue, Mar 2, 2010 at 1:48 PM, Johan Andersson <johan.rejeep@gmail.com> wrote:
> The result from the sub process is actually not as important as passing
> arguments. For now I can live with the exit value. But I still have no idea
> of how to pass values to the sub process. I could use some more hints
> here...
>
> On Tue, Mar 2, 2010 at 12:21 PM, Lennart Borgman <lennart.borgman@gmail.com>
> wrote:
>>
>> I don't understand. Of course you want to pass the variables and
>> values needed for testing to the inferior process. And I guess you
>> want to read the result... ;-)
>>
>> I think we somehow misunderstand each other and I am quite sure you
>> will get this right.
>>
>>
>> On Tue, Mar 2, 2010 at 1:06 PM, Johan Andersson <johan.rejeep@gmail.com>
>> wrote:
>> > I don't see why I would want to do that. I want the inferior emacs
>> > process
>> > to read from the original emacs process. Or pass the variables from
>> > the original emacs process to the inferior emacs process. But why the
>> > other
>> > way around?
>> >
>> > On Tue, Mar 2, 2010 at 11:50 AM, Lennart Borgman
>> > <lennart.borgman@gmail.com>
>> > wrote:
>> >>
>> >> On Tue, Mar 2, 2010 at 12:48 PM, Johan Andersson
>> >> <johan.rejeep@gmail.com>
>> >> wrote:
>> >> > I'm not sure how that would help me? Do you mean something like this?
>> >> >   (let ((var "some variable"))
>> >> >     (call-process "emacs" nil "*scratch*" t "-Q" "--batch" "-l"
>> >> > "~/test.el"))
>> >> > Using call-process would reset the state, but how do I reach
>> >> > var in test.el?
>> >> > I thought that was what you meant with dynamic scoping?
>> >>
>> >>
>> >> Using dynamic scoping and call-process are too different ways. When
>> >> using call-process you have to write some output in the inferior emacs
>> >> process and investigate that in the original emacs process.
>> >
>> >
>
>