From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: UP and DOWN with multi-line minibuffer history Date: Sun, 13 Dec 2015 17:24:15 +0200 Message-ID: <83lh8y5q3k.fsf@gnu.org> References: <83wpsj6978.fsf@gnu.org> <87y4czz63l.fsf@mail.linkov.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1450020276 21513 80.91.229.3 (13 Dec 2015 15:24:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 13 Dec 2015 15:24:36 +0000 (UTC) Cc: emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 13 16:24:27 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1a88Ve-000758-C3 for ged-emacs-devel@m.gmane.org; Sun, 13 Dec 2015 16:24:26 +0100 Original-Received: from localhost ([::1]:55591 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a88Vd-0007uB-EL for ged-emacs-devel@m.gmane.org; Sun, 13 Dec 2015 10:24:25 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46893) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a88VP-0007tg-0G for emacs-devel@gnu.org; Sun, 13 Dec 2015 10:24:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a88VK-00021p-Bo for emacs-devel@gnu.org; Sun, 13 Dec 2015 10:24:10 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:40272) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a88VK-00021l-8d; Sun, 13 Dec 2015 10:24:06 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2936 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1a88VJ-00080d-EN; Sun, 13 Dec 2015 10:24:05 -0500 In-reply-to: <87y4czz63l.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 13 Dec 2015 01:20:49 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:196210 Archived-At: > From: Juri Linkov > Cc: emacs-devel@gnu.org > Date: Sun, 13 Dec 2015 01:20:49 +0200 > > > I think it would be more consistent, including with how > > line-move-visual behaves in normal buffers, if UP ended up in the last > > line of the previous item. WDYT? > > The initial implementation of this feature was like you described above. > But later I received complaints off-list that convinced me to open > bug#19824 with better implementation to address the inconvenience of > navigating through the multi-line minibuffer history: for backward-compatible > behavior we need every UP in the sequence move to a previous history item. > This can be achieved when UP places the cursor at the top line of a > multi-line history item, ready for going to the next previous item with > successive UP. Sorry, I don't understand why supporting goal-column must have this side effect. In a normal buffer, we do support goal-column (in the visual-line sense), and still we don't jump to the firs screen line of a long logical line. Why should the minibuffer behave differently? I guess the description in bug#19824 lacks some crucial details, because I simply don't see why preserving the column should force to jump to the first screen line of the previous history item. Can you explain? Are you interpreting the goal-column in physical, rather than visual, sense?