[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#70077: An easier way to track buffer changes
From: |
Eli Zaretskii |
Subject: |
bug#70077: An easier way to track buffer changes |
Date: |
Mon, 08 Apr 2024 21:36:41 +0300 |
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 70077@debbugs.gnu.org, acm@muc.de, yantar92@posteo.net
> Date: Mon, 08 Apr 2024 13:17:37 -0400
>
> > Name Type Default
> > ———— ———— ———————
> > beg t (point-max)
> > end t (point-min)
> > before t nil
> > next t nil
> >
> > BEG..END is the area that was changed and BEFORE is its previous
> > content[...]
>
> OK, I'll switch the two, thanks.
>
> > (Btw, those "t" under "Type" are also somewhat mysterious. What do
> > they signify?)
>
> `C-h o t RET` says:
>
> t’s value is t
>
> Not documented as a variable.
>
> Probably introduced at or before Emacs version 16.
>
>
>
> t is also a type.
>
> t is a type (of kind ‘built-in-class’).
> Children ‘sequence’, ‘atom’.
>
> Abstract supertype of everything.
>
> This is a built-in type.
If this indicates that the slots are of built-in-class type, why do we
show the cryptic t there?
> >> >> +By default SIGNAL is called as soon as convenient after a change,
> >> >> which is
> >> > ^^^^^^^^^^^^^^^^^^^^^
> >> > "as soon as it's convenient", I presume?
> >> Other than the extra " it's", what is the difference?
> > Nothing. I indeed thing "it's" is missing there.
>
> My local native-English representative says that "both work fine"
> (somewhat dismissively, I must add).
In that case I'll yield, but do note that it got me stumbled.
> > In general, when I want to create a clean slate, I don't care too much
> > about the dirt I remove. Why is it important to signal errors because
> > a state I am dumping had some errors?
>
> I don't understand why you think it will signal an error?
Doesn't cl-assert signal an error if the condition is false?
> More to the point, it should signal an error only if I made a mistake in
> `track-changes.el` or if you messed with the internals.
I have the latter possibility in mind, yes. Why catch me doing that
when I'm cleaning up my mess, _after_ all the damage, such as it is,
was already done?
> >> >> +;;;; Extra candidates for the API.
> >> >> +;; This could be a good alternative to using a temp-buffer like I used
> >> >> in
> >> > ^^^^^^
> >> > "I"?
> >> Yes, that refers to the code I wrote.
> > We don't usually leave such style in long-term comments and
> > documentation.
>
> `grep " I " lisp/**/*.el` suggests otherwise.
"A journey of a thousand miles begins with one first step."
- bug#70077: An easier way to track buffer changes, (continued)
bug#70077: An easier way to track buffer changes, Stefan Monnier, 2024/04/05
- bug#70077: An easier way to track buffer changes, Eli Zaretskii, 2024/04/06
- bug#70077: An easier way to track buffer changes, Stefan Monnier, 2024/04/08
- bug#70077: An easier way to track buffer changes, Eli Zaretskii, 2024/04/08
- bug#70077: An easier way to track buffer changes, Stefan Monnier, 2024/04/08
- bug#70077: An easier way to track buffer changes, Andrea Corallo, 2024/04/08
- bug#70077: An easier way to track buffer changes,
Eli Zaretskii <=
- bug#70077: An easier way to track buffer changes, Stefan Monnier, 2024/04/08
- bug#70077: An easier way to track buffer changes, Eli Zaretskii, 2024/04/09
bug#70077: An easier way to track buffer changes, Stefan Monnier, 2024/04/08
bug#70077: An easier way to track buffer changes, Eli Zaretskii, 2024/04/08
bug#70077: An easier way to track buffer changes, Stefan Monnier, 2024/04/09
bug#70077: An easier way to track buffer changes, Stefan Monnier, 2024/04/13
bug#70077: An easier way to track buffer changes, Dmitry Gutov, 2024/04/06