zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh User <zsh-users@sunsite.dk>
Subject: Re: cd && cdable_vars (bug?)
Date: Wed, 29 Mar 2006 10:09:01 -0800	[thread overview]
Message-ID: <060329100901.ZM5908@torch.brasslantern.com> (raw)
In-Reply-To: <20060329114653.GA24380@let.rug.nl>

On Mar 29,  1:46pm, Francisco Borges wrote:
}
} Two questions/comments about cd and cdable_vars:
} 
} 1. I have cdable_vars set and I do have some data directories with
}    "integer" names: 2, 3, 5.
} 
}    When trying to complete on these dirs, I get not only the dirs I'm
}    supposed to get (those inside directory "5/.") but I also get all
}    subdirs of the fifth entry in my dirstack as "directory after
}    cdablevar".

That looks like a bug in _cd.  It should be getting handled by _tilde
and classified as "directory-stack".
 
}    Which AFAIK should not happen, since there is a directory "5", so
}    there should be no cdablevar lookup, right?

That's probably true, but it may depend on your other completion settings.
Completion usually errs on the side of giving you too many choices, when
there is ambiguity.
 
} 2. The first problem lead me to try completing on cdablevars from the

Do you mean "completing" here, or do you mean executing "cd"?

}    dirstack. This is *not* something I would like to do, but I tried
}    motivated by the noise when completing.
} 
}    And it failed! But it shouldn't, right?

I think the doc for CDABLE_VARS predates the ability to refer to dirstack
entries with tilde-notation ... "as if it were preceded by a `~'" really
means "look it up in the named directories table and use the value of the
parameter".  Since "3" is not really a parameter ...  Anyway, I believe
this is a case of the implementation outrunning the doc.


  reply	other threads:[~2006-03-29 18:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 11:46 Francisco Borges
2006-03-29 18:09 ` Bart Schaefer [this message]
2006-03-29 19:40   ` Francisco Borges

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=060329100901.ZM5908@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).