zsh-workers
 help / color / mirror / code / Atom feed
From: Kunshan Wang <wks1986@gmail.com>
To: zsh-workers@zsh.org
Subject: Bug: Completion of the 'zsh' command.
Date: Thu, 10 Oct 2013 01:15:26 +1100	[thread overview]
Message-ID: <525564FE.3030705@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]

Hi,

Filename arguments of the 'zsh' command cannot be completed.

Distro: ArchLinux
Kernel: linux 3.11.4-1
Arch: x86-64
zsh: 5.0.2

Also reproducable on a Mac OSX 10.8 with zsh installed from Homebrew.

How to reproduce:

1. Create a new user account on my Linux to set up a clean environment.
Then use compinstall to initialize a default setting. (This is optional
since it is usually reproducable whenever completion is enabled)

2. Create a new text file:

    $ echo 'echo hello' > hello.zsh

3. Type 'zsh ./h' (no quote) and press TAB

What actually happens: The file hello.zsh is listed below, but continue
pressing TAB will not select the file 'hello.zsh'. Nothing happens.

What I think it should happen: zsh should cycle through all filenames in
the current directory beginning with 'h' (because I typed './h') and
complete it.

More information:

* The Mac OSX comes with an older 4.x version of zsh and it completes
the filename normally.

* The zsh FAQ 4.6 (http://zsh.sourceforge.net/FAQ/zshfaq04.html#l50)
works. It will start file completion normally, but I don't understand
why the completer of the 'zsh' command is not expecting any file in the
current directory. Also there are many scripts in
/usr/share/zsh/functions/Completion and many scripts for zsh's internal
commands, but there is no script for the 'zsh' command itself. Is it
placed elsewhere?

Regards,
Kunshan Wang


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]

             reply	other threads:[~2013-10-09 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 14:15 Kunshan Wang [this message]
2013-10-10  3:01 ` Bart Schaefer
2013-10-10 19:41   ` Bart Schaefer
2013-10-11  8:56     ` Peter Stephenson
2013-10-12  6:18       ` Bart Schaefer
2013-10-13 18:06         ` Peter Stephenson
2013-10-13 19:09           ` Bart Schaefer

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=525564FE.3030705@gmail.com \
    --to=wks1986@gmail.com \
    --cc=zsh-workers@zsh.org \
    /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).