Subject: bug#31888: 27.0.50; Segmentation fault in replace-buffer-contents

From: Eli Zaretskii <[email-masked]>
Date: Fri, 29 Jun 2018 22:09:36 +0300

> From: João Távora <[email-masked]>
> Cc: [email-masked],  [email-masked],  [email-masked],  [email-masked]
> Date: Fri, 29 Jun 2018 20:04:58 +0100
> 
> >> Is that worth the hassle?  The caller asked to replace the entire
> >> buffer by something else, why should they expect after-change hooks to
> >> be run on something other than the entire buffer?
> >
> > s/entire buffer/entire accessible portion of buffer/g
> 
> FWIW I use this on potentially small sections of the buffer, by first
> narrowing down to it.

In that case, the after-change hook will be called on the narrowed
portion of the buffer.