Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [Bug] Strange Globing Behaviour when used with sudo
- X-seq: zsh-workers 42903
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: <zsh-workers@xxxxxxx>
- Subject: Re: [Bug] Strange Globing Behaviour when used with sudo
- Date: Thu, 31 May 2018 09:49:36 +0100
- Cms-type: 201P
- Dkim-filter: OpenDKIM Filter v2.11.0 mailout1.w1.samsung.com 20180531084940euoutp0112a856ff3c3efc17b6271d27a4840e27~zroPypCnJ2575425754euoutp01q
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1527756580; bh=T6XqVsv0TPAYyxauQ79BySrC1P67ELyMSJhJWBxI7N0=; h=Date:From:To:Subject:In-Reply-To:References:From; b=LnqpPpVoM7qwy3VBjtUt4IVtWoOPKCKNMEME08YBWZGNsdvbxf+LrmHcffGXlR7vV O9wa+eolEAmoOoBQjkUgvw/kbl7fqFNOINmJOrVtlK+kpi/QzTNw//pC3qwDxxq3gH LF6yZbSOSmFrQaOcfOMecqzeES7BMAGJ84dhHOhc=
- In-reply-to: <20180531094403.05b62bee@camnpupstephen.cam.scsc.local>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- Organization: SCSC
- References: <CAMaoPXzXBv4pAD1_=Lr78h3iT+yhZfSq0CgEs+QMTVeDaR28Vw@mail.gmail.com> <CAH+w=7YxodoKJhA9-xswA5H7vckiHHzFTO_MqR5Ahux0p3h6NQ@mail.gmail.com> <1527707719.3469997.1390875592.73AD29B6@webmail.messagingengine.com> <20180530202349.GA10754@osmium.lan> <CAMaoPXzzuRvAn1FFF3BJ0fnJTiaGgeg2TJKAZgL4RLwV5t5RBw@mail.gmail.com> <CGME20180530205013epcas1p21e3a53e151d3696ad475913d56ced3db@epcas1p2.samsung.com> <CAMaoPXwFdVPszgra5busqtLNqAKsJxDV56LPW9ZrtUbg=tbSMQ@mail.gmail.com> <20180531094403.05b62bee@camnpupstephen.cam.scsc.local>
On Thu, 31 May 2018 09:44:03 +0100
Peter Stephenson <p.stephenson@xxxxxxxxxxx> wrote:
> If it is the issue, it's going to take some detective work by someone
> on MacOS as grepping the code doesn't reveal an obviously missing use
> of ino_t in the zsh code --- worth checking if ino_t is actually
> correctly typedef'd.
Also, worth doing some easy checks anyway in config.h. There's an
INO_T_IS_64_BIT definition that should be set, is it? If not, how about
trying the other configuration definition
#define _DARWIN_USE_64_BIT_INODE
and see if that fixes the matter? That would indicate the problem
wasn't that ino_t wasn't being used correctly in the code, just that
the type as defined wasn't large enough for certain situations in
configuration.
(Apologies if I'm teaching my grandmother to suck eggs but the thread so
far didn't suggest anyone on MacOS was actually looking down here.)
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author