From: Colin Williams <lackita@gmail.com>
To: Elena <egarrulo@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: perl-mode vs cperl-mode
Date: Fri, 7 Aug 2009 10:55:01 -0400 [thread overview]
Message-ID: <1b97198a0908070755y788c1d89u843f7e6243614718@mail.gmail.com> (raw)
In-Reply-To: <5b571924-1d5c-4907-b89d-46a5d4087a0d@p28g2000vbn.googlegroups.com>
I guess I understand that it generally handles quirky syntax "better,"
I'm looking more for examples/features that cperl-mode has that
perl-mode fails at. So far we've got regexp and string quoting, are
there any other "useful" features?
On Fri, Aug 7, 2009 at 10:33 AM, Elena<egarrulo@gmail.com> wrote:
> On 7 Ago, 13:45, Colin Williams <lack...@gmail.com> wrote:
>> I'm trying to decide how to set up my perl development environment,
>> and I've come to a bit of a conundrum. I realize that there is both a
>> `perl-mode' and a `cperl-mode' lying around in the emacs code base,
>> but it's unclear to me which one is better. Many people have said
>> (rather authoritatively, I might add) that `cperl-mode' is much
>> better, but none of these people bother to list the ways in which it's
>> better. I was hoping somebody could categorically list the features
>> `cperl-mode' has that make it better than `perl-mode'.
>>
>> Colin
>
> Last time I used it, cperl-mode dealt with Perl's quirky syntax better
> than perl-mode. You can check it on your own. Pay attention to both
> regex and strings quoting.
>
next prev parent reply other threads:[~2009-08-07 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4124.1249654635.2239.help-gnu-emacs@gnu.org>
2009-08-07 14:33 ` perl-mode vs cperl-mode Elena
2009-08-07 14:55 ` Colin Williams [this message]
[not found] ` <mailman.4127.1249656910.2239.help-gnu-emacs@gnu.org>
2009-08-07 15:04 ` Michael Ekstrand
2009-08-07 16:36 ` Ilya Zakharevich
2009-08-07 17:33 ` A.Politz
2009-08-07 17:56 ` Lennart Borgman
2009-08-07 22:33 ` Xah Lee
2009-08-08 4:11 ` Ilya Zakharevich
2009-08-07 13:45 Colin Williams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1b97198a0908070755y788c1d89u843f7e6243614718@mail.gmail.com \
--to=lackita@gmail.com \
--cc=egarrulo@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.