From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21150 invoked by alias); 2 Apr 2015 15:37:26 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 20066 Received: (qmail 9192 invoked from network); 2 Apr 2015 15:37:25 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=B+CN44rV4Q1eEvwt9LLS+2rTUblvU60yVficQdKaJKE=; b=QgESX8NnDrrpaCC/H4GdYnpbmEixSfpqo9meCMnXpxepnqj46bD3pyT6d3VqsSYSQi P3yuUh7bBgiWzriMUChEzu84MyUzrnptANe1P/Ma3aK3cc12l1zz7x7DH3DMizV31+v8 pzHH1v6UXqYwrbAw8Q17l84T9K68rymy8fRPDDZBzLr7S91UFqhhAWD7/dCNnmIJxzJ6 p5GHmsWjxus+owXVlBPoOXWW2hz2RP7nVIcs4IkTn+gdLhq1AIBDBFUYrUjB6RmMLebB I8RfNoJHCtm7bdJhw1KYMxQ0WByQ4ldb1UBx2vNmpyAdm/cMKQqTbZbnnFxrQi5Y/Uin FYzg== X-Gm-Message-State: ALoCoQnQACCT3pN4/jaU3KuOBg9IELaub5BOsrQ4pl/FZ4Ym0sbuA8dmzMzAdxgrIALQX/vrlr9y X-Received: by 10.60.70.161 with SMTP id n1mr47509296oeu.28.1427989042608; Thu, 02 Apr 2015 08:37:22 -0700 (PDT) From: Bart Schaefer Message-Id: <150402083718.ZM32022@torch.brasslantern.com> Date: Thu, 2 Apr 2015 08:37:18 -0700 In-Reply-To: <20150402070012.GC2805@localhost.localdomain> Comments: In reply to Han Pingtian "histbeep doesn't work?" (Apr 2, 3:00pm) References: <20150402070012.GC2805@localhost.localdomain> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-user Subject: Re: histbeep doesn't work? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 2, 3:00pm, Han Pingtian wrote: } } How to trigger the beep when failing to access a history entry? HISTBEEP doesn't refer to bang-history, it refers to history motions in the ZLE widget set.