From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: 3.1.6-dev-22
Date: Tue, 11 Apr 2000 14:58:17 +0000 [thread overview]
Message-ID: <1000411145817.ZM31950@candle.brasslantern.com> (raw)
In-Reply-To: <200004110754.JAA03928@beta.informatik.hu-berlin.de>
On Apr 11, 9:54am, Sven Wischnowsky wrote:
} Subject: PATCH: Re: 3.1.6-dev-22
}
} I wrote:
}
} - The change to file-patterns suggested by Peter (I planned to send
} this in a separate patch and then accidentally overwrote it, sorry).
} I.e. it looks a bit more like tags-order, one can do:
}
} ... file-patterns '*.o:obj-files *(-/):dirs' ...
}
} Giving more than one pattern per string, with different tags. Small
} problem: one can still give more than one pattern per tag -- and has
} to separate them with commas. I don't like that, it's different from
} every other separation character we have.
One possibility is to use the familiar brace expansion syntax:
... file-patterns '{*.(a|o),*(*)}:compiled-files *(-/):dirs' ...
In fact, that syntax could be used everywhere that multiple glob patterns
are presently separated by spaces, which would e.g. make it clearer that
all the patterns in a PATTERNS:TAG form were associated with the TAG.
However, that's a much bigger change, and I don't know whether it makes
parsing a lot more difficult.
That also "looks like" it should mean:
... file-patterns '*.(a|o):compiled-files *(*):compiled-files ...' ...
which ought to be supported as equivalent if it isn't yet, that is,
mentioning a tag a second time in the same string should union rather
than replace the previous patterns for that tag.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-04-11 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-11 7:54 Sven Wischnowsky
2000-04-11 8:14 ` Andrej Borsenkow
2000-04-11 14:58 ` Bart Schaefer [this message]
2000-04-11 8:28 Sven Wischnowsky
2000-04-11 12:32 ` Adam Spiers
2000-04-11 15:48 ` Bart Schaefer
2000-04-11 20:19 ` Peter Stephenson
2000-04-11 12:37 Sven Wischnowsky
2000-04-11 15:04 Sven Wischnowsky
2000-04-12 9:10 Sven Wischnowsky
2000-04-12 16:21 ` Bart Schaefer
2000-04-13 8:07 Sven Wischnowsky
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=1000411145817.ZM31950@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).