From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh-Users List <zsh-users@zsh.org>,
Pier Paolo Grassi <pierpaolog@gmail.com>
Subject: Re: read with redirected stdin
Date: Sun, 8 Jan 2023 15:42:03 +0100 [thread overview]
Message-ID: <CAN=4vMoSBJ=Kh6mCf2iS00Mxmhfn_C_a8exeRawiKVziRX+f_g@mail.gmail.com> (raw)
In-Reply-To: <20230108142157.GM8411@tarpaulin.shahaf.local2>
On Sun, Jan 8, 2023 at 3:22 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Roman Perepelitsa wrote on Sun, Jan 08, 2023 at 14:48:24 +0100:
> >
> > Doesn't $TTY already provide a better alternative?
>
> $TTY could be unset or set to another value without affecting the
> controlling terminal.
Paranoid scripts can do this:
zsh -fc 'print -r -- $TTY'
However, if one is overriding TTY, then they perhaps want to affect
scripts that read it (similarly to overriding HOME or HOST). In any
case, scripts can decide whether to pick up $TTY that might have been
altered or use the paranoid construct from above.
> Anyway, I suppose I should revise my point to 'Can we determine at the C
> level whether we have a controlling terminal more reliably than by
> checking $TTY, and if so, should we expose that to scripts'.
Zsh already knows how to set TTY, so the answer to the first question
must be "yes".
For the second question it would be nice to have a use case that
cannot already be solved by $TTY.
Roman.
next prev parent reply other threads:[~2023-01-08 14:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 13:31 Pier Paolo Grassi
2023-01-07 13:44 ` Roman Perepelitsa
2023-01-07 17:21 ` Pier Paolo Grassi
2023-01-07 17:31 ` Roman Perepelitsa
2023-01-07 17:36 ` Pier Paolo Grassi
2023-01-07 17:52 ` Roman Perepelitsa
2023-01-08 13:23 ` Daniel Shahaf
2023-01-08 13:48 ` Roman Perepelitsa
2023-01-08 14:21 ` Daniel Shahaf
2023-01-08 14:42 ` Roman Perepelitsa [this message]
2023-01-07 17:33 ` Pier Paolo Grassi
2023-01-08 4:28 ` Jim
2023-01-08 4:44 ` Pier Paolo Grassi
2023-01-08 21:18 ` Jim
2023-01-09 16:01 ` Pier Paolo Grassi
2023-01-09 22:47 ` Jim
2023-01-10 2:46 ` Bart Schaefer
2023-01-10 6:03 ` Pier Paolo Grassi
2023-01-08 14:44 ` Ray Andrews
2023-01-08 15:06 ` Roman Perepelitsa
2023-01-08 20:23 ` Ray Andrews
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='CAN=4vMoSBJ=Kh6mCf2iS00Mxmhfn_C_a8exeRawiKVziRX+f_g@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=pierpaolog@gmail.com \
--cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).