zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>,
	<zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: _expand, _expand_word, and their doc
Date: Thu, 5 Oct 2000 17:11:52 +0000	[thread overview]
Message-ID: <1001005171152.ZM24006@candle.brasslantern.com> (raw)
In-Reply-To: <002901c02ee1$c41a6f80$21c9ca95@mow.siemens.ru>

On Oct 5,  7:34pm, Andrej Borsenkow wrote:
}
} > What would you (or anyone else) think of removing insert-all-completions
} > from _expand entirely (thus eliminating the -c option) and instead put
} > compstate[insert]=all at the end of _expand_word (after _main_complete)?
} 
} What has inserting all *completions* to do with *expansions* (and thus
} _expand_word)?

You're starting from an initial pattern and expanding it into a set of
strings, aren't you?  What difference does it make whether the way you
got those strings was by globbing, parameter substitution, history, or
by invoking the completion system, or anything else?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2000-10-05 17:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-05  8:13 Sven Wischnowsky
2000-10-05 15:21 ` Bart Schaefer
2000-10-05 15:34   ` Andrej Borsenkow
2000-10-05 17:11     ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-10-09 11:49 Sven Wischnowsky
2000-10-06  8:14 Sven Wischnowsky
2000-10-06 12:34 ` Andrej Borsenkow
2000-10-06 13:00   ` Sven Wischnowsky
2000-10-08 19:35     ` Bart Schaefer
2000-09-20 17:57 Bart Schaefer
2000-09-21  5:07 ` Bart Schaefer
2000-09-21  6:33 ` Andrej Borsenkow
2000-09-21 14:37   ` Bart Schaefer
2000-09-21 14:59     ` Andrej Borsenkow

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=1001005171152.ZM24006@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --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).