unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: 14343@debbugs.gnu.org, jon@jrock.us
Subject: bug#14343: 24.3; cperl font-lock (highlighting) bug after copy-paste
Date: Mon, 06 May 2013 14:19:13 -0400	[thread overview]
Message-ID: <jwvppx4f4yc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87txmk5b2z.fsf@xvii.vinc17.org> (Vincent Lefevre's message of "Fri, 03 May 2013 17:37:08 +0200")

> It seems that Emacs lost my bug report. :( Let's try again...
> Under X Window (so that Emacs has its own interface), open a file
> cperl-font-lock-string starting with:

> #!/usr/bin/env perl
> # -*- mode: cperl -*-

> print <<EOF;
> foo
> bar
> EOF
[...]
> Triple-click on the "foo" line and click with the middle mouse button
> to paste. All the lines starting with the second "foo" get colored in
> red.

A "simpler" recipe (which involves less code) is to go just before "bar"
and do M-: (insert "a") RET

> This happens with the Debian package emacs24 24.3+1-1 and this is
> a regression in GNU Emacs 24. No problems with Emacs 23.

The "simpler" recipe fails in Emacs-23 as well (i.e. the change is due
to the way select+paste changed, rather than to a change in cperl).
It also fails with the "non-Emacs" cperl-mode-5.23 I got from
https://raw.github.com/jrockway/cperl-mode/master/cperl-mode.el, so it
looks like it's not due to our messing things up.


        Stefan





  reply	other threads:[~2013-05-06 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 15:37 bug#14343: 24.3; cperl font-lock (highlighting) bug after copy-paste Vincent Lefevre
2013-05-06 18:19 ` Stefan Monnier [this message]
2021-05-31  6:03 ` Lars Ingebrigtsen

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=jwvppx4f4yc.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=14343@debbugs.gnu.org \
    --cc=jon@jrock.us \
    --cc=vincent@vinc17.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).