From: Nick Roberts <nickrob@snap.net.nz>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-pretest-bug@gnu.org, 451@emacsbugs.donarmstrong.com
Subject: bug#451: 23.0.60; x-gtk-map-stock destroys match data
Date: Sat, 21 Jun 2008 17:07:54 +1200 [thread overview]
Message-ID: <18524.36010.681991.485230@kahikatea.snap.net.nz> (raw)
In-Reply-To: <jwvr6as9o95.fsf-monnier+emacsbugreports@gnu.org>
> > I don't think that's right. The problem goes away if I remove the tool bar.
> > If I do:
> > (string-match "ox" "The quick lazy fox jumped")
> > in the *scratch* buffer then
> > (match-beginning 0)
> > (match-end 0)
> > give me false values immediately afterwards.
> What do you mean "immediately afterwards"? If you get back to the
> toplevel in the mean time, the "immediately" actually runs a crapload of
> code. I.e. it's anything but "immediate". Your expectation is
> just wrong.
I meam using C-x C-e. It looks like you are indeed right and that
match-beginning and match-end can only be used programmatically. I was
using edebug and getting strange values evaluating them (manually). I
thought I had done that before - but clearly not.
Sorry but I don't know how to close the bug report.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-06-21 5:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwvmyle1sk2.fsf-monnier+emacsbugreports@gnu.org>
2008-06-20 2:38 ` bug#451: 23.0.60; x-gtk-map-stock destroys match data Nick Roberts
2008-06-20 14:28 ` Stefan Monnier
2008-06-20 23:01 ` Nick Roberts
2008-06-21 2:27 ` Stefan Monnier
2008-06-21 5:07 ` Nick Roberts [this message]
2008-06-21 19:55 ` bug#451: marked as done (23.0.60; x-gtk-map-stock destroys match data) Emacs bug Tracking System
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=18524.36010.681991.485230@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=451@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
--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 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).