zsh-workers
 help / color / mirror / code / Atom feed
From: Phil Pennock <phil@athenaeum.demon.co.uk>
To: Zsh Development Workers <zsh-workers@math.gatech.edu>
Subject: Non-intuitive completion
Date: Tue, 1 Dec 1998 02:47:58 +0000	[thread overview]
Message-ID: <19981201024758.60618@athenaeum.demon.co.uk> (raw)

I've not tested this against Peter Stephenson's patched 3.1.5, only
stock release.  And I'm lost as to what's changed in the new stuff.
Also, this isn't necessarily a bug, as it's 'daft' on my part.  But the
results are counter-intuitive, to me at least.

longprompt% zsh-3.1.5 -f
athenaeum% compctl -L print
compctl: no compctl defined for print
athenaeum% print $ZSH_*<TAB>

At which point the leading $ZSH_ is completely ignored and removed, and
the * is expanded out to files in the current directory, as per usual.

Nothing special about the above choice of variable, except that <TAB>
after the Z provides the next three characters.  I'm lazy and wanted
both, so tried '*' to see what zsh would do.  I /know/ it's a filename
glob, but shouldn't the leading text have some effect instead of being
treated as null?

Notably:
athenaeum% print $ZSH_VERSION*<TAB>
beeps whilst
athenaeum% print $ZSH_VERSIO*<TAB>
loses everything before the *.

It looks as though expansion of wibble* doesn't account for wibble being
a 'variable' with null value.  Evidence:
athenaeum% FOO=
athenaeum% print $FOO*<TAB>
produces the file list.  If FOO has a non-null value, it doesn't.

Is this comprehensive enough?
-- 
--> Phil Pennock ; GAT d- s+:+ a22 C++(++++) UL++++/I+++/S+++/H+ P++@ L+++
E-@ W(+) N>++ o !K w--- O>+ M V !PS PE Y+ PGP+ t-- 5++ X+ R !tv b++>+++ DI+ D+
G+ e+ h* r y?


             reply	other threads:[~1998-12-01  5:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-01  2:47 Phil Pennock [this message]
1998-12-01  6:28 ` Bart Schaefer
1998-12-03 11:48 Sven Wischnowsky
1999-03-13 17:26 ` Bart Schaefer
1999-03-15 10:06 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=19981201024758.60618@athenaeum.demon.co.uk \
    --to=phil@athenaeum.demon.co.uk \
    --cc=zsh-workers@math.gatech.edu \
    /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).