From: Paul Eggert <eggert@cs.ucla.edu>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 33940-done@debbugs.gnu.org
Subject: bug#33940: 27.0.50; ?\^c syntax confuses scanning
Date: Tue, 1 Jan 2019 11:42:43 -0800 [thread overview]
Message-ID: <d42ad125-3d76-1f99-e339-eee1015808ef@cs.ucla.edu> (raw)
In-Reply-To: <8736qdhv80.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 276 bytes --]
Michael Heerdegen wrote:
> Yes, with exactly that recipe, but with emacs built from the master
> branch, please. Oh, and happy new year, if you not are still in the old
> one.
The same for you! Thanks for pointing me in the right direction; I installed the
attached patch.
[-- Attachment #2: 0001-Fix-woman.el-to-not-confuse-scan-sexps.patch --]
[-- Type: text/x-patch, Size: 895 bytes --]
From 504457673dabfa89cb2eac89f093f10736c52ca7 Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Tue, 1 Jan 2019 11:35:17 -0800
Subject: [PATCH] Fix woman.el to not confuse scan-sexps
* lisp/woman.el (woman-unpadded-space-char):
Escape the close-bracket (Bug#33940).
---
lisp/woman.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/woman.el b/lisp/woman.el
index 13aea5d91c..9548fdc6b3 100644
--- a/lisp/woman.el
+++ b/lisp/woman.el
@@ -2078,7 +2078,7 @@ woman-escaped-escape-string
(char-to-string woman-escaped-escape-char)
"Internal string representation of escaped escape characters.")
-(defconst woman-unpadded-space-char ?\^]
+(defconst woman-unpadded-space-char ?\^\]
;; An arbitrary unused control character
"Internal character representation of unpadded space characters.")
(defconst woman-unpadded-space-string
--
2.17.1
next prev parent reply other threads:[~2019-01-01 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 2:58 bug#33940: 27.0.50; ?\^c syntax confuses scanning Michael Heerdegen
2019-01-01 3:58 ` Paul Eggert
2019-01-01 4:12 ` Michael Heerdegen
2019-01-01 19:42 ` Paul Eggert [this message]
2019-01-02 0:28 ` Michael Heerdegen
2019-01-02 0:48 ` Paul Eggert
2019-01-02 9:49 ` Andreas Schwab
2019-01-02 11:31 ` Michael Heerdegen
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=d42ad125-3d76-1f99-e339-eee1015808ef@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=33940-done@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).