zsh-users
 help / color / mirror / code / Atom feed
From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: read with redirected stdin
Date: Sat, 7 Jan 2023 18:36:46 +0100	[thread overview]
Message-ID: <CAP+y1xC+bk5=Poax3-6eXWUCLgk3R08DcwmhqX30dTj4b3FY1g@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMqDbbQnimVEbhboTXNOvwrEC97Cjijc3_Q+_q0kUDfN6A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 917 bytes --]

oh ok, that seems what I want (except I don't want to read from stdin when
there is no tty, just assume a negative answer, but that's trivial).
I am still wondering,  what can be a way to simulate the situation of a
script launched by cron, where there is no tty and no other mean for read
to connect to a terminal?
thanks!

Pier Paolo Grassi


Il giorno sab 7 gen 2023 alle ore 18:31 Roman Perepelitsa <
roman.perepelitsa@gmail.com> ha scritto:

> 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
>
> Roman.
>

[-- Attachment #2: Type: text/html, Size: 1585 bytes --]

  reply	other threads:[~2023-01-07 17:39 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 [this message]
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
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='CAP+y1xC+bk5=Poax3-6eXWUCLgk3R08DcwmhqX30dTj4b3FY1g@mail.gmail.com' \
    --to=pierpaolog@gmail.com \
    --cc=roman.perepelitsa@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).