From: Sven Wischnowsky <wischnow@berkom.de>
To: zsh-workers@sunsite.dk
Subject: Re: Redirection completion
Date: Thu, 14 Mar 2002 13:03:12 +0100 [thread overview]
Message-ID: <15504.37248.85718.601896@wischnow.berkom.de> (raw)
In-Reply-To: <26367.1016038533@csr.com>
Peter Stephenson wrote:
> ...
>
> It seems vaguely preferable to allow the user to omit trailing
> `,-default-' bits when defining commands (it's not important in style
> contexts since you would usually use a wildcard anyway), but it doesn't
> actually gain you anything apart from laxity.
That would only work if that would mean to omit the commas, too,
because I think the distinction between an empty field (no command on
the line) and -default- may sometime be good to have. I may be wrong,
of course.
> > I.e.:
> > should `-redirect-,-default-,echo' or `-redirect-,>,-default-' take
> > precedence?
>
> It seems more logical that the command variant should take precedence,
> although the order of the parts would imply otherwise.
Yes, that's the kind of philosophical question I was thinking about.
The whole style-context name is sorted least-to-most-specific.
Other comments?
> ...
>
> This seems OK unless we do something more complicated with pattern
> handling, e.g. some way of matching the point at which you want the
> pattern tried. But I don't see any great call for that at the moment.
Nor do I, really...
Oliver on the same topic:
> Hmm, we might want to define -redirect-,<,-default- and would want
> patterns tried before that. I think the post-patterns should perhaps be
> tried just before -default- is first tried in the command position for
> redirection and in the parameter name position for values. Or perhaps,
> we need to look to see where each post-pattern uses -default-. If it
> uses a pattern for one part then we should use it before trying
> -default- for that part. We might need to require patterns to all be
> of the form -whatever-,pattern,pattern.
I think we should wait until we find something where we need a
different behaviour and then implement that (or the thing that solves
the problem behind the problem). We can add possibilities quite easily
because we already use the $_compskip parameter there (implementation
could be somewhat more complicated, depending on what we want).
Bye
Sven
--
Sven Wischnowsky wischnow@berkom.de
next prev parent reply other threads:[~2002-03-14 12:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 12:33 Peter Stephenson
2002-03-08 12:54 ` Sven Wischnowsky
2002-03-08 14:06 ` Peter Stephenson
2002-03-08 14:10 ` Sven Wischnowsky
2002-03-11 8:42 ` Sven Wischnowsky
2002-03-11 9:58 ` Sven Wischnowsky
2002-03-11 10:54 ` Peter Stephenson
2002-03-11 11:16 ` Sven Wischnowsky
2002-03-11 11:29 ` Peter Stephenson
2002-03-11 12:08 ` Sven Wischnowsky
2002-03-11 14:01 ` Peter Stephenson
2002-03-11 16:56 ` Bart Schaefer
2002-03-12 9:03 ` Sven Wischnowsky
2002-03-12 13:16 ` Oliver Kiddle
2002-03-13 9:25 ` Sven Wischnowsky
2002-03-13 16:55 ` Peter Stephenson
2002-03-14 12:03 ` Sven Wischnowsky [this message]
2002-03-13 17:58 ` Oliver Kiddle
2002-03-13 18:19 ` Bart Schaefer
2002-03-14 13:51 ` Oliver Kiddle
2002-03-14 14:41 ` Peter Stephenson
2002-03-14 14:43 ` Sven Wischnowsky
2002-03-08 13:20 ` Oliver Kiddle
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=15504.37248.85718.601896@wischnow.berkom.de \
--to=wischnow@berkom.de \
--cc=zsh-workers@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).