From: Felix Rosencrantz <f_rosencrantz@yahoo.com>
To: zsh-workers <zsh-workers@sunsite.auc.dk>
Subject: Re: spaceflag question; remhist() going away
Date: Mon, 17 Jul 2000 22:23:17 -0700 (PDT) [thread overview]
Message-ID: <20000718052317.200.qmail@web1303.mail.yahoo.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1682 bytes --]
Wayne Davison wrote:
>The matching rule would allow more general command-name rules, plus
>line-oriented rules that name-oriented support don't allow. For
>instance: ignoring lines that are just 1 or 2 chars long; ignoring
>the make command unless it had an argument or was a part of a compound
>statement; ignoring the history command, but only if it is not a part
>of a compound statement (such as having its output piped into a
>script); ignoring lines that begin with whitespace (including tab)
>without having any extra alias-checking rules done; ignoring a lynx
>command that uses the -auth option; etc.
>
>The plus side is that a line-matching rule is much more flexible. The
>down side is that a user has to understand complex patterns to be able
>to use it effectively. Some good examples would get the casual user
>going, though.
Yeah, I was talking about something similar that could be used with
Bart's new smart-insert-last-word widget. Seems like some common ability
to match and filter history would be useful in several situations. Sort of
a regex for command history... 8)
Another thing I would use is a "soft" or "fuzzy" history mechanism. For
example, I would really like to be able to intercept a "!$" history option
and replace it with a call to smart-insert-last-word (w/command line matching).
Or the ability to intercept other history calls like !* or !!. It seems like
it would be useful to have an option that would allow us to play with this
history mechanism, so it's a little more DWIM.
-FR
__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail Free email you can access from anywhere!
http://mail.yahoo.com/
next reply other threads:[~2000-07-18 5:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-18 5:23 Felix Rosencrantz [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-17 1:54 Wayne Davison
2000-07-17 8:57 ` Peter Stephenson
2000-07-17 10:04 ` Wayne Davison
2000-07-17 16:46 ` Bart Schaefer
2000-07-17 18:29 ` Wayne Davison
2000-07-17 19:44 ` Wayne Davison
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=20000718052317.200.qmail@web1303.mail.yahoo.com \
--to=f_rosencrantz@yahoo.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).