[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (error "Stack overflow in regexp matcher") and (?)wrong display of r

From: Noam Postavsky
Subject: Re: (error "Stack overflow in regexp matcher") and (?)wrong display of regexp in backtrace
Date: Sun, 15 Mar 2020 10:21:51 -0400

On Sun, 15 Mar 2020 at 06:40, Alan Mackenzie <address@hidden> wrote:

> First of all, note the regexp, "\\(\\\\\\(.\\|\n\\)\\|[^\\\n\15]\\)*"
>                                                             ^^^
> In the source, the "\15" is "\r".  Why is this substitution being made
> for the backtrace?  Is it intentional (in which case, why not do the
> same to the "\n"?), or is it a bug?  To me, it is more like a bug.

It's not really a bug (perhaps a missing feature), it's due to
print-escape-control-characters being non-nil. Newline is printed as
"\n" because print-escape-newlines is non-nil, but there is no
equivalent print-escape-carriage-returns.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]