--- Begin Message ---
Subject: |
23.1; can't escape quotes preceded by certain characters in perl-mode |
Date: |
Mon, 01 Aug 2011 09:58:10 -0500 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 |
When I try to escape quotes with a backslash, within quotes, the
coloring in perl-mode breaks in a very specific way. It depends
entirely on the characters that precede the backslash. For example,
this works fine:
$a = " x \"string\"";
but if you replace the 'x' with m, q, s, or y, then Emacs thinks you're
still inside a quote.
You can find a screenshot here:
http://i.imgur.com/mG6ey.jpg
I've tried this in emacs 23.1, 23.2, and 22.2 on Windows and Linux and
the problem is the same in all of these versions.
Thanks
--Gabe
If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
`bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
c:/Program Files (x86)/emacs-23.1/etc/DEBUG for instructions.
In GNU Emacs 23.1.1 (i386-mingw-nt6.1.7601)
of 2009-07-29 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 6.1.7601
configured using `configure --with-gcc (4.4)'
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: ENU
value of $XMODIFIERS: nil
locale-coding-system: cp1252
default-enable-multibyte-characters: t
Major mode: Fundamental
Minor modes in effect:
tooltip-mode: t
tool-bar-mode: t
mouse-wheel-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
blink-cursor-mode: t
global-auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
line-number-mode: t
transient-mark-mode: t
Recent input:
# ! <backspace> <backspace> C-p C-p C-p C-p C-k C-k
C-k C-k C-k # ! / u s r / b i n / p e r l <return>
<return> M-x p e r l SPC m o d e <return> $ t e s t
SPC = SPC " SPC y SPC \ " h e l l o \ " " ; <return>
<return> $ <backspace> E <backspace> $ t e s t SPC
= SPC " " ; C-p C-p <backspace> m <backspace> a <backspace>
b <backspace> c <backspace> y <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <menu-bar> <help-menu>
<about-emacs> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> M-x
r e p o r t SPC e <tab> <return>
Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a. [2 times]
-----------------------------------
Gabriel M. Simon, Ph.D.
Post-Doctoral Research Fellow
Laboratory of Dr. Jeffrey I. Gordon
Washington University in St. Louis
lab: 314-362-3963
cell: 858-964-8666
emacs_escape_quote_bug.jpg
Description: JPEG image
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#9217: 23.1; can't escape quotes preceded by certain characters in perl-mode |
Date: |
Sat, 6 Jul 2019 05:23:35 +0200 |
Gabriel Simon <address@hidden> writes:
> When I try to escape quotes with a backslash, within quotes, the coloring in
> perl-mode breaks in a very specific way. It depends entirely on the
> characters
> that precede the backslash. For example, this works fine:
>
> $a = " x \"string\"";
>
> but if you replace the 'x' with m, q, s, or y, then Emacs thinks you're still
> inside a quote.
>
> You can find a screenshot here:
>
> http://i.imgur.com/mG6ey.jpg
>
> I've tried this in emacs 23.1, 23.2, and 22.2 on Windows and Linux and the
> problem is the same in all of these versions.
>
> Thanks
>
> --Gabe
Hi,
I can't reproduce this on Emacs 26.2, the latest version of Emacs.
(I failed to reproduce it on Emacs 25.1 as well.)
Since the bug was reported 8 years ago, I will assume that this bug has
been fixed in the meantime. I am therefore closing this bug.
If you can still reproduce this issue on the latest version of Emacs,
please report back and we can re-open the issue.
Thanks,
Stefan Kangas
--- End Message ---