unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: platon7pronko@gmail.com, larsi@gnus.org, 41788@debbugs.gnu.org
Subject: bug#41788: 28.0.50; emacsclient -t doesn't work with vipe from moreutils
Date: Mon, 06 Jun 2022 20:03:30 +0300	[thread overview]
Message-ID: <83zgip7mhp.fsf@gnu.org> (raw)
In-Reply-To: <87mtephi8z.fsf@igel.home> (message from Andreas Schwab on Mon, 06 Jun 2022 18:25:00 +0200)

> Resent-From: Andreas Schwab <schwab@linux-m68k.org>
> Original-Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
> Resent-CC: bug-gnu-emacs@gnu.org
> Resent-Sender: help-debbugs@gnu.org
> Cc: Platon Pronko <platon7pronko@gmail.com>, 41788@debbugs.gnu.org
> From: Andreas Schwab <schwab@linux-m68k.org>
> Date: Mon, 06 Jun 2022 18:25:00 +0200
> 
> On Jun 06 2022, Lars Ingebrigtsen wrote:
> 
> > open(STDIN, "</dev/tty") || die "reopen stdin: $!";
> > open(OUT, ">&STDOUT") || die "save stdout: $!";
> > close STDOUT;
> > open(STDOUT, ">/dev/tty") || die "reopen stdout: $!";
> 
> That associates the process with /dev/tty, not the real terminal.  But
> the running Emacs process usually does not have a controlling terminal,
> thus it cannot open /dev/tty.  It needs to know the real terminal to be
> able to open a tty frame on it.

So you are saying that, instead of using "/dev/tty", vipe should use
the actual name of the terminal device, obtained via the equivalent of
the 'tty' command?  Or is this impossible for what vipe wants to do?





  reply	other threads:[~2022-06-06 17:03 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
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 [this message]
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=83zgip7mhp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=41788@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=platon7pronko@gmail.com \
    --cc=schwab@linux-m68k.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 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).