From: dalanicolai <dalanicolai@gmail.com>
To: 57854@debbugs.gnu.org
Subject: bug#57854: Test result to previous suggestion
Date: Fri, 16 Sep 2022 12:05:58 +0200 [thread overview]
Message-ID: <CACJP=3mBgqHmPOZX9HApv3JBj8SepGmLnGxQAnC3kKjSQvF6fg@mail.gmail.com> (raw)
In-Reply-To: <CACJP=3nYUawxhZVkjLEqOB=zmgTr7w=_T24mbzSMhgzq=CrABw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
In my previous message, I suggested that python might determine that some
input was given.
I have tested it now by letting the command print a message in case input
was determined,
and indeed, while the terminal still produces the error, using
`shell-command-to-string` now
returns the printed message. So I guess the 'hypothesis' was correct.
[-- Attachment #2: Type: text/html, Size: 435 bytes --]
next prev parent reply other threads:[~2022-09-16 10:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 9:39 bug#57854: 29.0.50; Different exit code in Emacs and terminal for identical process dalanicolai
2022-09-16 10:00 ` bug#57854: some extra info from inspecting the `pdftocio` package dalanicolai
2022-09-16 10:39 ` Eli Zaretskii
2022-09-16 19:16 ` dalanicolai
2022-09-16 11:00 ` bug#57854: 29.0.50; Different exit code in Emacs and terminal for identical process Eli Zaretskii
2022-09-16 19:29 ` dalanicolai
2022-09-16 19:44 ` dalanicolai
2022-09-17 6:10 ` Eli Zaretskii
2022-09-17 13:37 ` dalanicolai
2022-09-17 13:56 ` Eli Zaretskii
2022-09-17 14:16 ` dalanicolai
2022-09-17 14:42 ` Eli Zaretskii
2022-09-16 10:05 ` dalanicolai [this message]
2022-09-16 10:12 ` bug#57854: good to know dalanicolai
2022-09-16 10:46 ` bug#57854: 29.0.50; Different exit code in Emacs and terminal for identical process Eli Zaretskii
2022-09-16 10:35 ` Eli Zaretskii
[not found] ` <CACJP=3k9N5u1vY9Q2sM9angpcLEA7NMeLiFbvPdFAZfX+XbGYg@mail.gmail.com>
2022-09-17 6:05 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACJP=3mBgqHmPOZX9HApv3JBj8SepGmLnGxQAnC3kKjSQvF6fg@mail.gmail.com' \
--to=dalanicolai@gmail.com \
--cc=57854@debbugs.gnu.org \
/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.