From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Reliable after-change-functions (via: Using incremental parsing
 in Emacs)
Date: Wed, 01 Apr 2020 17:55:35 +0300
Message-ID: <83blobz254.fsf@gnu.org>
References: <jwv8sjjt3ym.fsf-monnier+emacs@gnu.org> <xjfo8sfhtgq.fsf@sdf.org>
 <83o8sf3r7i.fsf@gnu.org>
 <A930C630-1AA1-40A1-9A62-2968ECDAAC6A@gmail.com>
 <jwv5zelrigd.fsf-monnier+emacs@gnu.org>
 <2E218879-0F24-4A20-B210-263C8D0BEEA4@gmail.com> <838sjh2red.fsf@gnu.org>
 <jwvd08tkytx.fsf-monnier+emacs@gnu.org> <83369o3bvb.fsf@gnu.org>
 <jwvpncsk1x9.fsf-monnier+emacs@gnu.org> <83imik1qbq.fsf@gnu.org>
 <jwv369ojw9r.fsf-monnier+emacs@gnu.org> <835zek1kpv.fsf@gnu.org>
 <f4023fa9-4365-261f-9e46-4cc3d8f598d1@yandex.ru> <83v9mkz5oo.fsf@gnu.org>
 <e4de67da-f8b2-9280-5ad8-8685f096ce4a@yandex.ru> <83pncsym6l.fsf@gnu.org>
 <4a9d6bb2-458d-89b0-5389-d1f883ef24a1@yandex.ru>
 <D0DF3DEF-0582-49F8-8A06-758E3392DC68@gnu.org>
 <74f34b72-725d-2390-faea-c61daad43350@yandex.ru> <83eet7z4if.fsf@gnu.org>
Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202";
	logging-data="102096"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: casouri@gmail.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
 akrl@sdf.org
To: dgutov@yandex.ru
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Apr 01 16:56:07 2020
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1jJemk-000QQb-H1
	for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Apr 2020 16:56:06 +0200
Original-Received: from localhost ([::1]:33202 helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1jJemj-0002Dy-Gb
	for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Apr 2020 10:56:05 -0400
Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37137)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <eliz@gnu.org>) id 1jJem7-0001Oj-Fj
 for emacs-devel@gnu.org; Wed, 01 Apr 2020 10:55:28 -0400
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34219)
 by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <eliz@gnu.org>)
 id 1jJem6-0006Jw-QC; Wed, 01 Apr 2020 10:55:26 -0400
Original-Received: from [176.228.60.248] (port=3770 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <eliz@gnu.org>)
 id 1jJem4-0000lM-1I; Wed, 01 Apr 2020 10:55:26 -0400
In-Reply-To: <83eet7z4if.fsf@gnu.org> (message from Eli Zaretskii on Wed, 01
 Apr 2020 17:04:24 +0300)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Original-Sender: "Emacs-devel"
 <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Xref: news.gmane.io gmane.emacs.devel:246196
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/246196>

> Date: Wed, 01 Apr 2020 17:04:24 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: casouri@gmail.com, akrl@sdf.org, monnier@iro.umontreal.ca,
>  emacs-devel@gnu.org
> 
> What I did was start the profiler, then manually call got-char, then
> produce the profiler report.

That came out confusingly unclear.  What I actually did was start the
profiler, then evaluate the form that visits xdisp.c and goes to
point-max, then call profiler-report.