From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Strange font-lock/invisible/intangible bug
Date: Wed, 22 Jan 2003 14:20:01 -0500 [thread overview]
Message-ID: <200301221920.h0MJK1u02273@rum.cs.yale.edu> (raw)
In-Reply-To: 86n0ltgj2n.fsf@mobile.repose.cx
> I've been trying to debug some weird behavior with emacs-wiki.el on
> the nearly-latest CVS (as of about a week ago). emacs-wiki.el uses font-lock
> mode to convert a string of the form "*foo*" to bold, in the process
> propertizing the "*"s as invisible and intangible.
>
> Now, there is a difficult to reproduce bug in the latest CVS which wasn't
> around in previous emacs releases. Sometimes (maybe 1 in 20 times?), when
> typing "*foo* ", point is suddenly moved to the line below. Infact, not just
> space, but any command - Even C-x =, which you'd expect to show no character
> (as I'm at the end of the buffer), instead says "C-j" in the minibuffer and
> point is suddenly moved to the start of the next line. Repeating C-x = now
> indicates that there's no character on point.
>
> The other strange thing is that pressing backspace a few times and repeating
> the same key combination results in it working. But if you undo the previous
> line instead, and type it again, the strange behavior results.
>
> Does anyone have a 'hunch' on where this bug might be, or any tips on how I
> might debug where this is going on? My C knowledge is somewhat rusty.
It's in adjust_point_for_properties. Same problem as reported
earlier for some wnn input method system.
Since both cases show up in conjunction with `intangible' (which
is made unnecessary by the new problematic code), maybe we can simply
disable that code in case there is an `intangible' property around.
I don't have time to try it out right now, but I'll look at it later.
Stefan
next prev parent reply other threads:[~2003-01-22 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 18:01 Strange font-lock/invisible/intangible bug Damien Elmes
2003-01-22 19:20 ` Stefan Monnier [this message]
[not found] ` <200301231301.WAA08276@etlken.m17n.org>
2003-01-23 14:58 ` Damien Elmes
2003-01-23 16:54 ` Stefan Monnier
2003-01-23 11:38 ` Richard Stallman
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=200301221920.h0MJK1u02273@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--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).