From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26758 invoked by alias); 27 Sep 2015 07:08:52 -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: 20655 Received: (qmail 12046 invoked from network); 27 Sep 2015 07:08:50 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM, T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=frjBVrLZpgF653mi56lrMmc5Z7PTtDNIL1CjNEjf0DU=; b=XFm3Yw8B5MM0ygKZeaSuC+npNCBJaLPzqTi1U1XcmdSWqh299nYa+wrprOLOb7/kf6 Ph4U6U+ipCQHaTavY19O7yOVT/d8f5p8SHvznyv1O+Wt1byg5VHvDQymSzMOHF1uRUnh K1EREx3mFaLyJ38eFX5Pfu3qPbsP5pcbE7p4/5QrbebnV7b7onfPtgNeWUbnoaY2iSwX jT4AyhUymlqgTckNEsa6g/eVv5SXk9Vbgllr7+PjM2Yce/+teVa7lLtgjPGAu+cF4Sgo sT+6lYezp9VAA3o+AVls4V06DCQzQ3V41JevlaYf3GFJXqNaL3nbPp37XfYyoQ4vFwMZ MJLA== X-Received: by 10.112.164.35 with SMTP id yn3mr3794852lbb.18.1443337726646; Sun, 27 Sep 2015 00:08:46 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <150926164544.ZM18002@torch.brasslantern.com> References: <150926164544.ZM18002@torch.brasslantern.com> From: Sebastian Gniazdowski Date: Sun, 27 Sep 2015 09:08:27 +0200 Message-ID: Subject: Re: One other alternative history search widget To: zsh-users@zsh.org Content-Type: text/plain; charset=UTF-8 On 27 September 2015 at 01:45, Bart Schaefer wrote: > On Sep 26, 4:07pm, Sebastian Gniazdowski wrote: > } > } One problem is that it puts multi line history entries into one line, > } introducing '\n' where the newlines should be. > > Is that a problem with "history -nr" output, or is it a problem with > the representation necessary to allow curses-based list selection? It's rather difficult to implement multi-line entries in the curses list. It doesn't support them right now, so the format gave by history call is a plus. One quick idea is to keep array ENTRY_MULTIPLICITY which would hold count of "\n"-s for each list entry. I would implement that in separate n-list-multi-line. Line-wise n-list is fine in the line-wise Unix world, but like in the history case, there are situations where that isn't fully enough. Best regards, Sebastian Gniazdowski