From: Cosmo <cosmo@informix.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: zsh-workers@math.gatech.edu
Subject: Re: ideas: free-search-complete, noexpand
Date: Fri, 07 Aug 1998 14:02:50 +0100 [thread overview]
Message-ID: <35CAFAFA.7776F8F1@informix.com> (raw)
In-Reply-To: <199808071213.OAA20646@beta.informatik.hu-berlin.de>
Sven Wischnowsky wrote:
> Cosmo wrote:
>
> >
> > Sven Wischnowsky wrote:
> >
> > > Maybe we should think about developing an easy to read syntax for
> > > completion control.
>
> I guess many of us would like to have a real DWIM, but...
>
> Doing something like that would require at least some serious parsing
> and some guessing (what's the difference between include-file,
> tape-file, and files; and for other commands the same words may have
> different meanings).
I'm not quite that lazy. Specifying /usr/include/*,
/dev/rst* wouldn't be too much of a trial.
> Also, some users may prefer to build their
> compctls according to the way they normaly use the commands
> (e.g. someone may use only few of the --options of some commands).
Then just specify the ones you use most. I wasn't thinking of tryingto parse the -help
output of a command or the man page description,
It just seemed an easier way to describe simple completion behaviour.
Cosmo
next prev parent reply other threads:[~1998-08-07 13:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-07 12:13 Sven Wischnowsky
1998-08-07 13:02 ` Cosmo [this message]
1998-08-07 13:04 ` EZ-compctl (was Re: ideas: free-search-complete, noexpand) Bruce Stephens
-- strict thread matches above, loose matches on Subject: below --
1998-08-07 7:19 ideas: free-search-complete, noexpand Sven Wischnowsky
1998-08-07 9:28 ` Cosmo
1998-08-06 9:56 Sven Wischnowsky
1998-08-06 13:14 ` Peter Stephenson
1998-08-06 9:01 Sven Wischnowsky
1998-08-06 8:03 Sven Wischnowsky
1998-08-06 8:39 ` Peter Stephenson
1998-08-06 9:09 ` Zefram
1998-08-06 17:50 ` Bart Schaefer
1998-08-05 6:29 Sven Wischnowsky
1998-08-04 18:49 Johan Sundström
1998-08-04 21:37 ` 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=35CAFAFA.7776F8F1@informix.com \
--to=cosmo@informix.com \
--cc=wischnow@informatik.hu-berlin.de \
--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).