From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Edebug corrupting point in buffers. Date: Wed, 02 Nov 2022 05:28:48 +0200 Message-ID: <83fsf2avbj.fsf@gnu.org> References: <83wn8fcgvd.fsf@gnu.org> <83iljydh7e.fsf@gnu.org> <838rkud9d5.fsf@gnu.org> <83v8nybnuk.fsf@gnu.org> <83pme6bls8.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20114"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acm@muc.de, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 02 04:29:29 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oq4RU-00054P-8b for ged-emacs-devel@m.gmane-mx.org; Wed, 02 Nov 2022 04:29:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oq4R5-0006KH-6D; Tue, 01 Nov 2022 23:29:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oq4R3-0006Jr-C7 for emacs-devel@gnu.org; Tue, 01 Nov 2022 23:29:01 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oq4R3-0001Mo-2X; Tue, 01 Nov 2022 23:29:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=hMCRIeGQYN/jFd+BBZnrXHhilA9MrvTNWZ85NG561Tk=; b=e4Njg+/kfOWw +fO1zZPc3PizOWb5E+a6qXlMjUhJDA/ItEP2IebGAXISc8yAbEM5sxjdBVJfOsswY3WX9GGjXiDhQ J9kphIrDAXgphxXJ0jPmgD9A4r13qbpH+SnNbbRMeOOi3kZUOiWmZP2vAbzby1e6iPhmICwbFgX6z CoA5FwkY68UDHiK4dknPsEBuEXUJ5f/MOEq6Zl+jFyU0f+9dUfX08K26jFgh9egw0bQJbZaB5CkCi yDSSKkij7pIT7wQvps3brgMr9EPCE/sGAxY8dlfUPzW3x6/VPbkJANg/8faId5VDmwu3C7wns0Ekr YpuCfDPjSDvxj2Nu4QTwmA==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oq4R2-0005ie-1g; Tue, 01 Nov 2022 23:29:00 -0400 In-Reply-To: (message from Stefan Monnier on Tue, 01 Nov 2022 15:47:45 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: "Emacs-devel" Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:298991 Archived-At: > From: Stefan Monnier > Cc: Eli Zaretskii , emacs-devel@gnu.org > Date: Tue, 01 Nov 2022 15:47:45 -0400 > > > Why does set-window-configuration overwrite the buffer-points? The > > window configuration does not contain them. The code just assumes that > > the buffer-point should be set to the window point. Of course, we have > > a race condition if a buffer is displayed in several windows. So this > > would appear to be a bug, the root cause of the bug in this thread. > > This suggests the patch below, right? I hope not. We should not change behavior of set-window-configuration easily, certainly not due to this problem. I'm against this patch, sorry.