From: Seth Kurtzberg <seth@cql.com>
To: Andrey Borzenkov <arvidjaar@newmail.ru>
Cc: zsh-workers@sunsite.dk
Subject: Re: = completion
Date: Sun, 27 Nov 2005 09:06:15 -0500 [thread overview]
Message-ID: <1133100375.29478.7.camel@localhost.localdomain> (raw)
In-Reply-To: <200511271121.55108.arvidjaar@newmail.ru>
On Sun, 2005-11-27 at 11:21 +0300, Andrey Borzenkov wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Saturday 26 November 2005 22:22, Seth Kurtzberg wrote:
> >
> > In each of the following, however, tab completion does not work (that
> > is, no completion occurs):
> >
> > export abc=/whatever:$abc (obviously I attempt tab completion
> > before adding the :$abc)
> >
>
> Works fine and with COMPLETE_IN_WORD set also in the middle of string
>
> > dd if=./whatever
> >
>
> Of course works too.
>
> Which zsh version and completion style do you use? I am not sure if compctl
> does what you want (I have not used it for years) but new compsys does. If
> you have zsh 4.2.x, try
>
> autoload -U compinit; compinit
Thanks much, this indeed took care of the problem. I didn't realize
that this wasn't the default.
I'll use the users list next time.
>
> to initialize completion system.
>
> > The latter is an example of using arg=/some/path which occurs for
> > various commands, so dd is just an example and the question is not in
> > any way specific to dd.
> >
>
> It is. Completion is context-sensitive. It knows that export expects
> (path-)assignment; that for dd if= has path as argument; but it has no way to
> know this for arbitrary command "foo". While it is possible to fallback to
> something like dd does, I am now sure it is good idea; you probably need it
> only for several commands and it is likely zsh already includes suitable
> completion for them.
>
> > I do have the options related to equals completion enabled.
> >
>
> Which suggests you are using compctl.
>
> > I also tried this on a new install of linux
>
> This satement is meaningless :) Which distribution, which version? Some of
> them may use compsys by default some not. Anyway, just try compinit as above
> and if it works, try compinstall that will help you to setup new completion
> system.
>
> BTW zsh-users would be more appropriate for such questions.
>
> - -andrey
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
>
> iD8DBQFDiWyiR6LMutpd94wRAkHWAJ9eBvoUlJre1se/GdN0hJ5aw7wSrwCgsIgb
> rK26xHma2Fcr9v1cxi5dPak=
> =NVS1
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2005-11-27 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 19:22 Seth Kurtzberg
2005-11-27 8:21 ` Andrey Borzenkov
2005-11-27 14:06 ` Seth Kurtzberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-08 10:30 \# completion Sven Wischnowsky
2000-08-04 14:33 Peter Stephenson
2000-08-05 16:41 ` 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=1133100375.29478.7.camel@localhost.localdomain \
--to=seth@cql.com \
--cc=arvidjaar@newmail.ru \
--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).