From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Speed of keyboard macro execution? Date: Fri, 11 Dec 2015 07:27:07 +0100 Message-ID: <87zixhqz44.fsf@fencepost.gnu.org> References: <20151209163954.0cefcc7f@jabberwock.cb.piermont.com> <87si3bcltu.fsf@isaac.fritz.box> <20151209180343.5a67c0e7@jabberwock.cb.piermont.com> <83r3iu9rvp.fsf@gnu.org> <20151210120051.6be8201f@jabberwock.cb.piermont.com> <87k2omciy2.fsf@isaac.fritz.box> <20151210123312.39c417c9@jabberwock.cb.piermont.com> <83lh929omw.fsf@gnu.org> <87k2omta6x.fsf@fencepost.gnu.org> <83d1ue9lns.fsf@gnu.org> <87fuzat7ot.fsf@fencepost.gnu.org> <837fkm9ire.fsf@gnu.org> <20151210151631.3b07c461@jabberwock.cb.piermont.com> <87twnqrqgx.fsf@fencepost.gnu.org> <87h9jqrpa9.fsf@fencepost.gnu.org> <878u51swr0.fsf@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1449823267 8031 80.91.229.3 (11 Dec 2015 08:41:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 11 Dec 2015 08:41:07 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: "Perry E. Metzger" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 11 09:41:06 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 1a7JGD-0001Rm-8f for ged-emacs-devel@m.gmane.org; Fri, 11 Dec 2015 09:41:05 +0100 Original-Received: from localhost ([::1]:46454 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a7JGC-0001rD-9R for ged-emacs-devel@m.gmane.org; Fri, 11 Dec 2015 03:41:04 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34711) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a7JG6-0001nx-SF for emacs-devel@gnu.org; Fri, 11 Dec 2015 03:40:59 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a7JG5-0006M8-RJ for emacs-devel@gnu.org; Fri, 11 Dec 2015 03:40:58 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:37264) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a7JG5-0006M3-Mf; Fri, 11 Dec 2015 03:40:57 -0500 Original-Received: from localhost ([127.0.0.1]:51082 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.82) (envelope-from ) id 1a7JG4-0006Ax-Qv; Fri, 11 Dec 2015 03:40:57 -0500 Original-Received: by lola (Postfix, from userid 1000) id D9763DF4F8; Fri, 11 Dec 2015 07:27:07 +0100 (CET) In-Reply-To: (John Wiegley's message of "Thu, 10 Dec 2015 17:14:48 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) 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:196094 Archived-At: John Wiegley writes: >>>>>> David Kastrup writes: > >> My claim is not about "right" but "useful" behavior. We've had one other >> person state that he switches off visual-line-mode always since keyboard >> macros would otherwise be useless. Of course that's one possibility, but >> visual-line-mode is actually useful for _visual_ navigation. Which is not >> what happens during macro execution since the computer executes the recorded >> keys without human intervention. Which makes sense in _similar_ but not >> identical situations (for identical situations, one could just copy and >> paste the result repeatedly). And non-identical situations will sometimes >> have lines wrapped visually and sometimes not without that being related to >> the structure of the modified text. > > I think we're presupposing what users want, and that is no reason to change a > long-standing default. I'm still waiting for a single example where the current behavior would be actually useful for keyboard macro execution. > You can always disable visual movement during recording and playback > manually; I don't see why it needs to happen automatically now. line-move-visual is not a minor mode. Changing it requires setting of a variable. Setting a variable and resetting it afterwards every time one wants to use keyboard macros requires a different level of expertise than that required to use keyboard macros in the first place. Apart from being a nuisance. > If you want a customization option to auto-disable visual movement > during recording and playback, it should be easy to achieve with > advice. Give it a try for a few months, and then tell me if you really > find it to be a quality of life improvement. If so, I'd welcome the > customization. Can we get a single case where the current behavior would be useful? Just one? Or is this really just an academic exercise? -- David Kastrup