zsh-users
 help / color / mirror / code / Atom feed
From: Shawn Halpenny <paxunix@gmail.com>
To: zsh-users@sunsite.dk
Subject: Re: can't complete .. paths with 4.2.3
Date: Fri, 28 Jan 2005 11:25:13 -0500	[thread overview]
Message-ID: <44613de00501280825265c7f4a@mail.gmail.com> (raw)
In-Reply-To: <1050128030646.ZM11582@candle.brasslantern.com>

On Fri, 28 Jan 2005 03:06:46 +0000, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> On Jan 27,  9:29pm, Shawn Halpenny wrote:
> }
> } With zsh 4.2.3, on AIX, HP-UX and Solaris, if I use the completion
> } system I can't complete a path that starts with '..' .
> 
> Is there any particular context in which you're completing these files?
> I can't reproduce this on linux with completion after "ls", but that
> doesn't mean it might not happen with some other command.
> 
> Have you tried deleting your .zcompdump file?
> 

Yes, with no effect.  The context doesn't seem to make any difference
at all.  I tried completing after 'echo' and 'ls' and 'grep' and if
the path starts with .. no completions are listed.  Furthermore, it
seems if .. is anywhere in the path, no completions are returned.

I tried removing the functions.zwc that contains the precompiled
functions for local/share/zsh/4.2.3/functions but nothing changed.

I tried completing 'echo ../' with trace enabled and noticed that tmp1
after the call to compfiles (line 345 of _path_files) was empty,
whereas on Cygwin, it had the list of files in the parent dir.

(I can post the trace to the list but didn't want to force 439 lines
of junk on anyone.)


  reply	other threads:[~2005-01-28 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28  2:29 Shawn Halpenny
2005-01-28  3:06 ` Bart Schaefer
2005-01-28 16:25   ` Shawn Halpenny [this message]
2005-01-29 18:39     ` Bart Schaefer
2005-01-31 17:32       ` Shawn Halpenny
2005-02-01  2:31         ` Bart Schaefer
2005-01-29  4:23   ` Joshua Tinnin

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=44613de00501280825265c7f4a@mail.gmail.com \
    --to=paxunix@gmail.com \
    --cc=zsh-users@sunsite.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).