From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Bryan C. Mills" <bcmills@google.com>
Cc: 48940@debbugs.gnu.org
Subject: bug#48940: 27.2; regression: "emacs --script /dev/stdin" parses the script incorrectly when /dev/stdin is a pipe
Date: Thu, 11 Nov 2021 06:09:00 +0100 [thread overview]
Message-ID: <87k0hfb7o3.fsf@gnus.org> (raw)
In-Reply-To: <CAKWVi_SYejiEvRyOMT1=AVHvy1jsFnrV08oA0+D25d6JKH6-KQ@mail.gmail.com> (Bryan C. Mills's message of "Mon, 14 Jun 2021 17:37:17 -0400")
"Bryan C. Mills" <bcmills@google.com> writes:
> I tested the fix locally with a small dummy script as input and it
> seems to work, but I can't be confident that there won't be deeper
> bugs. You're welcome to use it as a starting point for a more robust
> fix.
I tried (on Debian/bullseye with Emacs 29), but it doesn't seem to make
any difference here. With or without the patch, I get:
larsi@xo:~/src/emacs/trunk$ emake; cat /tmp/script.el | ./src/emacs -Q --script /dev/stdin
Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" "/proc/162231/fd/pipe:[1065564]")
load("/proc/162231/fd/pipe:[1065564]" nil t t)
command-line-1(("-scriptload" "/dev/stdin"))
command-line()
normal-top-level()
Perhaps something further has changed in the meantime? (You didn't post
an output of the error message you were getting...)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-11-11 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 20:31 bug#48940: 27.2; regression: "emacs --script /dev/stdin" parses the script incorrectly when /dev/stdin is a pipe Bryan C. Mills via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-13 10:26 ` Eli Zaretskii
2021-06-14 21:37 ` Bryan C. Mills via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-11 5:09 ` Lars Ingebrigtsen [this message]
2021-11-11 17:23 ` Bryan C. Mills via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-12 3:26 ` Lars Ingebrigtsen
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=87k0hfb7o3.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=48940@debbugs.gnu.org \
--cc=bcmills@google.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).