RetroSearch Browse

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

Showing content from https://lists.gnu.org/archive/html/emacs-devel/2022-11/msg00194.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: Thu, 03 Nov 2022 21:36:23 +0200

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Alan Mackenzie <acm@muc.de>,  emacs-devel@gnu.org
> Date: Thu, 03 Nov 2022 15:29:38 -0400
> 
> I wish Someoneâ¢ could dig into the problem further and find the source
> of the problem and an actual fix, but indeed, this seems like a fair
> workaround in the mean time.

I think before digging into the reasons, we should decide what kind of
behavior we would consider "correct" and/or "useful" in the relevant
use cases with Edebug.  The answer is not easy, because AFAIU Edebug
cannot easily know which window(s) and which buffer(s) are affected by
the program being debugged.

Re: Edebug corrupting point in buffers., (continued)
- Re: Edebug corrupting point in buffers; we need buffer-point and set-buffer-point, perhaps., Eli Zaretskii, 2022/11/01

Prev by Date: Re: Edebug corrupting point in buffers.
Next by Date: Re: Edebug corrupting point in buffers.
Previous by thread: Re: Edebug corrupting point in buffers.
Next by thread: Re: Edebug corrupting point in buffers.
Index(es):
- Date
- Thread

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