A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://lists.gnu.org/archive/html/emacs-devel/2022-11/msg00115.html below:

Re: Edebug corrupting point in buffers.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] From: Eli Zaretskii Subject: Re: Edebug corrupting point in buffers. Date: Wed, 02 Nov 2022 16:00:52 +0200 
> Date: Wed, 2 Nov 2022 11:34:37 +0000
> Cc: emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
> 
> (i) Emacs -Q.
> (ii) On a single frame, arrange buffers *scratch*, test-edebug.el, and
>   some other substantial buffer, that I call emacs.README.
> (iii) Put point in emacs.README somewhere other than point-max.
> (iv) Instrument test-edebug for edebug with C-u C-M-x.
> (iv)a Put point into window *scratch*.
> (v) M-: (test-edebug).
> (vi) Step through test-edebug using the space key.
> (vii) Note that the second text insertion happens where point was in the
>   window, not at point-max.  This is the bug.

Yes, I see the problem, but setting edebug-save-windows to nil
eliminates it.  So I think we already have a solution for the rare
situations where this is an issue.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4