zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Problem with _expand, _path_files, and $(command)
Date: Mon, 3 Jul 2000 11:01:07 +0200 (MET DST)	[thread overview]
Message-ID: <200007030901.LAA04627@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Mon, 3 Jul 2000 08:51:23 +0000


Bart Schaefer wrote:

> On Jul 3, 10:12am, Sven Wischnowsky wrote:
> } Subject: Re: PATCH: Problem with _expand, _path_files, and $(command)
> }
> } Bart Schaefer wrote:
> } 
> } > zagzig[88] echo $(exit 0)
> } > zagzig[88] echo \$\*\(exit\ 0Om\)
> } 
> } Shouldn't we just test for [[ $PREFIX$SUFFIX = *\$\(*\)* ]] and
> } give up if that is true?
> 
> This is a contrived example, but:
> 
> zagzig[128] ls Completion/$(echo Core)/_
> Completing file
> _funcall            _compalso           _files              _ignored          
> _menu               _approximate        _list               _setup
> (etc.)
> 
> This is without the _expand completer.  (The odd-looking order of the
> file names is because my styles display them sorted by mod time.)  Is
> that still going to work if _path_files gives up as you suggest?

Hm, no. Maybe just change the patterns in lines 120, 122, 166 and 168
from `(?*)' to `(*[^\$])'? (Haven't tried...)

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2000-07-03  9:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-03  9:01 Sven Wischnowsky [this message]
2000-07-03 17:30 ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2000-07-05  6:26 Sven Wischnowsky
2000-07-04  8:04 Sven Wischnowsky
2000-07-04 17:15 ` Bart Schaefer
2000-07-03  8:12 Sven Wischnowsky
2000-07-03  8:51 ` Bart Schaefer
2000-07-02 17:13 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=200007030901.LAA04627@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.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).