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: Mon, 31 Jan 2005 12:32:26 -0500	[thread overview]
Message-ID: <44613de0050131093255b80bc7@mail.gmail.com> (raw)
In-Reply-To: <1050129183904.ZM13058@candle.brasslantern.com>

On Sat, 29 Jan 2005 18:39:04 +0000, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> On Jan 28, 11:25am, Shawn Halpenny wrote:
> } Subject: Re: can't complete .. paths with 4.2.3
> }
> } 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.
> 
> Do you have any zstyles set at all?  Put another way, have you tried
> reproducing this with 'zsh -f' (running autoload and compinit by hand)?
> 
> The only obvious reason that compfiles would behave that way at that
> particular spot is if the "fake-files" style were set to something.

I have zstyles, but it makes no difference if they are executed or
not.  However, I noticed that running 'zsh -f' and running compinit by
hand made things work again, so the problem must have been in my rc
files.

As it turns out, in my .zshenv I have 'setopt nocaseglob'.  If I
remove that (or 'setopt caseglob' at a prompt), I can complete paths
with .. again.  This behavior must have changed since 4.2.1, since
I've had that option setting for ages.

-- 
Shawn Halpenny


  reply	other threads:[~2005-01-31 18:00 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
2005-01-29 18:39     ` Bart Schaefer
2005-01-31 17:32       ` Shawn Halpenny [this message]
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=44613de0050131093255b80bc7@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).