From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#22544: 25.0.90; Long history items cause surprising positioning of cursor in minibuffer Date: Sat, 06 Feb 2016 09:45:55 +0200 Message-ID: <83k2mith70.fsf@gnu.org> References: <83a8nhycsl.fsf@gnu.org> <87d1sd1du7.fsf@mail.linkov.net> <831t8sxwvs.fsf@gnu.org> <87fux82bp7.fsf@mail.linkov.net> <83h9hnv5xz.fsf@gnu.org> <878u2yps6d.fsf@mail.linkov.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1454744843 18925 80.91.229.3 (6 Feb 2016 07:47:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 6 Feb 2016 07:47:23 +0000 (UTC) Cc: 22544@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Feb 06 08:47:12 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1aRxaJ-0007Sg-Dz for geb-bug-gnu-emacs@m.gmane.org; Sat, 06 Feb 2016 08:47:11 +0100 Original-Received: from localhost ([::1]:52281 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aRxaH-0007OU-9N for geb-bug-gnu-emacs@m.gmane.org; Sat, 06 Feb 2016 02:47:09 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47263) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aRxaD-0007O2-Gt for bug-gnu-emacs@gnu.org; Sat, 06 Feb 2016 02:47:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aRxaA-0003Ln-A2 for bug-gnu-emacs@gnu.org; Sat, 06 Feb 2016 02:47:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:54714) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aRxaA-0003Lj-64 for bug-gnu-emacs@gnu.org; Sat, 06 Feb 2016 02:47:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aRxaA-0006Aq-1d for bug-gnu-emacs@gnu.org; Sat, 06 Feb 2016 02:47:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 06 Feb 2016 07:47:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22544 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 22544-submit@debbugs.gnu.org id=B22544.145474479323698 (code B ref 22544); Sat, 06 Feb 2016 07:47:02 +0000 Original-Received: (at 22544) by debbugs.gnu.org; 6 Feb 2016 07:46:33 +0000 Original-Received: from localhost ([127.0.0.1]:35070 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aRxZg-0006AA-SB for submit@debbugs.gnu.org; Sat, 06 Feb 2016 02:46:33 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:56131) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aRxZf-00069v-Ft for 22544@debbugs.gnu.org; Sat, 06 Feb 2016 02:46:31 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aRxZS-0003GG-If for 22544@debbugs.gnu.org; Sat, 06 Feb 2016 02:46:23 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:57472) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aRxZS-0003GC-FX; Sat, 06 Feb 2016 02:46:18 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2612 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aRxZR-0001P5-QQ; Sat, 06 Feb 2016 02:46:18 -0500 In-reply-to: <878u2yps6d.fsf@mail.linkov.net> (message from Juri Linkov on Sat, 06 Feb 2016 02:52:18 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:112548 Archived-At: > From: Juri Linkov > Cc: 22544@debbugs.gnu.org > Date: Sat, 06 Feb 2016 02:52:18 +0200 > > >> 1. Put the cursor at the end of the top visual line, not logical line. > >> Drawback: the cursor will be in the middle of the logical line. > >> > >> 2. Go to the previous history element when the cursor is anywhere > >> on any of the several visual lines of the top logical line, > >> not just the top visual line. > >> Drawback: can't move the cursor to the top visual line to edit text in it. > >> > >> 3. When moving the cursor from one visual line to another visual line of > >> the logical line, keep the cursor at the end of the visual line. > >> The problem is that this behavior should be implemented in previous-line. > >> > >> 4. Set temporary-goal-column like in the patch above, but instead of 0, > >> set it to the column of the end of the top visual line, so > >> will put the cursor at the end of the top visual line in your test case. > > > > Can't we special-case a line that isn't broken into several visual > > lines, and put the cursor at the end of such lines only? That'd be > > the best. > > The problem here is that like bash and other shells with histories do, > we need to put the cursor at the end of the previous history element > so the user can start editing it immediately (usually deleting the chars > from the end of the logical line). OTOH, a subsequent should > continue navigating the history and put the next previous element to the > minibuffer. But then can't be used to move between visual lines. > This is a lose-lose situation, unless we'll find some clever DWIM. > > > If that is too hard, I guess 1 is the second best. (I'm not really > > sure how 1 is different from 4, so maybe I actually mean 4 here.) > > 4 doesn't allow to navigate to the next previous element immediately > after arriving to the current previous element. Sorry, I still don't understand. Can you give an example showing the difference between 1 and 4? Thanks.