From: kobarity <kobarity@gmail.com>
To: Matthias Meulien <orontee@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Augusto Stoffel <arstoffel@gmail.com>,
64397@debbugs.gnu.org
Subject: bug#64397: 29.0.91; Limited configuration of commands based on python-interpreter
Date: Sun, 09 Jul 2023 21:17:48 +0900 [thread overview]
Message-ID: <eke7h6qd5leb.wl-kobarity@gmail.com> (raw)
In-Reply-To: <87h6qe2wri.fsf@gmail.com>
Matthias Meulien wrote:
>
> kobarity <kobarity@gmail.com> writes:
>
> > (...) How about the following descriptions?
> >
> > python-interpreter
> > Python interpreter for noninteractive use.
> > python-interpreter-args
> > Arguments for the Python interpreter for noninteractive use.
> > python-shell-interpreter
> > Python interpreter for interactive use.
> > python-shell-interpreter-args
> > Arguments for the Python interpreter for interactive use.
>
> I like it. But you skipped python-shell-interpreter-interactive-arg...
Sorry, I forgot about that.
`python-shell-interpreter-interactive-arg' is used only for prompt
detection, and its docstring has only one line:
Interpreter argument to force it to run interactively.
I think we can leave it as is, but if we want to improve it, how about
adding the second line? I could not shorten it to fit on one line.
Interpreter argument to force it to run interactively.
This is used only for prompt detection.
next prev parent reply other threads:[~2023-07-09 12:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 6:33 bug#64397: 29.0.91; Limited configuration of commands based on python-interpreter Matthias Meulien
2023-07-01 16:10 ` Matthias Meulien
2023-07-06 7:21 ` Eli Zaretskii
2023-07-06 14:51 ` kobarity
2023-07-07 8:09 ` Augusto Stoffel
2023-07-06 20:39 ` Matthias Meulien
2023-07-08 7:52 ` Eli Zaretskii
2023-07-08 11:28 ` kobarity
2023-07-08 13:50 ` Eli Zaretskii
2023-07-08 16:28 ` Matthias Meulien
2023-07-09 12:17 ` kobarity [this message]
2023-07-13 5:50 ` Eli Zaretskii
2023-07-13 21:44 ` Matthias Meulien
2023-07-15 8:30 ` Eli Zaretskii
2023-07-17 19:17 ` Matthias Meulien
2023-07-20 16:02 ` Eli Zaretskii
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=eke7h6qd5leb.wl-kobarity@gmail.com \
--to=kobarity@gmail.com \
--cc=64397@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=eliz@gnu.org \
--cc=orontee@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).