zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Danijel Tasov <zshuser@dtig.de>, zsh-users@sunsite.dk
Subject: Re: .. completion
Date: Sat, 16 Jun 2001 20:40:04 +0000	[thread overview]
Message-ID: <1010616204004.ZM5912@candle.brasslantern.com> (raw)
In-Reply-To: <20010616195236.A18024@camelot.de>

On Jun 16,  7:52pm, Danijel Tasov wrote:
} 
} When I type /us it will be completed to /usr/ when pressing TAB,
} but .. will not be completed to ../ like in tcsh.

Zsh tends to ignore '..' on the grounds that you only have to type one
character either way, so it's not a hardship to type '/' instead of TAB.

In 4.0.1 with the `compinit' system installed, you can fix this in some
contexts by using:

    zstyle ':completion:*' special-dirs ".."

I say "in some contexts" because the special-dirs style applies only when
completing path names or directories, not when completing file names.  So
the above style will allow '..' to complete to '../' after 'cd', but not
after 'ls' (for example).  This is probably a bug.

To zsh-workers:

In _path_files, the special-dirs style is looked up only as a string, but
the documentation says it may be either a string or a boolean.  Then the
string is used only if there's already a '/' on the line or if the -f or
-/ options were given.

However, in _files, _path_files is always called with -g option, so the
special-dirs style doesn't work at all for _files.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2001-06-16 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-16 17:52 Danijel Tasov
2001-06-16 20:40 ` Bart Schaefer [this message]
2001-06-16 21:38 ` Danijel Tasov
2001-06-18  7:50 ` Sven Wischnowsky

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=1010616204004.ZM5912@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-users@sunsite.dk \
    --cc=zshuser@dtig.de \
    /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).