From: Ray Andrews <rayandrews@eastlink.ca>
To: Zsh Users <zsh-users@zsh.org>
Subject: lost sysread
Date: Fri, 3 May 2024 15:42:50 -0700 [thread overview]
Message-ID: <08c57670-aa9f-41db-b0d3-574ec1e222f0@eastlink.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
Any ideas?
0 /aWorking/Zsh/Source/Wk 2 % . test1; print -r -- $(( srand32() ))
srand32:4: command not found: sysread
4
0 /aWorking/Zsh/Source/Wk 2 % exit
0 /aWorking/Zsh/Source/Wk 1 % . test1; print -r -- $(( srand32() ))
3551593729
0 /aWorking/Zsh/Source/Wk 1 % zsh -f
b6-12-Deb12b# . test1; print -r -- $(( srand32() ))
srand32:4: command not found: sysread
4
b6-12-Deb12b# exit
0 /aWorking/Zsh/Source/Wk 1 % . test1; print -r -- $(( srand32() ))
2230494374
... for some unknown reason one of my open shells can find sysread while
others can't. I use hibernate, so the OK shell has been open for far
too long to digress as to which commands might have put it into a
friendly mood as to sysread. How on earth do I figure this out?
Printing out all my variables, there's dozens of differences, but there
always are. Any hot prospects? I can't think where I'd even begin. How
can a builtin ever not be found? I know sometimes one 'level' of command
can mask another, like a function 'sysread' might mask the builtin, but
that's not the case here. It's not disabled. Nothing else seems to be
broken or missing. No idea.
[-- Attachment #2: Type: text/html, Size: 1654 bytes --]
next reply other threads:[~2024-05-03 22:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 22:42 Ray Andrews [this message]
2024-05-03 23:55 ` Lawrence Velázquez
2024-05-03 23:57 ` Bart Schaefer
2024-05-05 5:23 ` Lawrence Velázquez
2024-05-05 13:17 ` Ray Andrews
2024-05-05 15:42 ` Bart Schaefer
2024-05-05 16:19 ` Ray Andrews
2024-05-04 1:06 ` 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=08c57670-aa9f-41db-b0d3-574ec1e222f0@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).