From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, 31888@debbugs.gnu.org, monnier@IRO.UMontreal.CA,
k.michal@zoho.com
Subject: bug#31888: 27.0.50; Segmentation fault in replace-buffer-contents
Date: Fri, 29 Jun 2018 20:04:58 +0100 [thread overview]
Message-ID: <87wouhjtwl.fsf@gmail.com> (raw)
In-Reply-To: <837emho5kn.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 29 Jun 2018 20:39:20 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: acm@muc.de, 31888@debbugs.gnu.org, joaotavora@gmail.com, k.michal@zoho.com
>>
>> 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. OTOH I have no need for modification hooks. And
if I did, I'd probably use a simpler region-replacing strategy for every
region besides the one where point is.
João
next prev parent reply other threads:[~2018-06-29 19:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 13:12 bug#31888: 27.0.50; Segmentation fault in replace-buffer-contents Michał Kondraciuk
2018-06-18 21:50 ` bug#31888: Milan Stanojević
2018-06-22 13:03 ` bug#31888: 27.0.50; Segmentation fault in replace-buffer-contents Eli Zaretskii
2018-06-23 11:15 ` Eli Zaretskii
2018-06-25 10:49 ` João Távora
2018-06-25 14:54 ` Eli Zaretskii
2018-06-25 15:55 ` João Távora
2018-06-29 14:07 ` Eli Zaretskii
2018-06-29 14:51 ` Stefan Monnier
2018-06-29 15:23 ` Eli Zaretskii
2018-06-29 16:57 ` Stefan Monnier
2018-06-29 17:34 ` Eli Zaretskii
2018-06-29 17:39 ` Eli Zaretskii
2018-06-29 19:04 ` João Távora [this message]
2018-06-29 19:09 ` Eli Zaretskii
2018-06-30 8:33 ` João Távora
2018-06-30 11:03 ` Eli Zaretskii
2018-06-30 13:28 ` João Távora
2018-06-29 20:40 ` Stefan Monnier
2018-06-30 7:44 ` Eli Zaretskii
2018-06-30 12:54 ` Stefan Monnier
2018-06-30 13:51 ` Eli Zaretskii
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=87wouhjtwl.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=31888@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=k.michal@zoho.com \
--cc=monnier@IRO.UMontreal.CA \
/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).