unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Mark Tilford <ralphmerridew@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Perl mode and y=>
Date: Tue, 27 Sep 2011 12:51:08 -0500	[thread overview]
Message-ID: <CAKnavseXcTBOqBMxOOqKoV0yH74v+Ru96tOryMiythhmwGj3Rw@mail.gmail.com> (raw)

For some reason, Perl mode behaves oddly whenever it hits the syntax
"y => " (it thinks stuff after that is still quoted), which is used
frequently in Imager (
http://search.cpan.org/~tonyc/Imager-0.85/lib/Imager/Draw.pod#getscanline()
)
I have to replace that with "'y' =>" or "'y', ".  "x =>" or "z =>"
does not cause this problem.

1)  Any idea why?
2)  Could somebody fix this?



             reply	other threads:[~2011-09-27 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 17:51 Mark Tilford [this message]
2011-09-27 19:26 ` Perl mode and y=> S Boucher

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=CAKnavseXcTBOqBMxOOqKoV0yH74v+Ru96tOryMiythhmwGj3Rw@mail.gmail.com \
    --to=ralphmerridew@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.
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).