Re: possible emacs bug, need help with repro

[Le Wang]

filed bug http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7946 .  This is the first Emacs bug I've filed in memory.  Does anyone know what the timeline will be like?  I'd like to give any additional details while I have it fresh in mind.

On Mon, Jan 31, 2011 at 4:33 AM, Stephen Berman <stephen.berman@gmx.net> wrote:

On Sun, 30 Jan 2011 23:59:07 +0800 Le Wang <l26wang@gmail.com> wrote:

> Hi all,
>
>
> I discovered a weird issue with Emacs that I reproed with NTEmacs 23.2.1 and
> CVS build from 20110112.
>
> I need someone to follow some of these steps to see if they can repro the same
> thing on another platform before I file a bug report.  You need the
> "rebox2.el" attached.
>

> 1 emacs -Q rebox2_bug.el
>
> 2 M-x eval-current-buffer
>
> 3 C-x b<enter> ;; switch to "*scratch*"
>
> 4 M-x rebox-mode
>
> 5 M-<
>
> 6 SPC,SPC ;; space twice
>
> 7 C-aC-aC-aC-a ;; notice that the point is stuck at 6
>
> 8 C-xb<enter> ;; switch to "rebox2_bug.el
>
> 9 M-g g 1714
>
> 10 C-d ;; uncomment the hack workaround the bug
>
> 11 C-M-x ;; reevaluated the function 
>
> 12 C-x b<enter> ;; switch to "*scratch*"
>
> 13 C-aC-aC-aC-a ;; notice that the cursor switches between 1 and 6

>
> So step 10 fixed the issue I was debugging with rebox2, however, it does
> nothing except refer to the marker "marked-point" in a format call.
>
>
>     (format "%s" marked-point)
>
>
> How can this line change Emacs' behaviour?
>
> If you try the steps, please let me know if you can confirm my observations.
>  Thanks.

I get the same behavior you observed on GNU Emacs 24.0.50.1
(i686-pc-linux-gnu, GTK+ Version 2.20.1) of 2011-01-13 on escher

Steve Berman

-- 
Le