zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-users@sunsite.dk
Subject: Re: cd completion and CDABLE_VARS
Date: Thu, 11 Mar 2004 15:05:38 +0000	[thread overview]
Message-ID: <1754.1079017538@csr.com> (raw)
In-Reply-To: "=?iso-8859-1?q?Stefan_Reich=F6r?="'s message of "Thu, 11 Mar 2004 15:46:33 +0100." <w4dwu5rfnli.fsf@nanni.riic.uni-linz.ac.at>

> When I now hit ^xh I get the following:
> 
> tags in context :completion::complete:cd::
>     local-directories named-directories      (_alternative _cd) 
>     users named-directories directory-stack  (_tilde _alternative _cd) 
>     users                                    (_users _tilde _alternative _cd)

Sounds like you need to read zshcompsys for some orientation.  (I don't
mean to claim that's necessarily as enlightening as you might wish.)

As I said before, the names on the left are the tags.  What I didn't say
was the names in parentheses are the functions implementing completion
for those tags.  This gives you a hint about what the tags are used for.

_alternative is a utility function and we should probably suppress it
from the list since it doesn't generate its own completions (I think
that's easy to do but I haven't looked at the code).

There's no precedence until you use tag-order as I described before.
The lines are simply to associate tags with different completers.

> I see, that the user names are used for the name expansion. I do not
> want that. How can I switch this off?

Instead of putting '*' in the last value in tag-order, just put
in named-directories, giving

zstyle ':completion:*:complete:(cd|pushd):*' tag-order \
  'local-directories path-directories directory-stack' 'named-directories'

This time I've added pushd explicitly.  Note that it is harmless to add
tags which the completer in question doesn't actually use.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


  reply	other threads:[~2004-03-11 15:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11 11:45 Vincent Lefevre
2004-03-11 12:28 ` Peter Stephenson
2004-03-11 13:35   ` Stefan Reichör
2004-03-11 14:11     ` Peter Stephenson
2004-03-11 14:46       ` Stefan Reichör
2004-03-11 15:05         ` Peter Stephenson [this message]
2004-03-11 15:28           ` Stefan Reichör
2004-03-11 15:45             ` Peter Stephenson
2004-03-11 15:55               ` Stefan Reichör
2004-03-11 16:26   ` Vincent Lefevre
2004-03-11 16:41     ` Vincent Lefevre

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=1754.1079017538@csr.com \
    --to=pws@csr.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).