zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Stefan Radziuk <sradziuk@pdtpartners.com>, zsh-workers@zsh.org
Subject: Re: Using the history expansion modifier 'a' results in excessive lstat calls
Date: Fri, 20 May 2022 11:15:22 +0100 (BST)	[thread overview]
Message-ID: <200084252.242457.1653041722599@mail2.virginmedia.com> (raw)
In-Reply-To: <CY5PR20MB4843E231D8BA513A209C6541C1D39@CY5PR20MB4843.namprd20.prod.outlook.com>

On 20 May 2022 at 11:08 Stefan Radziuk <sradziuk@pdtpartners.com> wrote:
> I have looked through some threads in the mailing list to find out why
> zgetdir > is being used over getcwd in the first place. It seems it was
> implemented this way in the 1990s to work around a bug in some implementations
> of getcwd, which should not be a concern on modern systems. 
> 
> I was wondering if zgetdir is still the right way to do this? Are there
> use cases where it is preferred over getcwd? Maybe zgetcwd could simply
> use getcwd primarily (i.e. not as fallback), or perhaps USE_GETCWD could
> be enabled by default (currently it is only enabled on QNX builds).

The best bet would probably be to try that by default once we're sure the
release is out of the way --- as you say there's a good chance that's the
right way to go now and I don't think we're going to find out the problems
any other way.

pws


  reply	other threads:[~2022-05-20 10:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 10:08 Stefan Radziuk
2022-05-20 10:15 ` Peter Stephenson [this message]
2022-05-25  9:53   ` Peter Stephenson
2022-05-25 10:22     ` (EXT) " Stefan Radziuk
2022-05-25 10:33       ` Peter Stephenson
2022-05-26  8:35         ` Peter Stephenson
2022-05-20 10:34 ` Mikael Magnusson
2022-05-23 11:32   ` (EXT) " Stefan Radziuk

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=200084252.242457.1653041722599@mail2.virginmedia.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=sradziuk@pdtpartners.com \
    --cc=zsh-workers@zsh.org \
    --subject='Re: Using the history expansion modifier '\''a'\'' results in excessive lstat calls' \
    /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

Code repositories for project(s) associated with this 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).