GNU bug report logs - #75113
29.4; Lispref Manual: backslash before newline

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ulrich Müller <ulm <at> gentoo.org>
Subject: bug#75113: closed (Re: bug#75113: 29.4; Lispref Manual: backslash
 before newline)
Date: Sat, 28 Dec 2024 12:07:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#75113: 29.4; Lispref Manual: backslash before newline

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 75113 <at> debbugs.gnu.org.

-- 
75113: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=75113
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ulrich Müller <ulm <at> gentoo.org>
Cc: 75113-done <at> debbugs.gnu.org
Subject: Re: bug#75113: 29.4; Lispref Manual: backslash before newline
Date: Sat, 28 Dec 2024 14:05:59 +0200

> From: Ulrich Müller <ulm <at> gentoo.org>
> Date: Thu, 26 Dec 2024 11:03:41 +0100
> 
> Subsection "Basic Char Syntax" in objects.texi says:
> "You can also add a backslash before whitespace characters such as
> space, tab, newline and formfeed."
> 
> AFAICS this information isn't accurate for newline. ?\<newline> is
> invalid escape character syntax, and \<newline> inside a string is not a
> literal newline either but a line continuation.

Thanks, I've now removed the inaccurate parts from that section (on
the emacs-30 branch), and I'm therefore closing this bug.

[Message part 3 (message/rfc822, inline)]

From: Ulrich Müller <ulm <at> gentoo.org>
To: bug-gnu-emacs <at> gnu.org
Subject: 29.4; Lispref Manual: backslash before newline
Date: Thu, 26 Dec 2024 11:03:41 +0100

Subsection "Basic Char Syntax" in objects.texi says:
"You can also add a backslash before whitespace characters such as
space, tab, newline and formfeed."

AFAICS this information isn't accurate for newline. ?\<newline> is
invalid escape character syntax, and \<newline> inside a string is not a
literal newline either but a line continuation.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.