zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: Re: Backticks and other tricks
Date: Thu, 29 Mar 2001 08:47:11 +0000	[thread overview]
Message-ID: <1010329084711.ZM18150@candle.brasslantern.com> (raw)
In-Reply-To: <200103290814.KAA14298@beta.informatik.hu-berlin.de>

On Mar 29, 10:14am, Sven Wischnowsky wrote:
}
} The only case where the patch would cause trouble is that there are
} two (or more) options, one being a prefix of the other and the
} prefixish one gets an argument that has to come directly after the
} option.  A *very* seldom case I would say.

The only thing that worries me, given this explanation, is clusters of
single-letter options, like some of the very specialized cases in _rpm.
A whole lot of work went into making those cluster in just about every
ordering that might make sense to rpm, and some of them are pretty odd;
for example, -i means something different when it's the first option on
the line than it does when it follows -q, so `rpm -iq...' completes
differently from `rpm -qi...'.

It doesn't *appear* that anything has gone wrong with it, but there are
so many possible combinations to try ...

-- 
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:[~2001-03-29  8:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-29  8:14 Sven Wischnowsky
2001-03-29  8:47 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-29 14:09 Sven Wischnowsky
2001-03-29 16:43 ` Bart Schaefer
2001-03-28  9:49 Sven Wischnowsky
2001-03-28 15: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=1010329084711.ZM18150@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --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).