From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [RFC PATCH] Per-window face support Date: Thu, 07 Jun 2018 23:53:51 -0400 Message-ID: References: <5e08587a56ad528599ed5fb259be6335.squirrel@dancol.org> <5aac4e92-1fd7-193b-803c-a573b9ce6d28@dancol.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1528429926 11200 195.159.176.226 (8 Jun 2018 03:52:06 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 8 Jun 2018 03:52:06 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 08 05:52:01 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 1fR8RV-0002mO-Mm for ged-emacs-devel@m.gmane.org; Fri, 08 Jun 2018 05:52:01 +0200 Original-Received: from localhost ([::1]:32903 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fR8Ta-0002Zm-UE for ged-emacs-devel@m.gmane.org; Thu, 07 Jun 2018 23:54:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46672) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fR8TS-0002Yg-Oy for emacs-devel@gnu.org; Thu, 07 Jun 2018 23:54:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fR8TN-0006Lo-SW for emacs-devel@gnu.org; Thu, 07 Jun 2018 23:54:02 -0400 Original-Received: from chene.dit.umontreal.ca ([132.204.246.20]:40795) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fR8TN-0006L9-Mp for emacs-devel@gnu.org; Thu, 07 Jun 2018 23:53:57 -0400 Original-Received: from pastel.home (lechon.iro.umontreal.ca [132.204.27.242]) by chene.dit.umontreal.ca (8.14.7/8.14.1) with ESMTP id w583sIrl006414; Thu, 7 Jun 2018 23:54:18 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id ECA4D656CB; Thu, 7 Jun 2018 23:53:51 -0400 (EDT) In-Reply-To: <5aac4e92-1fd7-193b-803c-a573b9ce6d28@dancol.org> (Daniel Colascione's message of "Thu, 7 Jun 2018 20:18:18 -0700") X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 2 Rules triggered EDT_SA_DN_PASS=0, RV6303=0 X-NAI-Spam-Version: 2.3.0.9418 : core <6303> : inlines <6684> : streams <1789058> : uri <2654499> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.20 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:226110 Archived-At: >> Is there any chance we could allow running Elisp code there, i.e. allow > I thought about that, but I worry that allowing arbitrary code to execute > there would make any kind of caching invalidation or something much harder > later. Indeed. >> (:filter FUNCTION FACE-SPECIFICATION) >> or even just >> (:filter FUNCTION) >> where FUNCTION returns the FACE-SPECIFICATION (or nil, say). > If we went this route, I'd probably want to call it :eval. [ Based on the previous point, this might be moot, but it's a problem we have in many places in Elisp, so I find it's important to say it: ] I don't object to the name :eval BUT the argument should be a *function* and not an *expression* (i.e. the implementation should involve `funcall` rather than `eval`). It's no accident that "eval" and "evil" sound so much alike. Stefan