From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: read-file-name error-handling problem
Date: Fri, 30 Aug 2002 15:17:53 -0400 [thread overview]
Message-ID: <E17krHF-0004cm-00@fencepost.gnu.org> (raw)
In-Reply-To: <20020829204055.222280.FMU32625@piglet.prv.splode.com> (message from Noah Friedman on Thu, 29 Aug 2002 20:40:55 -0700 (PDT))
>I figured out the cause of this. The minibuffer's recursive edit
>comes inside your condition-case, and it established an environment
>where the debugger is allowed to run.
>
>It may not be the result that you want, but I am not sure it is a bug.
How do I avoid it?
You would have to solve your problem differently. Sorry, but I'd
rather not work on this.
prev parent reply other threads:[~2002-08-30 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-10 17:40 read-file-name error-handling problem Noah Friedman
2002-08-12 17:06 ` Richard Stallman
2002-08-12 17:47 ` Richard Stallman
2002-08-30 3:40 ` Noah Friedman
2002-08-30 19:17 ` Richard Stallman [this message]
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=E17krHF-0004cm-00@fencepost.gnu.org \
--to=rms@gnu.org \
--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 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).