From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Message's text-properties in *Messages* Date: Wed, 30 May 2018 22:55:06 +0300 Message-ID: <83po1chqat.fsf@gnu.org> References: <20180521171019.GA5750@ACM> <83a7sqcmnw.fsf@gnu.org> <83603eckk6.fsf@gnu.org> <83tvqpgix5.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1527709999 7796 195.159.176.226 (30 May 2018 19:53:19 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 30 May 2018 19:53:19 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 30 21:53:15 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fO79k-0001q7-1H for ged-emacs-devel@m.gmane.org; Wed, 30 May 2018 21:53:12 +0200 Original-Received: from localhost ([::1]:40549 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fO7Br-0005TS-0O for ged-emacs-devel@m.gmane.org; Wed, 30 May 2018 15:55:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34162) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fO7Bh-0005SD-Ic for emacs-devel@gnu.org; Wed, 30 May 2018 15:55:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fO7Be-0001X9-IJ for emacs-devel@gnu.org; Wed, 30 May 2018 15:55:13 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:34494) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fO7Be-0001Wv-Eo; Wed, 30 May 2018 15:55:10 -0400 Original-Received: from [176.228.60.248] (port=1672 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fO7Bd-0005AI-EU; Wed, 30 May 2018 15:55:09 -0400 In-reply-to: (message from Stefan Monnier on Wed, 30 May 2018 15:44:08 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:225832 Archived-At: > From: Stefan Monnier > Cc: emacs-devel@gnu.org > Date: Wed, 30 May 2018 15:44:08 -0400 > > > As I wrote previously, redisplay is not the issue here, as > > message_dolog doesn't call any redisplay entry points. > > Hmm... indeed I'm not worried about message_dolog calling redisplay, > instead I think the worry is about redisplay calling message_dolog > (probably via `message` or some variant thereof). I don't think this happens, and I don't think it could work for redisplay to call 'message' or its ilk. Do you see any such calls? > And in that case, we could also replace message_dolog with > message_dolog_lisp (if needed, building a fresh new Lisp string from > a char*). Probably, although it could be cumbersome with some of the current callers.