On Thu, Feb 08, 2001 at 10:42:49PM +0100, Michael Tatge wrote:
>Ok, quoting will help.
I haven't tried it on this, but quoting in quoting solves a few
problems like this. Ex.:
source "`find ~/base/dir/ -type f -print | grep '\.alias'`"
(notice that the apostrophes prevent a level of interpreting the
backslashes)
>At least that's what I thought first. But it's even more strange:
>
>fcc-save-hook "~t (A \| B \| C) | ~f (A \| B \| C)" =abc
>
>no way, but:
>
>fcc-save-hook "~t (A\|B\|C) | ~f (A\|B\|C)" =abc
>
>works.
>Mutt doesn't complain any more and does what I intended. Why do I have
>to leave out the spaces?
...because they're part of the expression. What you're telling the
regex matcher is that you want A followed by space, B prefixed and
followed by a space, or C prefixed with a space. It's perfectly
documented (e.g., correct in some sense) behavior. You could
certainly hack the source yourself to remove spaces in regexps, but
then there'd be the problem where you really WANTED to match against a
space.
>I did this to make my hooks more legible but
>with this 'feature' I wouldn't call the resulting hook legible. :-/
Take a page from the Sendmail documenters: the config file was
designed with machine parsing in mind, not human readability.
Provided it's low maintenance (set once and forget), you might
consider beginning the line with "#" how you'd like it to read, then
the working way on the next line. If you change it "frequently,"
that'd most assuredly mean changing everything twice.
>Can anybody explain this strange behavior to me?
I tried anyway.
>"It's God. No, not Richard Stallman, or Linus Torvalds, but God."
>(By Matt Welsh)
That's a great line!!!!
--
Oooooo-oooo-oooo-ooooo, Oooooo-oooo-oooo-ooooo, Ooooo-weem-oh-wum-ooo-ayyy
In the jungle, the silicon jungle, the process sleeps tonight.
Joe Philipps <[EMAIL PROTECTED]>, http://www.philippsfamily.org/Joe/
public PGP/GPG key 0xFA029353 available via http://www.keyserver.net
PGP signature
