From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Edebug corrupting point in buffers.
Date: Sat, 5 Nov 2022 16:50:44 +0000 [thread overview]
Message-ID: <Y2aUZEbKo095Vk6d@ACM> (raw)
In-Reply-To: <834jvd4pbd.fsf@gnu.org>
Hello, Eli.
On Sat, Nov 05, 2022 at 13:24:06 +0200, Eli Zaretskii wrote:
> > Date: Thu, 3 Nov 2022 20:25:12 +0000
> > Cc: emacs-devel@gnu.org
> > From: Alan Mackenzie <acm@muc.de>
> > > > > 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?
Yes, I think that would be best. Please do take account of my points
about the "The Outside Context", and put the phrase "corrupted point" (or
something like it) in somewhere.
Thanks!
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2022-11-05 16:50 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 11:43 Edebug corrupting point in buffers; we need buffer-point and set-buffer-point, perhaps Alan Mackenzie
2022-10-31 13:16 ` Eli Zaretskii
2022-10-31 14:32 ` Alan Mackenzie
2022-10-31 14:50 ` Eli Zaretskii
2022-10-31 15:46 ` Alan Mackenzie
2022-10-31 17:33 ` Stefan Monnier
2022-10-31 17:55 ` Eli Zaretskii
2022-10-31 20:46 ` Alan Mackenzie
2022-11-01 6:21 ` Eli Zaretskii
2022-10-31 17:19 ` Stefan Monnier
2022-10-31 18:09 ` Eli Zaretskii
2022-10-31 20:35 ` Stefan Monnier
2022-10-31 17:21 ` Stefan Monnier
2022-10-31 18:10 ` Eli Zaretskii
2022-10-31 23:14 ` Stefan Monnier
2022-11-01 7:06 ` Eli Zaretskii
2022-10-31 21:25 ` Alan Mackenzie
2022-11-01 6:45 ` Eli Zaretskii
2022-11-01 11:41 ` Edebug corrupting point in buffers Alan Mackenzie
2022-11-01 11:53 ` Eli Zaretskii
2022-11-01 13:42 ` Alan Mackenzie
2022-11-01 14:42 ` Eli Zaretskii
2022-11-01 17:06 ` Alan Mackenzie
2022-11-01 17:12 ` Eli Zaretskii
2022-11-01 17:24 ` Alan Mackenzie
2022-11-01 17:57 ` Eli Zaretskii
2022-11-01 19:02 ` Alan Mackenzie
2022-11-01 19:47 ` Stefan Monnier
2022-11-01 20:53 ` Alan Mackenzie
2022-11-01 21:51 ` Stefan Monnier
2022-11-02 10:40 ` Alan Mackenzie
2022-11-02 13:12 ` Stefan Monnier
2022-11-02 13:28 ` Eli Zaretskii
2022-11-02 3:28 ` Eli Zaretskii
2022-11-02 12:53 ` Stefan Monnier
2022-11-02 17:40 ` Juri Linkov
2022-11-02 18:26 ` Eli Zaretskii
2022-11-02 18:36 ` Juri Linkov
2022-11-02 18:52 ` Eli Zaretskii
2022-11-03 17:25 ` Juri Linkov
2022-11-03 18:06 ` Eli Zaretskii
2022-11-03 18:31 ` Juri Linkov
2022-11-02 11:34 ` Alan Mackenzie
2022-11-02 14:00 ` Eli Zaretskii
2022-11-02 16:18 ` Alan Mackenzie
2022-11-02 16:57 ` Eli Zaretskii
2022-11-03 11:32 ` Alan Mackenzie
2022-11-03 13:29 ` Eli Zaretskii
2022-11-03 18:07 ` Alan Mackenzie
2022-11-03 18:15 ` Eli Zaretskii
2022-11-03 20:25 ` Alan Mackenzie
2022-11-05 11:24 ` Eli Zaretskii
2022-11-05 16:50 ` Alan Mackenzie [this message]
2022-11-06 8:10 ` Eli Zaretskii
2022-11-06 14:40 ` Alan Mackenzie
2022-11-03 19:29 ` Stefan Monnier
2022-11-03 19:36 ` Eli Zaretskii
2022-11-03 20:39 ` Stefan Monnier
2022-11-04 6:34 ` Eli Zaretskii
2022-11-04 6:37 ` Eli Zaretskii
2022-11-03 19:57 ` Alan Mackenzie
2022-11-03 20:35 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y2aUZEbKo095Vk6d@ACM \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).