From: Carsten Dominik <dominik@science.uva.nl>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [bug]org-mode with flyspell-mode freezes emacs
Date: Tue, 17 Oct 2006 12:57:22 +0200 [thread overview]
Message-ID: <4d08b83ef805bfb7828085d8e1f67daf@science.uva.nl> (raw)
In-Reply-To: <17716.23811.425109.929050@kahikatea.snap.net.nz>
On Oct 17, 2006, at 6:33, Nick Roberts wrote:
>> Anyway, I do now have a backtrace for this problem. Can anyone
>> extract
>> something useful from this?
>
> If Emacs is hanging, a static backtrace is unlikely to be much use.
> You need
> to follow the instructions in DEBUG:
I have not been able to do this well, the results are very confusing to
me, I sometimes end up in the garbage collection, sometimes in search
functions like looking-at-1 or search-buffer. So for now I don't have
better information on this bug, and I don't have much time for going
much further on this.
However, on the Lisp level, I have been able to dig deeper and found
the following.
This error happens if flyspell is trying to check a word that is
followed by a character with the `intangible' text property. The words
in the buffer where Emacs enters an infinite loop look like this
something]]
where the "]]" carry both the invisible and the intangible text
property. If I remove the intangible text property and only keep
invisible, there is no problem and Emacs functions normally. If I
remove invisible and keep intangible, the error still happens.
> Also when a C backtrace is useful, it usually helps to include lisp
> backtrace.
> This is output automatically with `bt' if you run Emacs under GDB from
> the src
> directory otherwise you need to source .gdbinit (in the src directory)
> first.
A typical lisp backtrace looks like this:
Lisp Backtrace:
"flyspell-get-word" (0x3800209)
"flyspell-word-search-backward" (0x1add4e3)
"flyspell-word" (0x3800209)
"flyspell-post-command-hook" (0x0)
"run-hooks" (0x3809c69)
or
Lisp Backtrace:
"re-search-forward" (0x1b0d1b3)
"flyspell-get-word" (0x3800209)
"flyspell-word-search-backward" (0x1add4e3)
"flyspell-word" (0x3800209)
"flyspell-post-command-hook" (0x0)
"run-hooks" (0x3809c69)
This is strange because it looks like there is an infinite loop on the
lisp level, but when I use the lisp debugger, it is the call to
accept-process-output where Emacs gets stuck.
I guess as a temporary fix I could remove the intangible text property,
since invisible text is handled by the point-motion functions much like
intangible text, so it is not really necessary to have both. Is this a
correct assessment?
Thanks, and sorry that I cannot be more helpful.
- Carsten
next prev parent reply other threads:[~2006-10-17 10:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 4:20 [bug]org-mode with flyspell-mode freezes emacs Richard Stallman
2006-10-16 7:55 ` Carsten Dominik
2006-10-16 9:01 ` Carsten Dominik
2006-10-16 18:47 ` Richard Stallman
2006-10-17 4:33 ` Nick Roberts
2006-10-17 10:57 ` Carsten Dominik [this message]
2006-10-17 13:13 ` Carsten Dominik
2006-10-17 14:18 ` martin rudalics
2006-10-17 17:49 ` martin rudalics
2006-10-17 21:11 ` Carsten Dominik
2006-10-17 22:03 ` Stefan Monnier
2006-10-17 22:09 ` Lennart Borgman
2006-10-17 22:14 ` David Kastrup
2006-10-17 22:26 ` Lennart Borgman
2006-10-17 22:38 ` David Kastrup
2006-10-17 22:44 ` Drew Adams
2006-10-17 22:38 ` Carsten Dominik
2006-10-17 22:49 ` David Kastrup
2006-10-18 4:26 ` Carsten Dominik
2006-10-18 7:35 ` David Kastrup
2006-10-20 22:05 ` Michael Olson
2006-10-21 6:13 ` David Kastrup
2006-10-21 18:30 ` Michael Olson
2006-10-23 5:11 ` Richard Stallman
2006-10-23 13:00 ` Michael Olson
2006-10-22 0:24 ` Stefan Monnier
2006-10-22 16:39 ` David Kastrup
2006-10-18 0:28 ` Stefan Monnier
2006-10-18 4:26 ` Carsten Dominik
2006-10-18 4:14 ` Chong Yidong
2006-10-17 18:40 ` Richard Stallman
2006-10-17 20:45 ` martin rudalics
2006-10-18 10:41 ` Richard Stallman
[not found] <m2lknmthc4.fsf@sl392.st-edmunds.cam.ac.uk>
2006-10-12 16:57 ` Leo
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=4d08b83ef805bfb7828085d8e1f67daf@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-devel@gnu.org \
--cc=rms@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).