zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: zsh 5.0.5-dev-2
Date: Thu, 14 Aug 2014 20:54:29 +0100	[thread overview]
Message-ID: <20140814205429.44baf512@pws-pc.ntlworld.com> (raw)
In-Reply-To: <140814092045.ZM18007@torch.brasslantern.com>

On Thu, 14 Aug 2014 09:20:45 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Aug 14, 10:32am, Peter Stephenson wrote:
> } Subject: Re: zsh 5.0.5-dev-2
> }
> } > > Can we perhaps just remove or comment out that one error message for a
> } > > release?
> } > 
> } > zsh -fw
> } > cd /
> } > zsh: path expansion failed, using root directory
> } > 
> } > We certainly need to do something.  But if this is the only issue, can't
> } > it be straightforwardly fixed like this?
> } 
> } If someone can reassure me that the weird undocumented interaction with
> } xbuf bypassing parameter passing starts here --- i.e. we are resetting
> } xbuf here, then xsymlinks fiddles with it and this code looks at the
> } result --- then I can't see how this change can be wrong as far as it
> } goes.  The question is, is there more to it?
> 
> I don't have time to compose a more thorough response here, but I think
> this may have been discussed in the previous thread.

Yes, it says anything that resolves to the root directory has the same
problem.

It's entirely unclear to me from looking at xsymlinks() when an empty
xbuf would actually constitute a failure.  If it can't expand something
as a symbolic link it simply treats it literally; and any number of ".."
is valid in a path.  There's no stat so it doesn't care if the path
actually exists.  I don't think we worry about "superroots" any more.

If we don't have an answer now I'd be inclined to comment out the
warning.

pws


  reply	other threads:[~2014-08-14 20:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 20:29 Peter Stephenson
2014-08-12 22:36 ` Axel Beckert
2014-08-13 14:04   ` zsh 5.0.5-dev-2 / Occassional hangs on Test/A05execution.ztst Axel Beckert
2014-08-13 19:08     ` Bart Schaefer
2014-08-14  8:48       ` Axel Beckert
2014-08-14  8:50       ` Peter Stephenson
2014-08-14 16:25         ` Bart Schaefer
2014-08-14 16:31           ` Axel Beckert
2014-08-14 17:34             ` Axel Beckert
2014-08-15  4:50               ` Bart Schaefer
2014-08-15  9:32                 ` Axel Beckert
2014-08-15 17:33                   ` Bart Schaefer
2014-08-15 19:42                     ` Axel Beckert
2014-08-16 18:12                       ` zsh 5.0.5/6 Peter Stephenson
2014-08-13 17:28   ` zsh 5.0.5-dev-2 Dominic Hopf
2014-08-13 22:34 ` Oliver Kiddle
2014-08-14  8:34   ` Peter Stephenson
2014-08-14  9:32     ` Peter Stephenson
2014-08-14 16:20       ` Bart Schaefer
2014-08-14 19:54         ` Peter Stephenson [this message]
2014-08-15  4:44           ` Bart Schaefer
2014-08-15  8:38             ` Peter Stephenson
2014-08-15 11:23             ` Han Pingtian
2014-08-15 17:17               ` Bart Schaefer
2014-08-16  0:35                 ` Han Pingtian
2014-08-17 17:30                   ` Bart Schaefer
2014-08-18  2:56                     ` Han Pingtian
2014-08-18  6:36                       ` Bart Schaefer
2014-08-18 14:02                         ` Han Pingtian
2014-08-23 17:51                     ` Symlink chasing 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=20140814205429.44baf512@pws-pc.ntlworld.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@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).