From: Johan Andersson <johan.rejeep@gmail.com>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Reset Emacs state
Date: Tue, 2 Mar 2010 12:06:48 +0000 [thread overview]
Message-ID: <929ccd881003020406n70c62188ha649954100b7eda2@mail.gmail.com> (raw)
In-Reply-To: <e01d8a51003020350r27493dew739657ccbfb43f3f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
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.
>
[-- Attachment #2: Type: text/html, Size: 1392 bytes --]
next prev parent reply other threads:[~2010-03-02 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 10:41 Reset Emacs state Johan Andersson
2010-03-02 10:50 ` Lennart Borgman
2010-03-02 11:03 ` Johan Andersson
2010-03-02 11:18 ` Lennart Borgman
2010-03-02 11:48 ` Johan Andersson
2010-03-02 11:50 ` Lennart Borgman
2010-03-02 12:06 ` Johan Andersson [this message]
2010-03-02 12:21 ` Lennart Borgman
2010-03-02 12:48 ` Johan Andersson
2010-03-02 20:16 ` Lennart Borgman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=929ccd881003020406n70c62188ha649954100b7eda2@mail.gmail.com \
--to=johan.rejeep@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=lennart.borgman@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.