From: Eli Zaretskii <eliz@gnu.org>
To: Juan Jose Garcia-Ripoll <juanjose.garciaripoll@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Problems with call-process (= identifying run-python issues)
Date: Tue, 18 Aug 2020 19:24:11 +0300 [thread overview]
Message-ID: <83wo1vexck.fsf@gnu.org> (raw)
In-Reply-To: <CANejTzpQdx=7gzbkV-gzoyFKHx+U1sKy2Uid13g6hpwCa_GnRA@mail.gmail.com> (message from Juan Jose Garcia-Ripoll on Tue, 18 Aug 2020 17:54:35 +0200)
[Please use Reply All to keep the list on the CC.]
> From: Juan Jose Garcia-Ripoll <juanjose.garciaripoll@gmail.com>
> Date: Tue, 18 Aug 2020 17:54:35 +0200
>
> The recipe was in my previous email. I never mention Python other than in the subject (it is not used by the
> tests). It only uses pure Emacs, emacs-lisp (one script) and one command line script (chain.cmd). The text
> in "foo" is arbitrary. It is a Python script, but it can be anything.
Is it all needed? If so, can you explain its role here?
> Option A:
> 1. Save files with the specified names and locations
> 2. Open a command line processor (cmd.exe or PowerShell)
> 3. Invoke "runemacs -Q --load c:\Users\juanj\Downloads\test.el"
>
> Option B:
> 1. Save files with the specified names
> 2. Press Windows Key + R (to enter commands)
> 2. Enter "runemacs -Q --load c:\Users\juanj\Downloads\test.el"
Then I'm afraid I don't understand what the script chain.cmd does and
what it expects from Emacs or the user. Can you please take me though
this recipe one step at a time?
Thanks.
next prev parent reply other threads:[~2020-08-18 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 13:36 Problems with call-process (= identifying run-python issues) Juan José García-Ripoll
2020-08-18 15:41 ` Eli Zaretskii
[not found] ` <CANejTzpQdx=7gzbkV-gzoyFKHx+U1sKy2Uid13g6hpwCa_GnRA@mail.gmail.com>
2020-08-18 16:24 ` Eli Zaretskii [this message]
2020-08-19 8:59 ` Juan José García-Ripoll
2020-08-19 14:41 ` Eli Zaretskii
2020-08-19 16:23 ` Juan José García-Ripoll
2020-08-19 17:03 ` Eli Zaretskii
2020-08-20 7:52 ` Juan José García-Ripoll
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wo1vexck.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juanjose.garciaripoll@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).