unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: LanX <lanx.perl@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: fontification problem with PODs
Date: Tue, 4 May 2010 07:55:52 -0700 (PDT)	[thread overview]
Message-ID: <d50e4346-eb24-430b-a6ae-4f4df59ee874@q32g2000yqb.googlegroups.com> (raw)
In-Reply-To: hrothc$9u8$1@colin2.muc.de


> Which is a way of saying that the initialisation for cperl-mode isn't
> watertight.  ;-)

no it's a way to say that emacs is not watertight.

There is no automatic testing system and every little incompatible
changes can easily break a complex mode like cperl.

I recently had a long discussion until the dev team admitted that they
screwed font locking in compilation buffer because they started
appending newlines to all regexes ...


  reply	other threads:[~2010-05-04 14:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21 13:36 [cperl-mode] fontification problem with PODs LanX
2009-10-24  6:12 ` Ilya Zakharevich
2009-10-31  4:15   ` Will Willis
2009-12-07  0:12 ` Joseph Brenner
2009-12-09 12:49   ` LanX
2010-05-02  4:32     ` Ilya Zakharevich
2010-05-02 14:07       ` Alan Mackenzie
2010-05-04  3:33         ` Ilya Zakharevich
2010-05-04 10:39           ` Alan Mackenzie
2010-05-04 14:55             ` LanX [this message]
2010-05-06 20:08             ` Ilya Zakharevich
2010-05-07  1:31               ` Juanma Barranquero
     [not found]               ` <mailman.29.1273195927.9285.help-gnu-emacs@gnu.org>
2010-05-07  2:55                 ` Stefan Monnier
2010-05-08 21:50                   ` Juanma Barranquero

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=d50e4346-eb24-430b-a6ae-4f4df59ee874@q32g2000yqb.googlegroups.com \
    --to=lanx.perl@googlemail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).