zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: expansion of environment variables
Date: Thu, 05 Mar 2009 08:15:48 -0800	[thread overview]
Message-ID: <090305081548.ZM4603@torch.brasslantern.com> (raw)
In-Reply-To: <d5baa8100903050235ofd66039jf2c29b58684bc8d8@mail.gmail.com>

On Mar 5, 11:35am, ruud grosmann wrote:
}
} The new version has a feature that is not in the 3.0 version. I would
} like to disable the feature, but I am not sure if an option exist for
} that one. Maybe you can help me.

I don't know why this would have changed, but it does not appear that
there is any way to turn it off.  Both the expand-or-complete and the
complete-word widgets expand the variable; I would have expected the
latter not to.

Worse, if I enable the new completion system with 'compinit' then the
variable doesn't expand but the completion doesn't work.  I mention
this because with the new completion system enabled, the 'suffix'
zstyle is supposed to control exactly what Ruud is asking about, and
the default is to have the "old" behavior that he wants.
 
For benefit of zsh-workers, with compinit this is yet another problem
in _path_files.  At line 479 (latest CVS) it correctly assigns the
expanded list of files to the tmp2 array (having originally gotten
them from "compadd -D tmp1" at line 466), but then when building the
exppaths array at lines 484 or 486, it uses ${tpre}${tsuf} which have
never been expanded.

I'm also not sure how line 484 can ever be reached, since at 479
"${(@)tmp2:h}" is always going to strip off any trailing slash.  It
seems a bit strange to compare an entire array to a single pattern
at line 483 as well, but I guess it works since the last element of
the array should be representative of any single element.


  reply	other threads:[~2009-03-05 16:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 10:35 ruud grosmann
2009-03-05 16:15 ` Bart Schaefer [this message]
2009-03-05 16:21   ` Mikael Magnusson
2009-03-05 16:54   ` Peter Stephenson
2009-03-05 17:21     ` Bart Schaefer
2009-03-05 17:46       ` Peter Stephenson
2009-03-05 16:19 ` Benjamin R. Haskell

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=090305081548.ZM4603@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@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).