From: Unknown <unknown@unknown.invalid>
Subject: Re: Is this a bug in cperl mode
Date: Tue, 11 Feb 2003 02:04:24 GMT [thread overview]
Message-ID: <ISY1a.634216$F2h1.257600@news01.bloor.is.net.cable.rogers.com> (raw)
In-Reply-To: XfY1a.634119$F2h1.47277@news01.bloor.is.net.cable.rogers.com
Le Wang wrote:
> Daniel Pfeiffer wrote:
>
>> kai.grossjohann@uni-duisburg.de (Kai Großjohann) skribis:
>>> Harry Putnam <hgp@sbcglobal.net> writes:
>>
>>> > I get several kinds of goofy behavior from cperl mode on this snippet
>>> > of code. The syntax hylight breaks down on last section too. Makes
>>> > cperl pretty useless for what its designed for. Maybe its local guff
>>> > causing it but starting emacs -q -no-site-file doesn't seem to help.
>>
>>> I could reproduce this with the cperl that comes with Emacs, but the
>>> cperl from Ilya (I have 4.32, it seems) works.
>>
>>> How about you check that and submit a bug report, suggesting to
>>> upgrade the cperl in Emacs. (It seems that the cperl in Emacs is
>>> quite old.)
>>
>> Actually I've been exploring this recently, and the opposite is the case.
>> The CPerl from Ilya is quite old. The emacs variant has had quite a few
>> little bug-fixes over the last three years. This seems the first case
>> where Ilya's is better.
>
> Here is another:
>
> Using filladapt-mode, I'm able to fill end-of-line comments with the Ilya's
> version. This is broken in the Emacs version, both CVS and stable.
>
> I just checked, and adaptive-fill-mode is broken in the same manner.
>
> I can turn filladapt off in the mode hook, but still regression is never
> good.
Oops, things just got a little worse. In the cvs version of emacs, no matter
what version of cperl-mode (emacs' or Ilya's) I use, even if I turn filladapt
off in the mode hook, filling is broken as described above. With the
addition that even whole line comments won't fill at all. I'm trying to fill
by pressing <M-q>, which runs cperl-fill-paragraph.
Bummer.
--
Le
next prev parent reply other threads:[~2003-02-11 2:04 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 [this message]
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
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='ISY1a.634216$F2h1.257600@news01.bloor.is.net.cable.rogers.com' \
--to=unknown@unknown.invalid \
/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).