From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: hack-local-variables-confirm loops forever when running keyboard macro
Date: Mon, 22 Jan 2007 12:48:19 -0500 [thread overview]
Message-ID: <87fya3rlzw.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1H8WWI-0001Sx-KD@fencepost.gnu.org> (Richard Stallman's message of "Sun\, 21 Jan 2007 01\:49\:38 -0500")
Richard Stallman <rms@gnu.org> writes:
> Would someone please fix this, then ack?
I don't think any fix is necessary---one simply ought to be careful
when defining keyboard macros to avoid situations like this. Note
that C-g successfully breaks the loop, as it should.
> From: Chris Moore <dooglus@gmail.com>
> Subject: hack-local-variables-confirm loops forever when running keyboard macro
> To: emacs-pretest-bug@gnu.org, Chris Moore <dooglus@gmail.com>
> Cc:
>
> 1. ensure temp file doesn't exist
>
> $ rm /tmp/file.txt
>
> 2. create a temp file with 'risky' local variable:
>
> $ printf "# Local Variables:\n# eval: (put 'w 't 'f)\n# End:\n" > /tmp/file.txt
>
> 3. run Emacs:
>
> $ emacs -Q
>
> 4. visit the temp file. it will prompt for whether to run the risky
> code:
>
> C-x C-f /tmp/file.txt RET
>
> 5. answer that you don't want to run it:
>
> n
>
> 6. start recording a macro:
>
> C-x (
>
> 7. visit the risky temp file. it won't prompt this time, since the
> file is already visited
>
> C-x C-f /tmp/file.txt RET
>
> 8. stop recording the macro
>
> C-x )
>
> 9. kill the temp file's buffer
>
> C-x k RET
>
> 10. run the macro. Emacs will hang forever:
>
> C-x e
next prev parent reply other threads:[~2007-01-22 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 6:49 hack-local-variables-confirm loops forever when running keyboard macro Richard Stallman
2007-01-22 17:48 ` Chong Yidong [this message]
2007-01-22 20:10 ` Kim F. Storm
2007-01-23 2:07 ` Richard Stallman
2007-01-23 3:23 ` Chong Yidong
2007-01-24 8:22 ` Richard Stallman
2007-01-27 10:02 ` Chris Moore
2007-01-27 19:28 ` Chong Yidong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fya3rlzw.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.