unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: LaTeX mode (tex-mode.el) font-lock bug (?)
Date: Tue, 23 Jan 2018 20:05:32 +0100	[thread overview]
Message-ID: <878tcoqttv.fsf@mbork.pl> (raw)
In-Reply-To: <jwvvafu7fbl.fsf-monnier+gmane.emacs.help@gnu.org>


On 2018-01-22, at 04:20, Stefan Monnier <monnier@iro.umontreal.ca> 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



  reply	other threads:[~2018-01-23 19:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-21 13:40 LaTeX mode (tex-mode.el) font-lock bug (?) Emanuel Berg
2018-01-21 14:14 ` Marcin Borkowski
2018-01-22  3:20   ` Stefan Monnier
2018-01-23 19:05     ` Marcin Borkowski [this message]
     [not found]     ` <mailman.7847.1516734352.27995.help-gnu-emacs@gnu.org>
2018-01-23 19:18       ` Emanuel Berg
     [not found]   ` <mailman.7740.1516591280.27995.help-gnu-emacs@gnu.org>
2018-01-22 12:52     ` Emanuel Berg
     [not found] ` <mailman.7709.1516544111.27995.help-gnu-emacs@gnu.org>
     [not found]   ` <86shazxlys.fsf@zoho.com>
2018-01-21 15:38     ` Emanuel Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878tcoqttv.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).