From: Lars Ingebrigtsen <larsi@gnus.org>
To: Platon Pronko <platon7pronko@gmail.com>
Cc: 41788@debbugs.gnu.org
Subject: bug#41788: 28.0.50; emacsclient -t doesn't work with vipe from moreutils
Date: Mon, 06 Jun 2022 16:00:39 +0200 [thread overview]
Message-ID: <87wndtuc1k.fsf@gnus.org> (raw)
In-Reply-To: <288bd9d3-1c7c-e3fa-fd02-e1287f8329ec@gmail.com> (Platon Pronko's message of "Wed, 10 Jun 2020 16:19:45 +0300")
Platon Pronko <platon7pronko@gmail.com> writes:
> $ echo a | EDITOR='emacsclient -t' vipe
> *ERROR*: Could not open file: /dev/tty
> emacsclient -t exited nonzero, aborting
>
> (vipe is a tool from moreutils, used to insert an editor in the middle of
> the pipeline)
>
> Looking inside vipe source I see that it reopens stdin before calling
> the EDITOR:
>
> close STDIN;
> open(STDIN, "</dev/tty") || die "reopen stdin: $!";
>
> If I use for example nano instead of emacsclient -t then everything works correctly.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
This problem is still present in Emacs 29. Does anybody understand
where the misbehaviour between this STDIN redirect and what emacsclient
is complaining about can be fixed?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-06 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 13:19 bug#41788: 28.0.50; emacsclient -t doesn't work with vipe from moreutils Platon Pronko
2022-06-06 14:00 ` Lars Ingebrigtsen [this message]
2022-06-06 14:44 ` Andreas Schwab
2022-06-06 14:49 ` Lars Ingebrigtsen
2022-06-06 16:25 ` Andreas Schwab
2022-06-06 17:03 ` Eli Zaretskii
2022-06-06 17:43 ` Andreas Schwab
2022-06-14 4:38 ` Platon Pronko
2022-06-14 11:26 ` Eli Zaretskii
2022-06-06 17:07 ` Lars Ingebrigtsen
2022-06-06 17:40 ` Andreas Schwab
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=87wndtuc1k.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=41788@debbugs.gnu.org \
--cc=platon7pronko@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).