all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marcin Kasperski <Marcin.Kasperski@mekk.waw.pl>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 15836@debbugs.gnu.org, Marcin Kasperski <Marcin.Kasperski@softax.com.pl>
Subject: bug#15836: 24.3; query-replace-regexp does not detect incorrect usage of \#
Date: Wed, 13 Nov 2013 21:34:58 +0100	[thread overview]
Message-ID: <CAJQm8RbnA2sGmXeQ15U0oLijA-K5wfvnoq5qUfYzOY+S0aZKew@mail.gmail.com> (raw)
In-Reply-To: <jwv4n7m337f.fsf-monnier+emacsbugs@gnu.org>

"Error evaluating replacement expression: ... " would be a bit better,
it would point toward replacement expression as something suspicious.


On Sat, Nov 9, 2013 at 12:15 AM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> Hmm, perhaps replace-eval-replacement could temporarily bind
>> the function definition of replace-count to some informative error
>> message ("\# used in function context")?
>
> Sorry, I don't like this idea.  Much too specific to the particular way
> the user screwed up.
>
> I guess we could byte-compile the expression, which would give the user
> actual warnings about his code before running it, but I'm afraid this
> medicine would be worse than the disease.
>
> Another approach would be to refrain from substituting \# and
> instead to let-bind it during the evaluation.
>
>
>         Stefan





  reply	other threads:[~2013-11-13 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 10:24 bug#15836: 24.3; query-replace-regexp does not detect incorrect usage of \# Marcin Kasperski
2013-11-08 20:27 ` Glenn Morris
2013-11-08 20:35   ` Glenn Morris
2013-11-08 23:15     ` Stefan Monnier
2013-11-13 20:34       ` Marcin Kasperski [this message]
2013-11-13 20:50         ` Glenn Morris

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=CAJQm8RbnA2sGmXeQ15U0oLijA-K5wfvnoq5qUfYzOY+S0aZKew@mail.gmail.com \
    --to=marcin.kasperski@mekk.waw.pl \
    --cc=15836@debbugs.gnu.org \
    --cc=Marcin.Kasperski@softax.com.pl \
    --cc=monnier@iro.umontreal.ca \
    /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.