From owner-svn-src-head@freebsd.org Tue Oct 31 15:08:56 2017 Return-Path: Delivered-To: svn-src-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AB5EE5C5FC; Tue, 31 Oct 2017 15:08:56 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 374A57DA83; Tue, 31 Oct 2017 15:08:56 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 5EB0176A6; Tue, 31 Oct 2017 15:08:55 +0000 (UTC) Date: Tue, 31 Oct 2017 15:08:55 +0000 From: Alexey Dokuchaev To: Dan Mack Cc: Devin Teske , "src-committers@freebsd.org" , Eitan Adler , "svn-src-all@freebsd.org" , Cy Schubert , "svn-src-head@freebsd.org" , Ed Maste , Warner Losh Subject: Re: svn commit: r325092 - head/usr.bin/fortune/datfiles Message-ID: <20171031150855.GA55289@FreeBSD.org> References: <201710291851.v9TIpM0I073542@slippy.cwsent.com> <20171030151627.GA74374@FreeBSD.org> <3CB26689-0D12-4E69-9BBA-58CCC3B71F3F@shxd.cx> <20171031060631.GA78809@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Oct 2017 15:08:56 -0000 On Tue, Oct 31, 2017 at 09:56:47AM -0500, Dan Mack wrote: > Alexey Dokuchaev writes: > > ... > > I find this separation useless and actually mitigating the good. When > > I want to scroll the history without any search I'd simply won't type > > anything. Binding prefix-search to ESC-p/ESC-n, not up-arrow/down-arrow > > is beyond me. Empty command line gives you plain iteratation, typing > > anything limit iteratation over commands starting with typed prefix. > > Maybe this disconnect is related to the fact that I never use the > arrow keys. I used ctrl-n/p to cycle shell history down/up and put an > esc in front if I am searching using history-search-backward/forward. Okay, that explains it. I've just tried your setup, it makes sense (not that I would use it, but now I understand the reason behind ESC-p/ESC-n better). Thanks, ./danfe