From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18504@debbugs.gnu.org
Subject: bug#18504: 24.3.93; posn-at-point intermittently returns wrong value for a valid buffer position
Date: Fri, 19 Sep 2014 17:29:31 +0400 [thread overview]
Message-ID: <541C2FBB.3030008@yandex.ru> (raw)
In-Reply-To: <83a95v21qr.fsf@gnu.org>
On 09/19/2014 05:12 PM, Eli Zaretskii wrote:
>> Wouldn't setting a conditional breakpoint help?
>
> Conditional breakpoint where?
In the "call a function" routine, maybe? If the function is
"posn-at-point", and if its returned X coord is zero, halt!
Doing it in Elisp doesn't seem to produce the desired result, because
edebug doesn't exactly stop Emacs in place.
> With these issues, the only way to find the bug is to step through the
> offending code _before_ it produces the wrong values. So we need a
> condition that happens at the beginning of that code, not where it
> produces the final wrong results.
If `posn-at-point' is itself stateless (and doesn't modify any relevant
caches), why not call it again at that point?
next prev parent reply other threads:[~2014-09-19 13:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 0:56 bug#18504: 24.3.93; posn-at-point intermittently returns wrong value for a valid buffer position Dmitry
2014-09-19 6:21 ` Eli Zaretskii
2014-09-19 10:25 ` Dmitry Gutov
2014-09-19 13:12 ` Eli Zaretskii
2014-09-19 13:29 ` Dmitry Gutov [this message]
2014-09-19 13:35 ` Eli Zaretskii
2014-09-19 13:46 ` Dmitry Gutov
2014-09-19 14:00 ` Eli Zaretskii
2014-09-19 14:06 ` Dmitry Gutov
2014-09-19 14:21 ` Eli Zaretskii
2014-09-19 19:33 ` Dmitry Gutov
2014-09-20 7:13 ` Eli Zaretskii
2014-09-23 18:39 ` Dmitry Gutov
2014-09-23 19:16 ` Eli Zaretskii
2014-09-19 14:54 ` Eli Zaretskii
2014-09-19 17:52 ` Dmitry Gutov
2014-09-19 19:35 ` Eli Zaretskii
2014-09-19 19:38 ` Dmitry Gutov
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=541C2FBB.3030008@yandex.ru \
--to=dgutov@yandex.ru \
--cc=18504@debbugs.gnu.org \
--cc=eliz@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).