From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: lost sysread
Date: Sun, 5 May 2024 09:19:37 -0700 [thread overview]
Message-ID: <391c45c4-c8d4-4a8b-9e8b-bdb07226401f@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7ZW8hkZ_=ge2PQs-Zdh5ufNQ=geJmorBVc58sM==x=NcA@mail.gmail.com>
On 2024-05-05 08:42, Bart Schaefer wrote:
> On Sun, May 5, 2024 at 6:17 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>> Supposing the error msg was: "Module 'sysread' is not loaded"?
> If the module hasn't been loaded yet, how is the shell supposed to
> know that sysread isn't an external command? The whole point of
> modules is that the base shell does not have a compiled-in list of all
> the possible things that could come from modules.
Sure, it might not be workable. Just an idea. As you say there'd have
to be some list and that wouldn't be worth the weight. Or some way of
quickly scanning what's available:
zmodload --quick-check ... sorta
Not worth it since I suppose one only need bump into the problem once to
be made wise to 'not found' being sometimes 'not loaded' -- it never
happened to me before this. It seems I usually end up with the module
loaded even tho I don't know exactly where it gets done. I like
helpfulness but not at the cost of bloat. Yup, if it couldn't be done
easily then it's not worth worrying about.
>
next prev parent reply other threads:[~2024-05-05 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 22:42 Ray Andrews
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 [this message]
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=391c45c4-c8d4-4a8b-9e8b-bdb07226401f@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).