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: Re: Tags again
Date: Mon, 10 Apr 2000 10:11:16 +0200 (MET DST)	[thread overview]
Message-ID: <200004100811.KAA31446@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Fri, 07 Apr 2000 21:05:12 +0100


Peter Stephenson wrote:

> Sven Wischnowsky wrote:
> > Ok. Any questions left? ;-)
> 
> Thanks for the explanation.  I've upgraded my remarks in the user guide
> (which actually already gave half the story) to say `don't use tag-order
> with files'.
> 
> I was still struck by one slight hickup:  I expected to be able to say
> '*.lst:globbed-files *(-/):directories' to get them named differently but
> called at the same time, but it seems you have to do
> '*.lst *(-/):globbed-files' which kind of defeats the object of giving them
> a name.  But maybe I've missed something again.

I'm don't think it makes the name useless, but... hey, I hadn't
thought of this multiple names in one string thing. Makes it look more 
like tag-order which is almost certainly a good thing.

One small problem: we always supported (in file-patterns and in the
argument to -g) multiple patterns separated by white space. If we find 
an acceptable syntax for this combined with the multiple-names thing,
I'll implement it. Using backslashes before the spaces would be the
wrong thing, though -- that's already used to include spaces in the
patterns.


Bye
 Sven


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


             reply	other threads:[~2000-04-10  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-10  8:11 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-04-07  7:40 Sven Wischnowsky
2000-04-07 20:05 ` Peter Stephenson
2000-04-06 11:26 Sven Wischnowsky
2000-04-06 18:52 ` Peter Stephenson

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=200004100811.KAA31446@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).