From: Miles Bader <miles@gnu.org>
To: "Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>
Cc: rms@gnu.org, david.reitter@gmail.com,
Chong Yidong <cyd@stupidchicken.com>,
andrew.w.nosenko@gmail.com, emacs-devel@gnu.org,
monnier@iro.umontreal.ca, raman@users.sourceforge.net
Subject: Re: line-move-visual never set to nil?
Date: Fri, 01 Aug 2008 09:33:40 +0900 [thread overview]
Message-ID: <87wsj160bf.fsf@catnip.gol.com> (raw)
In-Reply-To: <48924CE0.9090603@gmail.com> (Lennart Borgman's message of "Fri, 01 Aug 2008 01:38:08 +0200")
"Lennart Borgman (gmail)" <lennart.borgman@gmail.com> writes:
>> 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?
The point is that it doesn't actually help -- there are a million other
cases that can trip up the user, and the only general solution is for
users to be aware of problems that can crop up during macro replying and
be fairly conservative in how they make macros.
Having commands work _differently_ during macro recording is guaranteed
to confuse people, and doing so will probably cause as many problems as
it "solves".
-Miles
--
自らを空にして、心を開く時、道は開かれる
next prev parent reply other threads:[~2008-08-01 0:33 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 17:43 line-move-visual never set to nil? T. V. Raman
2008-07-26 18:13 ` Stefan Monnier
2008-07-26 18:40 ` Vinicius Jose Latorre
2008-07-26 18:44 ` Stefan Monnier
2008-07-26 18:48 ` David Reitter
2008-07-26 18:57 ` Chong Yidong
2008-07-26 19:38 ` T. V. Raman
2008-07-26 19:41 ` Chong Yidong
2008-07-27 18:46 ` David Reitter
2008-07-27 20:59 ` Stefan Monnier
2008-07-27 21:08 ` Stefan Monnier
2008-07-28 0:23 ` T. V. Raman
2008-07-29 7:43 ` Andrew W. Nosenko
2008-07-29 14:34 ` Chong Yidong
2008-07-29 14:43 ` Lennart Borgman
2008-07-29 16:27 ` Stefan Monnier
2008-07-29 18:31 ` Chong Yidong
2008-07-29 18:37 ` David Reitter
2008-07-29 19:18 ` Chong Yidong
2008-07-29 19:23 ` Lennart Borgman (gmail)
2008-07-29 19:59 ` Stefan Monnier
2008-07-29 21:23 ` David De La Harpe Golden
2008-07-30 0:31 ` Miles Bader
2008-07-30 0:42 ` David Reitter
2008-07-30 3:46 ` Richard M Stallman
2008-07-30 4:43 ` Chong Yidong
2008-07-30 4:56 ` Miles Bader
2008-07-30 7:59 ` Lennart Borgman (gmail)
2008-07-31 17:24 ` Lennart Borgman (gmail)
2008-07-31 23:34 ` Miles Bader
2008-07-31 23:38 ` Lennart Borgman (gmail)
2008-08-01 0:25 ` David De La Harpe Golden
2008-08-01 0:27 ` David De La Harpe Golden
2008-08-01 0:29 ` Lennart Borgman (gmail)
2008-08-01 0:58 ` David De La Harpe Golden
2008-08-01 1:01 ` Lennart Borgman (gmail)
2008-08-01 1:49 ` David De La Harpe Golden
2008-08-01 8:43 ` Lennart Borgman (gmail)
2008-08-01 18:19 ` Richard M Stallman
2008-08-01 19:06 ` Chong Yidong
2008-08-01 19:29 ` Lennart Borgman (gmail)
2008-08-01 0:33 ` Miles Bader [this message]
2008-08-01 0:37 ` Lennart Borgman (gmail)
2008-08-01 0:46 ` Miles Bader
2008-08-01 0:50 ` Lennart Borgman (gmail)
2008-08-01 10:16 ` Andrew W. Nosenko
2008-08-01 4:43 ` Richard M Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wsj160bf.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=andrew.w.nosenko@gmail.com \
--cc=cyd@stupidchicken.com \
--cc=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=raman@users.sourceforge.net \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).