all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Fri, 12 Nov 2021 04:26:55 +0100	[thread overview]
Message-ID: <87y25u2gw0.fsf@gnus.org> (raw)
In-Reply-To: <CAKWVi_TRJcOpJ011UvHoBLQq=YvcrTQYwQwXMqk9HG7TvaZm+g@mail.gmail.com> (Bryan C. Mills's message of "Thu, 11 Nov 2021 12:23:38 -0500")

"Bryan C. Mills" <bcmills@google.com> writes:

> I did post the complete output: the pipeline `cat script.el | emacs
> --no-init-file --no-site-file --script /dev/stdin` did not produce any
> output whatsoever for my reproducer. (Nothing to stdout, nothing to
> stderr.)

Ah, I see.

I tracked down what's causing this new problem and fixed that, and after
doing that, I can confirm that your patch fixes the problem with
/dev/stdin-as-a-pipe, so I've pushed it to Emacs 29.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-11-12  3:26 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
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 [this message]

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=87y25u2gw0.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 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.