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 14:48:24 +0100 [thread overview]
Message-ID: <CAN=4vMoQTe=3-EhiR-W=LrotHpZcx3yYN9eKOtL3aKcsYZU5Vw@mail.gmail.com> (raw)
In-Reply-To: <20230108132350.GL8411@tarpaulin.shahaf.local2>
On Sun, Jan 8, 2023 at 2:30 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Roman Perepelitsa wrote on Sat, Jan 07, 2023 at 18:31:30 +0100:
> > On Sat, Jan 7, 2023 at 6:22 PM Pier Paolo Grassi <pierpaolog@gmail.com> wrote:
> > >
> > > Thanks, but i don't _always_ redirect stdin.
> >
> > The code will still work (except for the corner case I mentioned).
> >
> > Upon further thinking, the following should work in all cases:
> >
> > if [[ -n $TTY ]]; then
> > # There is a terminal. Read from it.
> > read -k1
> > else
> > # There is no terminal. Read from stdin.
> > read -k1 -u0
> > fi
>
> Would it be useful to provide a ctermid(3) wrapper in zsh/system?
Where would it be useful? Doesn't $TTY already provide a better alternative?
IIRC, ctermid() always returns "/dev/tty" while $TTY points to the real device.
Roman.
next prev parent reply other threads:[~2023-01-08 13:49 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 [this message]
2023-01-08 14:21 ` Daniel Shahaf
2023-01-08 14:42 ` Roman Perepelitsa
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=4vMoQTe=3-EhiR-W=LrotHpZcx3yYN9eKOtL3aKcsYZU5Vw@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).