From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: ndame via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#53507: 27.1; syntax highlight in the eval-expression prompt Date: Tue, 25 Jan 2022 13:17:49 +0000 Message-ID: References: <87fspcx9hz.fsf@gnus.org> Reply-To: ndame Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32304"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 53507@debbugs.gnu.org, "46092@debbugs.gnu.org" <46092@debbugs.gnu.org> To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jan 25 15:46:32 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 ) id 1nCN5c-0008CN-AV for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 25 Jan 2022 15:46:32 +0100 Original-Received: from localhost ([::1]:41570 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nCN5a-0002mG-TN for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 25 Jan 2022 09:46:30 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:42498) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nCLiw-0008DJ-FE for bug-gnu-emacs@gnu.org; Tue, 25 Jan 2022 08:19:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54490) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nCLiw-00051h-4q for bug-gnu-emacs@gnu.org; Tue, 25 Jan 2022 08:19:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nCLiw-0000VL-1z for bug-gnu-emacs@gnu.org; Tue, 25 Jan 2022 08:19:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: ndame Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 25 Jan 2022 13:19:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53507 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 53507-submit@debbugs.gnu.org id=B53507.16431166821829 (code B ref 53507); Tue, 25 Jan 2022 13:19:02 +0000 Original-Received: (at 53507) by debbugs.gnu.org; 25 Jan 2022 13:18:02 +0000 Original-Received: from localhost ([127.0.0.1]:47390 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nCLhx-0000TL-E4 for submit@debbugs.gnu.org; Tue, 25 Jan 2022 08:18:01 -0500 Original-Received: from mail-4319.protonmail.ch ([185.70.43.19]:42589) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nCLhs-0000St-SO for 53507@debbugs.gnu.org; Tue, 25 Jan 2022 08:17:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail2; t=1643116670; bh=bY8xnXTd7sXxyw6eetO8RRhSgJXcXl6YyZaVdKNidcg=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:From:To:Cc; b=f71qyAzFbxx8p+NwoAMQzujqNp3tdFhsVV+8Dy1W7iXcmZsAEpyl3FcAkiy5gSMPi 975L64D/WWS+YKNHDrA60wy42ZC4UMFnlFnaNIDn1DP4q8l2y8Z3YvTgssVyFKQ6dB FlP7fR8s8rOynaVm32kIA8+XpfGo8Eflq418LKI/z5Tl92AXOCq/CHnkPqH4HZUU8s EY2KICsG+UoTMRNgPqxdnMolnR1MXfvNXQ7gxdT6vEb6oTtWPQZA+YvrqGppdz029e wgGQ1sYOF7n50or4ZOEsALSjWPE3MynVgJNAJ3gANbGrD6cQWzOVV+YbpmdDhRhlQ6 nB3wJw/V07ahA== In-Reply-To: <87fspcx9hz.fsf@gnus.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" X-ACL-Warn: , ndame Xref: news.gmane.io gmane.emacs.bugs:225178 Archived-At: > > Yes -- but I don't think this is something we can change at this point. > It's likely to break various things. Naturally, I did not post the final solution. If you check the bug history they you can see that up to know it was not clear why font lock does not work in the eval-expression prompt: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D46092 Stefan gave a hint that it is disabled in font lock mode and this is the case. That's why I posted that proof of concept code which shows that font locking does work there if we remove the disabling code. It should be implemented properly, hopefully in emacs 29, because syntax highlight is useful to get elisp code easier to read, and that's also true for code written into the eval-expression prompt. > > So I don't think there's anything to be done on the Emacs side here, but > perhaps I'm misunderstanding what this report is about? This report is a wish so that it's implemented for core emacs, so font lock works by default in the eval expression prompt too, since font lock is enabled by default in emacs for emacs lisp, so the user rightly expects that it also works for code typed into eval-expression. The problem is as I wrote at the end of my previous mail, if you follow my steps and enable font lock there then you see that font locking elisp code does work, but then you can't quit the prompt with C-g for some reason. This is still a roadblock which should be investigated why this is. In order to highlight elisp in eval-expression I changed the major mode of the minibuffer to emacs-lisp-mode. Is that the reason? If not so then what is? If so then why is changing the mode stops C-g from working there? So there are still roadblocks which have to be overcome to get this feature work in emacs.