From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: Is this a bug in cperl mode
Date: Sun, 16 Feb 2003 01:28:47 +0000 (UTC) [thread overview]
Message-ID: <b2mpgf$228s$1@agate.berkeley.edu> (raw)
In-Reply-To: m21y2gundb.fsf@sbcglobal.net
[A complimentary Cc of this posting was sent to
Harry Putnam
<hgp@sbcglobal.net>], who wrote in article <m21y2gundb.fsf@sbcglobal.net>:
> Yup. Diffing the cperl-mode from emacs distro which claims to be
> 4.32 agaist the 4.32 found on Ilya's page shows major diff.
Mostly backward-compatibility bruhaha, and whitespace. I found only
one significant bug in 4.32-RMS (one with indentation of
$a = {
};
).
> And the
> one from Ilya's page doesn't have a problem with the posted code just
> like Kai said.
This is due to a different default for cperl-under-as-char. The
proper solution (one which allows customization of
cperl-under-as-char) should be using a separate syntax table during
cperl-find-pods-heres - one with "_" marked as word-character (as it
should be).
Hope this helps,
Ilya
next prev parent reply other threads:[~2003-02-16 1:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 3:20 Is this a bug in cperl mode Harry Putnam
2003-02-10 9:29 ` Kai Großjohann
2003-02-10 10:14 ` Daniel Pfeiffer
2003-02-11 1:23 ` Unknown
2003-02-11 2:04 ` Unknown
2003-02-10 15:50 ` Harry Putnam
2003-02-10 16:11 ` Harry Putnam
2003-02-10 21:07 ` Daniel Pfeiffer
2003-02-16 1:30 ` Ilya Zakharevich
2003-02-16 1:28 ` Ilya Zakharevich [this message]
2003-02-10 21:26 ` Daniel Pfeiffer
2003-02-11 21:21 ` Daniel Pfeiffer
2003-02-16 2:56 ` Ilya Zakharevich
2003-02-17 8:04 ` Daniel Pfeiffer
2003-02-17 19:33 ` Ilya Zakharevich
2003-02-17 7:56 ` CPerl mode v5.0 Ilya Zakharevich
2003-02-17 19:50 ` Ilya Zakharevich
2003-02-20 0:00 ` Daniel Pfeiffer
2003-02-20 20:26 ` Ilya Zakharevich
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='b2mpgf$228s$1@agate.berkeley.edu' \
--to=nospam-abuse@ilyaz.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).