From: "Lawrence Velázquez" <larryv@zsh.org>
To: johnnonedoe@aol.com
Cc: zsh-workers@zsh.org
Subject: Re: read -u n -t -k Does not work.
Date: Fri, 29 Jul 2022 18:57:52 -0400 [thread overview]
Message-ID: <6f6335b6-03c0-419c-b2ba-4ad22e6cd468@www.fastmail.com> (raw)
In-Reply-To: <549595162.4093300.1659133992108@mail.yahoo.com>
I'm looping the list back in. Please remember to reply to the list
in the future.
On Fri, Jul 29, 2022, at 6:33 PM, johnnonedoe@aol.com wrote:
> Thanks for the timely reply.
>
> macOS Monterey version 12.4
> zsh 5.8.1 (x86_64-apple-darwin21.0)
>
> I don't understand the significance of the lines marked below.
> I am trying to use 'read' in a shell function.
>
> johnnonedoe@aol.com
>
>
> -----Original Message-----
> From: Lawrence Velázquez <larryv@zsh.org>
> To: johnnonedoe@aol.com
> Cc: zsh-workers@zsh.org
> Sent: Fri, Jul 29, 2022 12:40 pm
> Subject: Re: read -u n -t -k Does not work.
>
> On Fri, Jul 29, 2022, at 3:20 PM, johnnonedoe@aol.com wrote:
>> read -t -k
>> Works as expected.
>> read -u 0 -t -k
>> Blocks till return is typed.
>
> I don't see this behavior.
>
> % zsh --version
> zsh 5.9 (x86_64-apple-darwin18.7.0)
> % zsh -fc 'read -t -k' <================
> % zsh -fc 'read -u 0 -t -k' <================
> %
Those lines run your commands in clean shells. They are supposed
to demonstrate that I am not seeing the behavior that you are seeing.
I also don't see it using a function in an older version of zsh.
% /bin/zsh --version
zsh 5.3 (x86_64-apple-darwin18.0)
% /bin/zsh -fc '() { read -u 0 -t -k }'
%
--
vq
prev parent reply other threads:[~2022-07-29 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 19:20 johnnonedoe
2022-07-29 19:40 ` Lawrence Velázquez
[not found] ` <549595162.4093300.1659133992108@mail.yahoo.com>
2022-07-29 22:57 ` Lawrence Velázquez [this message]
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=6f6335b6-03c0-419c-b2ba-4ad22e6cd468@www.fastmail.com \
--to=larryv@zsh.org \
--cc=johnnonedoe@aol.com \
--cc=zsh-workers@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).