From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: phillip.lord@russet.org.uk (Phillip Lord) Newsgroups: gmane.emacs.bugs Subject: bug#22295: viper-mode undo bug introduced between Nov 10 and Nov 14 Date: Tue, 17 May 2016 09:48:20 +0100 Message-ID: <87bn455auj.fsf@russet.org.uk> References: <83vb2h6lfq.fsf@gnu.org> <83r3d56jrg.fsf@gnu.org> <87poso7nf5.fsf@russet.org.uk> <878tzatbte.fsf@russet.org.uk> <83zirq3qt4.fsf@gnu.org> <5739FFDD.8080206@cs.stonybrook.edu> <83twhx529u.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1463475217 11405 80.91.229.3 (17 May 2016 08:53:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 17 May 2016 08:53:37 +0000 (UTC) Cc: Michael Kifer , 22295@debbugs.gnu.org, jim@meyering.net To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue May 17 10:53:27 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 1b2ako-0007gg-Vp for geb-bug-gnu-emacs@m.gmane.org; Tue, 17 May 2016 10:53:27 +0200 Original-Received: from localhost ([::1]:49352 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2ako-0002yz-7z for geb-bug-gnu-emacs@m.gmane.org; Tue, 17 May 2016 04:53:26 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34764) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2akX-0002O7-Iw for bug-gnu-emacs@gnu.org; Tue, 17 May 2016 04:53:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b2akR-0002Om-It for bug-gnu-emacs@gnu.org; Tue, 17 May 2016 04:53:08 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:42345) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2akR-0002Oi-Ek for bug-gnu-emacs@gnu.org; Tue, 17 May 2016 04:53:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1b2akR-0004Uj-A3 for bug-gnu-emacs@gnu.org; Tue, 17 May 2016 04:53:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: phillip.lord@russet.org.uk (Phillip Lord) Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 17 May 2016 08:53:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22295 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 22295-submit@debbugs.gnu.org id=B22295.146347515517217 (code B ref 22295); Tue, 17 May 2016 08:53:03 +0000 Original-Received: (at 22295) by debbugs.gnu.org; 17 May 2016 08:52:35 +0000 Original-Received: from localhost ([127.0.0.1]:54677 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b2ajy-0004TX-Ow for submit@debbugs.gnu.org; Tue, 17 May 2016 04:52:35 -0400 Original-Received: from cloud103.planethippo.com ([31.216.48.48]:38800) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b2ajv-0004Sd-4u for 22295@debbugs.gnu.org; Tue, 17 May 2016 04:52:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=russet.org.uk; s=default; h=Content-Type:MIME-Version:References:Message-ID :Date:In-Reply-To:Subject:Cc:To:From; bh=TzxnvNCiZqwoQdpR5XFa0cyIJU0KJiEL9PR0iIwAPKs=; b=nHBmfFz+2u43pfWx9nKLvQ+qMG hSzrR3TuoM4+gfSxpGQV9dQkhK6k1riA+5p5/edZ4lRrXp3WyFAEe9prbh7FsQuarpWcTd+CkL10y o7pSsMIeNKEc4Bw1ZhP6YkZ9fTttrO91nzjZy2qCne/ohMMjOi4Sf6YP1RrGRW/NyAPjiGKawMAZB zEan0ovGiM1QQqv0padd+hUY2oNdy1oH3FOHuKtRmENooxCHavCgtg4lEfXUj+47ndyjYUcYwNXZL UlNxS8PnHWA2VZVadyNjdSYPlVrfAUxQYcJdoMXf3tf+8RKyk0LWA6eqtOQy60oq0wz3M1EP1waVX yGC3+FXw==; Original-Received: from cpc1-benw10-2-0-cust373.gate.cable.virginm.net ([77.98.219.118]:46424 helo=russet.org.uk) by cloud103.planethippo.com with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.86_1) (envelope-from ) id 1b2ajp-000Pci-69; Tue, 17 May 2016 09:52:25 +0100 In-Reply-To: <83twhx529u.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 16 May 2016 20:41:17 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.93 (gnu/linux) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cloud103.planethippo.com X-AntiAbuse: Original Domain - debbugs.gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - russet.org.uk X-Get-Message-Sender-Via: cloud103.planethippo.com: authenticated_id: phillip.lord@russet.org.uk X-Authenticated-Sender: cloud103.planethippo.com: phillip.lord@russet.org.uk 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" Xref: news.gmane.org gmane.emacs.bugs:118346 Archived-At: Eli Zaretskii writes: >> Cc: phillip.lord@russet.org.uk, 22295@debbugs.gnu.org >> From: Michael Kifer >> Date: Mon, 16 May 2016 13:14:05 -0400 >> >> > Another alternative is to make viper use the default Emacs undo, and >> > then ask you and other users of viper to tell where the results don't >> > match your expectations. It could well be that starting with a clean >> > slate will get us to the goal faster and with less complex code. >> >> This would be a non-starter and would cause a mass migration to vim. The undo would also then be >> implementation dependent. If, say, "delete 2 words" is implemented differently from how it is now then it would >> be undone via a different sequence of commands. > > Then I guess the current trial-and-error method will have to be the > way. Too bad, I have hard time believing we will be ready with a > complete solution in time for Emacs 25.1, which is what I hoped. I worry about this as well. I still do not understand why my changes have caused this problem; I'd rather not be taking the approach to redoing the implementation of viper during release candidate. Still, if, as I suspect, it's because the timing of boundaries has changed slightly, it's likely to be the only choice. Phil