bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#9642: closed (Re: bug#9642: move-overlay creates an empty overlay wi


From: Tassilo Horn
Subject: bug#9642: closed (Re: bug#9642: move-overlay creates an empty overlay with the evaporate property)
Date: Thu, 26 Apr 2012 17:30:27 +0200
User-agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/24.1.50 (gnu/linux)

address@hidden (GNU bug Tracking System) writes:

Hi Paul,

> Your bug report
>
> #9642: move-overlay creates an empty overlay with the evaporate property
>
> which was filed against the emacs package, has been closed.

I think your fix (revno 108012) has some bad side effects.  At least
since I updated my emacs checkout today from a 3-4 days old version, I
frequently get errors like this one:

--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (error "Marker does not point anywhere")
  overlays-in(1 54815)
  preview-clearout(1 54815 (20377 23663))
  preview-kill-buffer-cleanup()
  kill-buffer("expose.tex")
  call-interactively(kill-buffer nil nil)
--8<---------------cut here---------------end--------------->8---

That one happened when trying to kill a LaTeX-mode (AUCTeX) buffer.
I've tried moving point or setting mark, but that didn't change
anything.  I couldn't kill the buffer.  Then I've hit C-< which resulted
in an emacs freeze that couldn't be recovered from with C-g.  I had to
kill it.

Before that, I already had two freezes where I had to kill emacs where
that error was triggered from some function in `post-command-hook'.

Sadly, I have no recipe how to reproduce that issue.  But I'll start
running emacs from the debugger to get a backtrace the next time it
happens.

Should I append to this already closed bug report, or should I file a
new one?

Bye,
Tassilo





reply via email to

[Prev in Thread] Current Thread [Next in Thread]