From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: zsh-users@zsh.org
Subject: Re: histbeep doesn't work?
Date: Sat, 4 Apr 2015 06:30:15 +0800 [thread overview]
Message-ID: <20150403223015.GG2805@localhost.localdomain> (raw)
In-Reply-To: <150403091454.ZM13582@torch.brasslantern.com>
On Fri, Apr 03, 2015 at 09:14:54AM -0700, Bart Schaefer wrote:
> On Apr 3, 11:14am, Han Pingtian wrote:
> }
> } > HISTBEEP doesn't refer to bang-history, it refers to history motions
> } > in the ZLE widget set.
> }
> } I'd like to suggest clarify the doc something like this:
> }
> } -Beep when an attempt is made to access a history entry which
> } +Beep in ZLE widget when an attempt is made to access a history entry which
> } isn't there.
>
> Perhaps "Beep in ZLE when a widget attempts to access ..." but this
> change is otherwise fine.
Thanks. I have composed a new patch according to your suggestion.
>From 7c0ff8a0f0e01c33c84ec5b5bab546b84a41a841 Mon Sep 17 00:00:00 2001
From: Han Pingtian <hanpt@linux.vnet.ibm.com>
Date: Fri, 3 Apr 2015 11:09:39 +0800
Subject: [PATCH] clarifying doc of HIST_BEEP
Signed-off-by: Han Pingtian <hanpt@linux.vnet.ibm.com>
---
Doc/Zsh/options.yo | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Doc/Zsh/options.yo b/Doc/Zsh/options.yo
index 19920ca..8540256 100644
--- a/Doc/Zsh/options.yo
+++ b/Doc/Zsh/options.yo
@@ -809,7 +809,7 @@ pindex(NOHISTBEEP)
cindex(history beeping)
cindex(beep, history)
item(tt(HIST_BEEP) <D>)(
-Beep when an attempt is made to access a history entry which
+Beep in ZLE when a widget attempts to access a history entry which
isn't there.
)
pindex(HIST_EXPIRE_DUPS_FIRST)
--
1.9.3
prev parent reply other threads:[~2015-04-03 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 7:00 Han Pingtian
2015-04-02 15:37 ` Bart Schaefer
2015-04-03 3:14 ` Han Pingtian
2015-04-03 16:14 ` Bart Schaefer
2015-04-03 22:30 ` Han Pingtian [this message]
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=20150403223015.GG2805@localhost.localdomain \
--to=hanpt@linux.vnet.ibm.com \
--cc=zsh-users@zsh.org \
/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).