From: Shawn Wilson <ag4ve.us@gmail.com>
To: John <jmharres@gmail.com>,zsh-users@zsh.org
Subject: Re: zsh 5.0.2-test-1 is available
Date: Sat, 09 Nov 2013 00:20:55 -0500 [thread overview]
Message-ID: <2b0bdcdd-c292-4fb4-9bc5-8a55dc9c3ef0@email.android.com> (raw)
In-Reply-To: <527DAD8A.30309@gmail.com>
John <jmharres@gmail.com> wrote:
>On 11/8/13, 7:11 PM, Bart Schaefer wrote:
>> On Nov 8, 4:11pm, Peter Stephenson wrote:
>> }
>> } It seems to me it's equally not an error to mark zstat as a builtin
>from
>> } zsh/stat if it's already loaded as a builtin from zsh/stat. It
>would
>> } only be an error if there's a conflict.
>> }
>> } That's how "autoload" works, after all: it can't check for a
>conflict
>> } (without major faff) but it does check if a function's already
>loaded.
>>
>>
>> I'm confused; these statements seem contradictory, so I must be
>missing
>> something. If we can't check for a conflict, how can we suppress the
>> error message? I.e., how do we know that zstat is already loaded as
>a
>> builtin from the same module we're now loading?
>Could you do something as simple as remember a checksum (or md5sum) and
>
>maybe the filename when it's loaded? It seems like that would catch
>everything with a low risk of false matches.
>
I think that's overkill. I think giving a return status of 2 or 255 might be sufficient.
next prev parent reply other threads:[~2013-11-09 5:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 20:23 Peter Stephenson
2013-11-06 21:57 ` Phil Pennock
2013-11-07 15:33 ` Axel Beckert
2013-11-07 16:05 ` Peter Stephenson
2013-11-07 19:18 ` Phil Pennock
2013-11-08 1:36 ` Bart Schaefer
2013-11-08 3:16 ` Axel Beckert
2013-11-08 6:01 ` Bart Schaefer
2013-11-08 7:16 ` Phil Pennock
2013-11-08 9:38 ` Peter Stephenson
2013-11-08 14:39 ` Bart Schaefer
2013-11-08 16:11 ` Peter Stephenson
2013-11-09 2:11 ` Bart Schaefer
2013-11-09 3:35 ` John
2013-11-09 5:20 ` Shawn Wilson [this message]
2013-11-09 22:32 ` Peter Stephenson
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=2b0bdcdd-c292-4fb4-9bc5-8a55dc9c3ef0@email.android.com \
--to=ag4ve.us@gmail.com \
--cc=jmharres@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).