From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-users@zsh.org
Subject: Re: zsh 5.0.2-test-1 is available
Date: Fri, 08 Nov 2013 16:11:09 +0000 [thread overview]
Message-ID: <20131108161109.6e373049@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <131108063903.ZM25660@torch.brasslantern.com>
On Fri, 08 Nov 2013 06:39:03 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Nov 8, 9:38am, Peter Stephenson wrote:
> }
> } I think the problem with making this silent is it's not currently
> } trivial to check that the builtin that's there is actually the same as
> } the one you're trying to add, so in theory it's not safe to ignore
>
> If you want to ignore it, "zmodload -ia zsh/stat zstat" works. I don't
> think there's any reason to make -i obsolete in this case.
Hmmm... the reason is we're getting reports for things that probably
aren't actually bugs, and I for one would rather only get reports for
actual errors.
We removed the need -i from the case of "zmodload zsh/stat" because it's
not an error if zsh/stat gets loaded when zsh/stat is already present.
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.
pws
next prev parent reply other threads:[~2013-11-08 16: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 [this message]
2013-11-09 2:11 ` Bart Schaefer
2013-11-09 3:35 ` John
2013-11-09 5:20 ` Shawn Wilson
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=20131108161109.6e373049@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.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).