zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: James Devenish <j-devenish@users.sourceforge.net>
Cc: zsh-workers@sunsite.dk
Subject: Re: Options for Completion/Zsh/Command/_cd?
Date: Thu, 02 Jan 2003 17:43:58 +0100	[thread overview]
Message-ID: <2987.1041525838@finches.logica.co.uk> (raw)
In-Reply-To: <20030102160616.GA8414@gulag.guild.uwa.edu.au>

On 3 Jan, you wrote:

> I always use a 'custom' version of _cd because:
> 
>  - I don't want tab completion to consider $cdpath
>    (in fact, I hate when that happens!)

  zstyle ':completion:*:*:cd:*' tag-order local-directories

will do this for you. Or you could use:

  zstyle ':completion:*:*:cd:*' tag-order local-directories path-directories

to only complete directories from $cdpath when no local directories match.

In any context where more than one type of thing is completed, you can
press ^Xh and it will list the tags used for completion in that context
and you can specify the order for them to be completed.

>  - I like CVS and .svn directories to be ignored.

  zstyle ':completion:*:*:cd:*' ignored-patterns '(|*/)(.svn|CVS)'

> I achieve this by scrubbing out portions of _cd and then adding an -F
> option to _path_files. It would probably be better if I were to be able

If I remember correctly, the ignored-patterns style is implemented by
adding -F.

> to set some options in my .zshrc rather than rolling a new _cd with each
> release. What is the canonical or preferred way of passing options to
> completion functions? I can envisage being able to solve my $cdpath

Not sure. The preferred way is that we don't ever and a zstyle is made
to do the job.

> I'm willing to bother doing the necessary patches, but my prowess with
> zsh completion functions is at the novice end of the scale. (Having
> said that, though, I have a completion function for Subversion version
> control: _svn, which I should share sometime.)

Please do share it.

Oliver

This e-mail and any attachment is for authorised use by the intended recipient(s) only.  It may contain proprietary material, confidential information and/or be subject to legal privilege.  It should not be copied, disclosed to, retained or used by, any other party.  If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender.  Thank you.


      reply	other threads:[~2003-01-02 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 16:06 James Devenish
2003-01-02 16:43 ` Oliver Kiddle [this message]

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=2987.1041525838@finches.logica.co.uk \
    --to=okiddle@yahoo.co.uk \
    --cc=j-devenish@users.sourceforge.net \
    --cc=zsh-workers@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).