From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: UP and DOWN with multi-line minibuffer history Date: Mon, 14 Dec 2015 02:07:45 +0200 Organization: LINKOV.NET Message-ID: <87d1u9vqni.fsf@mail.linkov.net> References: <83wpsj6978.fsf@gnu.org> <87y4czz63l.fsf@mail.linkov.net> <83lh8y5q3k.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1450053843 22696 80.91.229.3 (14 Dec 2015 00:44:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 14 Dec 2015 00:44:03 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 14 01:43:54 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 1a8HF2-0006RK-FF for ged-emacs-devel@m.gmane.org; Mon, 14 Dec 2015 01:43:52 +0100 Original-Received: from localhost ([::1]:57145 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8HF1-0008Sa-TP for ged-emacs-devel@m.gmane.org; Sun, 13 Dec 2015 19:43:51 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60749) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8HEf-0008Ri-WA for emacs-devel@gnu.org; Sun, 13 Dec 2015 19:43:30 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a8HEf-0000od-4L for emacs-devel@gnu.org; Sun, 13 Dec 2015 19:43:29 -0500 Original-Received: from sub3.mail.dreamhost.com ([69.163.253.7]:52166 helo=homiemail-a12.g.dreamhost.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8HEa-0000o4-W4; Sun, 13 Dec 2015 19:43:25 -0500 Original-Received: from homiemail-a12.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a12.g.dreamhost.com (Postfix) with ESMTP id 326E51030063; Sun, 13 Dec 2015 16:43:23 -0800 (PST) Original-Received: from localhost.linkov.net (m83-180-31-224.cust.tele2.ee [83.180.31.224]) (Authenticated sender: jurta@jurta.org) by homiemail-a12.g.dreamhost.com (Postfix) with ESMTPA id 379DB103005E; Sun, 13 Dec 2015 16:43:21 -0800 (PST) In-Reply-To: <83lh8y5q3k.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 13 Dec 2015 17:24:15 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (x86_64-pc-linux-gnu) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] X-Received-From: 69.163.253.7 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:196229 Archived-At: > 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? Because the minibuffer is different from a normal buffer where you have a better overview on the content to be able to navigate it freely with support of more available commands. Even without mentioning the controversies of the current implementation of visual-line-mode such as unending flow of reports about broken macros, this doesn't mean we have to mimic its behavior in the minibuffer, where the primary purpose of UP is to quickly bring previous history item= s, and only as a secondary feature allow editing a multi-line item. So the question at hand can be considered as Consistency vs. Convenience, i.e. trying to achieve consistency at the cost of losing convenience. > 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? In fact, supporting goal-column is not required to have this side effect. Jumping to the first screen line was part of complaints that needed addre= ssing. Jumping to the last screen line can be achieved by exchanging just two li= nes in next-line-or-history-element and previous-line-or-history-element: moving =E2=80=98(goto-char (minibuffer-prompt-end))=E2=80=99 to the forme= r, and exchanging it with =E2=80=98(goto-char (point-max))=E2=80=99 from the latter. I invite you and everyone interested to try this change for a few days to see its real effect.