From: "Ryan Moszynski" <ryan.m.lists@gmail.com>
Subject: perl mode problems
Date: Wed, 19 Jul 2006 21:21:17 -0400 [thread overview]
Message-ID: <fbf7c10b0607191821s3ea4f254q8b56a8ce50289aef@mail.gmail.com> (raw)
emacs 21.4.1 debian/ubuntu dapper
does anyone else have constant problems with perl-mode?
i have problems with reserved words not being recognized, parenthese
and and braces matching is terrible, and sometimes, inexplicably, I
have to put an extra ' or " after a comment so that emacs doesn't
thighlight the rest of my program as a comment.
In every other way emacs works wonderfully for me. I've never had
these problems in c-mode or java-mode. Should I try cvs emacs, or is
there a way to upgrade just the perl mode and paren, curly braces
matching?
thanks,
ryan
next reply other threads:[~2006-07-20 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 1:21 Ryan Moszynski [this message]
2006-07-20 8:42 ` perl mode problems Peter Dyballa
[not found] <mailman.4272.1153642838.9609.help-gnu-emacs@gnu.org>
2006-07-24 8:15 ` Tim X
2006-07-24 14:53 ` Eric Pement
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=fbf7c10b0607191821s3ea4f254q8b56a8ce50289aef@mail.gmail.com \
--to=ryan.m.lists@gmail.com \
/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).