From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Lennart Borgman (gmail)" Newsgroups: gmane.emacs.devel Subject: Re: line-move-visual never set to nil? Date: Fri, 01 Aug 2008 01:38:08 +0200 Message-ID: <48924CE0.9090603@gmail.com> References: <18571.25125.311010.324079@gargle.gargle.HOWL> <87od4k1nj5.fsf@stupidchicken.com> <1F7E32D0-7C19-4950-94DB-F6CD33A56EB0@gmail.com> <6161f3180807290043l2b0cc1as85a338204687f183@mail.gmail.com> <87y73kbvz3.fsf@stupidchicken.com> <4891F546.2080505@gmail.com> <8763ql7hmk.fsf@catnip.gol.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1217547543 9789 80.91.229.12 (31 Jul 2008 23:39:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 31 Jul 2008 23:39:03 +0000 (UTC) Cc: rms@gnu.org, david.reitter@gmail.com, Chong Yidong , andrew.w.nosenko@gmail.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca, raman@users.sourceforge.net To: Miles Bader Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 01 01:39:52 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KOhkM-0000la-PU for ged-emacs-devel@m.gmane.org; Fri, 01 Aug 2008 01:39:51 +0200 Original-Received: from localhost ([127.0.0.1]:53010 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KOhjR-0006np-1H for ged-emacs-devel@m.gmane.org; Thu, 31 Jul 2008 19:38:53 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KOhjF-0006eq-RF for emacs-devel@gnu.org; Thu, 31 Jul 2008 19:38:41 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KOhjC-0006aB-7a for emacs-devel@gnu.org; Thu, 31 Jul 2008 19:38:41 -0400 Original-Received: from [199.232.76.173] (port=38211 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KOhjC-0006a3-1M for emacs-devel@gnu.org; Thu, 31 Jul 2008 19:38:38 -0400 Original-Received: from ch-smtp02.sth.basefarm.net ([80.76.149.213]:40890) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KOhiz-0004dS-RE; Thu, 31 Jul 2008 19:38:26 -0400 Original-Received: from c83-254-151-176.bredband.comhem.se ([83.254.151.176]:59331 helo=[127.0.0.1]) by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1KOhiw-0000CR-6V; Fri, 01 Aug 2008 01:38:22 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 In-Reply-To: <8763ql7hmk.fsf@catnip.gol.com> X-Antivirus: avast! (VPS 080731-0, 2008-07-31), Outbound message X-Antivirus-Status: Clean X-Originating-IP: 83.254.151.176 X-ACL-Warn: Too high rate of unknown addresses received from you X-Scan-Result: No virus found in message 1KOhiw-0000CR-6V. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1KOhiw-0000CR-6V e6f51e8d93b7c3343919d3c240d8574a X-detected-kernel: by monty-python.gnu.org: Linux 2.6? (barebone, rare!) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:101833 Archived-At: Miles Bader wrote: > "Lennart Borgman (gmail)" writes: >>> If a command normally moves by screen lines, making it do something >>> different in a keyboard macro is incorrect. >> Wouldn't it be more correct to say that the requirement is that during >> execution of the macro the command should do the same thing to the >> buffer as during recording of the macro? >> >> This mean that if for example the command changes point then this change >> must be independent of the window size. > > Macros do not -- and cannot -- make any guarantees about what happens if > you execute them in a different environment, or on different text, than > where they were recorded. Do you mean that there is something that prevents us from temporary turning things off during keyboard macro recording and execution? In that case: what?