unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
To: help-gnu-emacs@gnu.org
Subject: Re: cperl-mode and fontlock
Date: Fri, 9 Oct 2009 09:04:25 +0000 (UTC)	[thread overview]
Message-ID: <slrnhctv4p.d2b.nospam-abuse@chorin.math.berkeley.edu> (raw)
In-Reply-To: 873a67glr1.fsf@lifelogs.com

On 2009-09-28, Ted Zlatanov <tzz@lifelogs.com> wrote:
> Ilya, it looks like Chong Yidong has synchronized 6.2 into the Emacs
> trunk.

How much does it differ from what was done a decade ago?  That time
a brave guy volunteered and converted cperl-mode to new conventions.
Only years of user experiences had shown that this introduced so many
bugs that the mode is IMO unusable.

  (Usability is the question of trust.  THE purpose of a mode is to
   use faces/paren-match/indentation to make driver errors as much
   visible as possible.  I know that "my" version has so few false
   positives that EVERY irregularity of
   highlight/paren-match/indentation deserves to be investigated.
   AFAIK, the situation is opposite with the shipped version; the "cry
   wolves" effect...)

> Can you follow up on emacs-devel and clear up any remaining issues?

Could not find it on gmane.emacs.devel...

> I'd like to make sure the Emacs version of cperl-mode doesn't
> get out of sync again, and it's good that Chong (one of the two current
> Emacs maintainers) feels strongly enough to synchronize against your
> version.

The only practically viable solution I can see is to aim for identical
byte-code between "my" version and Emacs's one...  (At least with some
"define"; the default compile may aim for distinct bytecode, but all
the corresponding places in the .el file should be easily identifyable...)

Thanks,
Ilya


  reply	other threads:[~2009-10-09  9:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.6904.1253227091.2239.help-gnu-emacs@gnu.org>
2009-09-25 10:08 ` cperl-mode and fontlock Ilya Zakharevich
2009-09-25 22:29   ` Harry Putnam
2009-09-26  1:46   ` Harry Putnam
2009-09-26  2:30   ` Harry Putnam
     [not found]   ` <mailman.7552.1253917816.2239.help-gnu-emacs@gnu.org>
2009-09-28 14:57     ` Ted Zlatanov
2009-10-09  9:04       ` Ilya Zakharevich [this message]
2009-10-09 14:50         ` Ted Zlatanov
2009-10-09 21:48           ` Ilya Zakharevich
2009-10-14 15:55             ` Ted Zlatanov
2009-10-09  8:29     ` Ilya Zakharevich
2009-10-09 13:41       ` Harry Putnam
     [not found]   ` <mailman.7555.1253929616.2239.help-gnu-emacs@gnu.org>
2009-09-29  9:48     ` Ilya Zakharevich
2009-09-29 16:03       ` Harry Putnam
2009-09-30  6:25         ` Kevin Rodgers
2009-09-30  6:28           ` Harry Putnam
2009-09-17 22:37 Harry Putnam

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=slrnhctv4p.d2b.nospam-abuse@chorin.math.berkeley.edu \
    --to=nospam-abuse@ilyaz.org \
    --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).