From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>,
<zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: POSIX exit codes (not quite Re: status codes on Dec OSF)
Date: Wed, 27 Jun 2001 07:46:05 +0000 [thread overview]
Message-ID: <1010627074605.ZM5083@candle.brasslantern.com> (raw)
In-Reply-To: <000c01c0fed8$edde6520$21c9ca95@mow.siemens.ru>
On Jun 27, 11:15am, Andrej Borsenkow wrote:
}
} Any real reasons to retain current zsh exaustive path search?
Aside from the fact that I happen to find that behavior useful, one of
the reasons that zsh works that way is because it's presumably more
efficient to simply let the kernel decide whether it can execve() any
given path than it is for the shell to stat() it first; no need to
waste time copying all that inode data into user space, etc.
} It depends on the definition of "appropriate execution permissions".
} It may be understood as "if file can be executed" (what zsh does
} currently). But I suspect, that it actually meant "stat.st_mode &
} (S_IXUSR|S_IXGRP|S_IXOTHR)". I.e. file with any executable bit set.
Or it may mean a file with execute bits set such that it's executable
by the current user. Is there no way to tell?
I think the question should always be "Any real reason to change the
current behavior?" So far I think not.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-06-27 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1000304181244.ZM24879@candle.brasslantern.com>
2001-06-21 21:46 ` status codes on Dec OSF Brian Harvell
2001-06-22 6:01 ` Andrej Borsenkow
2001-06-23 3:49 ` PATCH: POSIX exit codes (not quite Re: status codes on Dec OSF) Bart Schaefer
2001-06-23 18:22 ` Bart Schaefer
2001-06-25 5:57 ` Andrej Borsenkow
2001-06-27 7:15 ` Andrej Borsenkow
2001-06-27 7:46 ` Bart Schaefer [this message]
2001-06-27 13:02 ` Brian Harvell
2001-06-22 7:03 ` status codes on Dec OSF Sven Wischnowsky
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=1010627074605.ZM5083@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=zsh-workers@sunsite.auc.dk \
/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).