From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: ignored-patterns giving correction a go
Date: Tue, 21 Mar 2000 16:46:09 +0000 [thread overview]
Message-ID: <1000321164609.ZM7674@candle.brasslantern.com> (raw)
In-Reply-To: <200003211610.RAA14795@beta.informatik.hu-berlin.de>
On Mar 21, 5:10pm, Sven Wischnowsky wrote:
} Subject: Re: ignored-patterns giving correction a go
}
} > } zstyle ... tag-order --foo=files --bar=files
} > } zstyle '*-foo' ignored-patterns '*.ps'
} >
} > Tags right now are pretty much predetermined by the completion functions
} > that use them, e.g. the way _files uses globbed-files. Hmm ... is that
} > changed by what you're working on now?
}
} Yes, and that's what the original example above was about -- the
} `user' `invented' the tag names `foo' and `bar', linking them to the
} `method' `files'. And before that I made the suggestion to allow the
} file-patterns style to contain invented tag names.
So where do the method names come from? I don't think we want this to
be so configurable that, for example, the file-patterns style could be
caused to generate parameter names. Do we?
} > shift "i > $# ? $# : i" # Stupid shift error on i > $#
}
} Yes! It's annoying, isn't it? I was tempted more than one to change it.
Bash gives the same error. Sigh.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-03-21 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-21 16:10 Sven Wischnowsky
2000-03-21 16:46 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-22 13:32 Sven Wischnowsky
2000-03-21 10:00 Sven Wischnowsky
2000-03-21 16:01 ` Bart Schaefer
2000-03-16 19:03 Oliver Kiddle
2000-03-14 14:19 tags and all that Sven Wischnowsky
2000-03-17 9:05 ` ignored-patterns giving correction a go Sven Wischnowsky
2000-03-17 18:20 ` Bart Schaefer
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=1000321164609.ZM7674@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=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).