zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Wayne Davison <wayne@clari.net>
Cc: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: PATCH: history improvements for 3.1.5-pws-17
Date: Sat, 29 May 1999 07:26:40 +0000	[thread overview]
Message-ID: <990529072640.ZM27086@candle.brasslantern.com> (raw)
In-Reply-To: <199905110939.CAA29206@bebop.clari.net>

Man, I hate getting this far behind.

On May 11,  2:39am, Wayne Davison wrote:
} Subject: Re: PATCH: history improvements for 3.1.5-pws-17
}
} > Hmmm, it might be a good idea to make `zle widget num' override the
} > value of $NUMERIC with num when calling a widget.
} 
} I like this -- it makes writing an up-line-or-local-history function
} much simpler.

Way back in zsh-workers/4103 I griped:

    ... right now it's completely impossible for a user-defined
    widget to initiate a history search; "zle history-search-backward"
    just causes the shell to prompt the user for input, but the
    widget may already have a string it wants to search for.
    "history-search-backward string" is the natural way to perform
    that action.

If we're implementing this, why are we limiting it to *numeric* arguments?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1999-05-29  7:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-08  2:50 PATCH: history improvements for 3.1.5-pws-17 and 3.0.6-pre-2 Wayne Davison
1999-05-08 14:01 ` Peter Stephenson
1999-05-08 23:43   ` Wayne Davison
1999-05-10  7:53     ` Peter Stephenson
1999-05-11  9:39       ` PATCH: history improvements for 3.1.5-pws-17 Wayne Davison
1999-05-29  7:26         ` Bart Schaefer [this message]
1999-05-29  7:08       ` PATCH: history improvements for 3.1.5-pws-17 and 3.0.6-pre-2 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=990529072640.ZM27086@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=wayne@clari.net \
    --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).