From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Marcin Borkowski Newsgroups: gmane.emacs.help Subject: Re: LaTeX mode (tex-mode.el) font-lock bug (?) Date: Tue, 23 Jan 2018 20:05:32 +0100 Message-ID: <878tcoqttv.fsf@mbork.pl> References: <86wp0bxrd3.fsf@zoho.com> <87fu6z5mef.fsf@mbork.pl> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1516734287 29386 195.159.176.226 (23 Jan 2018 19:04:47 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 23 Jan 2018 19:04:47 +0000 (UTC) User-Agent: mu4e 0.9.19; emacs 27.0.50 Cc: help-gnu-emacs@gnu.org To: Stefan Monnier Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jan 23 20:04:43 2018 Return-path: Envelope-to: geh-help-gnu-emacs@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 1ee3ry-0006fa-Cd for geh-help-gnu-emacs@m.gmane.org; Tue, 23 Jan 2018 20:04:30 +0100 Original-Received: from localhost ([::1]:46825 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ee3ty-0007TH-Im for geh-help-gnu-emacs@m.gmane.org; Tue, 23 Jan 2018 14:06:34 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35949) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ee3tH-0007SI-8a for help-gnu-emacs@gnu.org; Tue, 23 Jan 2018 14:05:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ee3tB-0002a0-Oz for help-gnu-emacs@gnu.org; Tue, 23 Jan 2018 14:05:51 -0500 Original-Received: from mail.mojserwer.eu ([195.110.48.8]:48434) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ee3tB-0002X1-IP for help-gnu-emacs@gnu.org; Tue, 23 Jan 2018 14:05:45 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by mail.mojserwer.eu (Postfix) with ESMTP id 91D3AE68C5; Tue, 23 Jan 2018 20:05:40 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mail.mojserwer.eu Original-Received: from mail.mojserwer.eu ([127.0.0.1]) by localhost (mail.mojserwer.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BWGOVJRQ7ta6; Tue, 23 Jan 2018 20:05:38 +0100 (CET) Original-Received: from localhost (static-dwadziewiec-jedenpiec7.echostar.pl [109.232.29.157]) by mail.mojserwer.eu (Postfix) with ESMTPSA id 73419E68C2; Tue, 23 Jan 2018 20:05:37 +0100 (CET) In-reply-to: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.110.48.8 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:115817 Archived-At: On 2018-01-22, at 04:20, Stefan Monnier wrote: >> 2. Why aren't you using AUCTeX? > > Don't know about Emmanuel, but I use tex-mode.el because I much prefer > its C-c C-c and its indentation (no wonder: I wrote them). Fair enough. Still, I prefer AUCTeX (with some functions I wrote to it;-)). >> 4. More precisely, stock Emacs' tex-mode seems to insist that the >> argument to \textbf{...} does not contain newlines. > > Indeed, handling multiline font-lock elements is always a pain in the > rear, so I haven't tried to do it yet, especially since with LaTeX > there's always a risk of mis-parsing (it's nigh on impossible to parse > it reliably without (re)implementing TeX). That's true... IOW, the un-fontlocking of multiline elements is by design. Best, -- Marcin Borkowski