From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Redisplay hook Date: Mon, 04 Jul 2016 17:52:09 +0300 Message-ID: <83h9c5piau.fsf@gnu.org> References: <577814F4.8060500@gmail.com> <8360sns8nj.fsf@gnu.org> <57789637.8020204@gmail.com> <83twg7qi5t.fsf@gnu.org> <5779A83D.6020201@gmail.com> <83twg6p1kd.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1467643977 7938 80.91.229.3 (4 Jul 2016 14:52:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 Jul 2016 14:52:57 +0000 (UTC) Cc: clement.pit@gmail.com, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 04 16:52:50 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bK5Ev-0006yM-TG for ged-emacs-devel@m.gmane.org; Mon, 04 Jul 2016 16:52:50 +0200 Original-Received: from localhost ([::1]:48389 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bK5Ev-000740-5f for ged-emacs-devel@m.gmane.org; Mon, 04 Jul 2016 10:52:49 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59576) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bK5Ep-00073u-3N for emacs-devel@gnu.org; Mon, 04 Jul 2016 10:52:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bK5El-0004u6-3a for emacs-devel@gnu.org; Mon, 04 Jul 2016 10:52:43 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:56443) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bK5El-0004u2-0D; Mon, 04 Jul 2016 10:52:39 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1921 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bK5Ei-0007x8-As; Mon, 04 Jul 2016 10:52:37 -0400 In-reply-to: (message from Stefan Monnier on Mon, 04 Jul 2016 03:55:05 -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:205134 Archived-At: > From: Stefan Monnier > Cc: Clément Pit--Claudel , > emacs-devel@gnu.org > Date: Mon, 04 Jul 2016 03:55:05 -0400 > > I don't have a clear recollection either, sorry. It happens ;-) > I guess part of the question is what would be the use of such a hook. > The difference between a pre-redisplay-hook and a > post-redisplay-hook is not very large since most of the result of > redisplay is "invisible" to Elisp. The main differences I can think of > would be: > - jit-lock stuff, in case you want to see the buffer after jit-locking. > but it seems you can just as well hook into jit-lock to get > that result. > - scrolling, in case you want to react to changes in the user-visible > window-start/end. The use case which started this thread is yet another use case which definitely wants to run after a frame was updated. > Of course the use could be fairly tricky, with risks of the > post-redisplay-hook causing further redisplay-cycle ad-nauseam, but we > already have this problem with the window-scroll-functions, IIRC. Yes, getting this solved should be part of the job. Thanks.