msirota@ee.rochester.edu (Mark Sirota) (03/31/91)
Dan and Bart:
I have a wish list for the "pick" and "mark" commands.
(1) I've mentioned before that I'd like to be able to pick from both the To:
header and Cc: header in one swell foop.
(2) I'd like to be able to match exactly (optionally), not just match
substrings. Sometimes I still want to match substrings, though.
(3) I'd like to be able to match against the local-part of an address.
That is, I'd like "pick -t msirota" to match
"msirota@ee.rochester.edu", but not match "user@msirota.com".
(4) I'd like more than five priorities.
I realize that (3) is probably pretty tough, but it's also pretty important.
And assuming (3) is implented, I'd also like (2) to apply optionally to just
the local-part, so that I could match exactly in the above example, but I'd
like to be able to match substrings for "autox", "autox-request",
"owner-autox", etc.
How likely is it that my dreams might sometime come true? (My dream of
having tabs *not* expand to spaces with wrapcolumn set still hasn't come
true...)
--
Mark Sirota - Department of Electrical Engineering Systems Staff
University of Rochester, Rochester NY
Internet: msirota@ee.rochester.edu
UUCP: {decvax,garp,harvard,hombre,rutgers}!rochester!ur-valhalla!msirotaschaefer@ogicse.ogi.edu (Barton E. Schaefer) (04/01/91)
In article <1991Mar31.023112.23996@ee.rochester.edu> Mark Sirota <msirota@ee.rochester.edu> writes: } Dan and Bart: } } I have a wish list for the "pick" and "mark" commands. } } (1) I've mentioned before that I'd like to be able to pick from both the To: } header and Cc: header in one swell foop. Yeah. Any suggestions on a syntax for specifying multiple search criteria that wouldn't be even worse than that of find(1) ? } (2) I'd like to be able to match exactly (optionally), not just match } substrings. Sometimes I still want to match substrings, though. These are regular expressions, you know. ^ matches beginning of line, $ matches end of line, etc. Whatever your regex library supports. NOT file globbing patterns, for those readers who might confuse the two! } (3) I'd like to be able to match against the local-part of an address. } That is, I'd like "pick -t msirota" to match } "msirota@ee.rochester.edu", but not match "user@msirota.com". That's a tough one. } I realize that (3) is probably pretty tough, but it's also pretty important. Oh. :-) } (4) I'd like more than five priorities. Recompile with MAX_PRIORITY defined larger. I believe it'll handle up to 10 priorities. Although toolmode will still be able to twiddle only the first five from the mark menu. } How likely is it that my dreams might sometime come true? (My dream of } having tabs *not* expand to spaces with wrapcolumn set still hasn't come } true...) Dream #1 is the most likely, assuming we can think of a syntax. I think you can already do #2. #3 might be very slow, because mush would have to parse the address on every search; you might be better off trying to come up with a regex for it (e.g., '!*msirota[@ ]', sort of). How many priorities would be enough? The problem with tabs and spaces is with getting any arbitrary terminal to backspace over a tab correctly .... -- Bart Schaefer schaefer@zipcode.com Z-Code Software Corporation schaefer@cse.ogi.edu