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: Sat, 05 Nov 2022 13:24:06 +0200 Message-ID: <834jvd4pbd.fsf@gnu.org> References: <83pme6bls8.fsf@gnu.org> <83mt99a223.fsf@gnu.org> <83cza59tvg.fsf@gnu.org> <83wn8c6u96.fsf@gnu.org> <83bkpn7vmb.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37986"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Nov 05 12:24:27 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 1orHHn-0009fM-1M for ged-emacs-devel@m.gmane-mx.org; Sat, 05 Nov 2022 12:24:27 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1orHHW-00061i-Ev; Sat, 05 Nov 2022 07:24:10 -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 1orHHU-00061a-Un for emacs-devel@gnu.org; Sat, 05 Nov 2022 07:24:08 -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 1orHHU-0002dR-MQ; Sat, 05 Nov 2022 07:24:08 -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=mawZ09ERKVNQTOqNmIff7qy4B60b5aIjW37StrEoYO8=; b=Sb5HU7H2Tsph qPYuPGKUFL9edawmb4vdV+ZDewh7ZDOpikegeg64qIgiLgS4G2pt7gd9IDgemzaot8k5oYp88OpAc 8+DIKyW8xGzEweUKx+Th52KNjEvBMifFIzA6/zIBLemr4Zq7L/7lY9ITjQC5xUXhqK2PZGVu0D0Me llsJ/dcWDQITAxj8aXYZ6f1GJuYFJmwWlpJ/HrHdb9rxU7PjFJ5XIxAc/5ftKOnCjUxxmETSowDfJ 8la3JnWxdNDHHE6KhvW3GEIeoOR0MmMhoFNfQJph9SCf2E4KPw74Fj8VEKlPACFowwHnCH7MTklil 5hb8D9EKZ+J1QasokdxX5Q==; 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 1orHHU-0004gC-4M; Sat, 05 Nov 2022 07:24:08 -0400 In-Reply-To: (message from Alan Mackenzie on Thu, 3 Nov 2022 20:25:12 +0000) 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:299189 Archived-At: > Date: Thu, 3 Nov 2022 20:25:12 +0000 > Cc: emacs-devel@gnu.org > From: Alan Mackenzie > > > > > The node you added is very short, barely a dozen lines. It makes > > > > little sense to have it separate from where edebug-save-windows is > > > > described. So I think you should move it there. The location of the > > > > node inside the manual's hierarchy is much less important than to have > > > > the information pertaining to edebug-save-windows in a single place, > > > > because no one reads the ELisp reference manual in its entirety. The > > > > only thing we need to facilitate people finding this place is add good > > > > index entries there. > > > > So you're proposing leaving the "The outside context" node incomplete, > > > according to its clearly defined purpose, and therefore wrong? Why? > > > If you want, you can add a short sentence there about the issue, with > > a cross-reference to where the issue is described in full. > > "There"? There is no suitable place to put such a link, other than my > new node. Such a strategy would unbalance "The Outside Context" by > having most of its contents in subsubsections, and the bit about point > corruption at the other end of a link, in some random page. > > As a matter of interest, one of the other nodes under "The Outside > Context", namely "Checking Whether to Stop" has just 13 lines. > > > This is how we organize our manuals: when some topic could be relevant > > to more than one situation, we describe it in full in one place, and > > have short references in all the others. > > We should describe it in the PRIMARY relevant place. > > > > Remember, this patch is not about edebug-save-windows. It's about point > > > getting corrupted. > > > The index entries and the cross-references should solve this. And the > > issue _is_ related to edebug-save-windows .... > > It is only tangentially related to edebug-save-windows. It is about > point getting corrupted. An angry victim of this bug should be be able > to find the description by searching for "corrupt". > > > .... and to the other similar option described in the same node. So > > having all of this info there makes the description more > > comprehensive. > > Yes, stuff about options belongs in the "Options" page. Stuff about > point getting corrupted does not, except at the other end of a link. Instead of continuing this endless argument, I prefer to fix this myself, using your text where appropriate. Are you okay with that?