* Re: master 69521ffcb0: Clarify the doc string of 'with-buffer-unmodified-if-unchanged'
[not found] ` <20220504084622.0F678C009A8@vcs2.savannah.gnu.org>
@ 2022-05-04 9:10 ` Lars Ingebrigtsen
2022-05-04 9:30 ` Eli Zaretskii
0 siblings, 1 reply; 4+ messages in thread
From: Lars Ingebrigtsen @ 2022-05-04 9:10 UTC (permalink / raw)
To: emacs-devel; +Cc: Eli Zaretskii
Eli Zaretskii <eliz@gnu.org> writes:
> +Note that only changes in the raw byte sequence of the buffer text,
> +as stored in the internal representation, are monitored for the
> +purpose of detecting the lack of changes in buffer text. Any other
> +changes that are normally perceived as \"buffer modifications\", such
> +as changes in text properties, `buffer-file-coding-system', buffer
> +multibytenes, etc. -- will still cause the buffer to become modified."
This is pretty unclear -- the point is that if BODY does any of those
"buffer modifications", the buffer will won't be marked as modified.
This seems to say the opposite.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: master 69521ffcb0: Clarify the doc string of 'with-buffer-unmodified-if-unchanged'
2022-05-04 9:10 ` master 69521ffcb0: Clarify the doc string of 'with-buffer-unmodified-if-unchanged' Lars Ingebrigtsen
@ 2022-05-04 9:30 ` Eli Zaretskii
2022-05-04 9:54 ` Lars Ingebrigtsen
0 siblings, 1 reply; 4+ messages in thread
From: Eli Zaretskii @ 2022-05-04 9:30 UTC (permalink / raw)
To: Lars Ingebrigtsen; +Cc: emacs-devel
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Wed, 04 May 2022 11:10:05 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > +Note that only changes in the raw byte sequence of the buffer text,
> > +as stored in the internal representation, are monitored for the
> > +purpose of detecting the lack of changes in buffer text. Any other
> > +changes that are normally perceived as \"buffer modifications\", such
> > +as changes in text properties, `buffer-file-coding-system', buffer
> > +multibytenes, etc. -- will still cause the buffer to become modified."
>
> This is pretty unclear -- the point is that if BODY does any of those
> "buffer modifications", the buffer will won't be marked as modified.
> This seems to say the opposite.
Which part(s) say the opposite?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: master 69521ffcb0: Clarify the doc string of 'with-buffer-unmodified-if-unchanged'
2022-05-04 9:30 ` Eli Zaretskii
@ 2022-05-04 9:54 ` Lars Ingebrigtsen
2022-05-04 10:10 ` Eli Zaretskii
0 siblings, 1 reply; 4+ messages in thread
From: Lars Ingebrigtsen @ 2022-05-04 9:54 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: emacs-devel
Eli Zaretskii <eliz@gnu.org> writes:
>> > +multibytenes, etc. -- will still cause the buffer to become modified."
>>
>> This is pretty unclear -- the point is that if BODY does any of those
>> "buffer modifications", the buffer will won't be marked as modified.
>> This seems to say the opposite.
>
> Which part(s) say the opposite?
"Become modified" is most easily interpreted as (buffer-modified-p) => t.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: master 69521ffcb0: Clarify the doc string of 'with-buffer-unmodified-if-unchanged'
2022-05-04 9:54 ` Lars Ingebrigtsen
@ 2022-05-04 10:10 ` Eli Zaretskii
0 siblings, 0 replies; 4+ messages in thread
From: Eli Zaretskii @ 2022-05-04 10:10 UTC (permalink / raw)
To: Lars Ingebrigtsen; +Cc: emacs-devel
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 04 May 2022 11:54:39 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> > +multibytenes, etc. -- will still cause the buffer to become modified."
> >>
> >> This is pretty unclear -- the point is that if BODY does any of those
> >> "buffer modifications", the buffer will won't be marked as modified.
> >> This seems to say the opposite.
> >
> > Which part(s) say the opposite?
>
> "Become modified" is most easily interpreted as (buffer-modified-p) => t.
Ah, yes. Should be fixed now, thanks.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-05-04 10:10 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <165165398176.31589.14519991900728099034@vcs2.savannah.gnu.org>
[not found] ` <20220504084622.0F678C009A8@vcs2.savannah.gnu.org>
2022-05-04 9:10 ` master 69521ffcb0: Clarify the doc string of 'with-buffer-unmodified-if-unchanged' Lars Ingebrigtsen
2022-05-04 9:30 ` Eli Zaretskii
2022-05-04 9:54 ` Lars Ingebrigtsen
2022-05-04 10:10 ` Eli Zaretskii
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).