GNU bug report logs - #33175
26.1; match-string

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 33175 in the body.
You can then email your comments to 33175 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: 濱田和明 <hmd24kaz <at> gmail.com>
To: "bug-gnu-emacs <at> gnu.org" <bug-gnu-emacs <at> gnu.org>
Subject: 26.1; match-string
Date: Sat, 27 Oct 2018 19:59:16 +0900

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

(progn
   (string-match "\\(key[ \t]*\\)= \\(.*\\)" (buffer-string))
   (match-string 0))

Key = 100
->#("
Key = 10" 0 1 (fontified t) 1 9 (fontified t))

Is not “key = 100”?

[Message part 2 (text/html, inline)]

Message #8 received at 33175 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: 濱田和明 <hmd24kaz <at> gmail.com>
Cc: 33175 <at> debbugs.gnu.org
Subject: Re: bug#33175: 26.1; match-string
Date: Sat, 27 Oct 2018 07:10:16 -0400

tags 33175 notabug
close 33175
quit

濱田和明 <hmd24kaz <at> gmail.com> writes:

> (progn
>    (string-match "\\(key[ \t]*\\)= \\(.*\\)" (buffer-string))
>    (match-string 0))
>
> Key = 100
> ->#("
> Key = 10" 0 1 (fontified t) 1 9 (fontified t))
>
> Is not “key = 100”?

    (match-string NUM &optional STRING)

    [...]
    STRING should be given if the last search was by ‘string-match’ on STRING.

Try this instead:

    (let ((str (buffer-string)))
       (string-match "\\(key[ \t]*\\)= \\(.*\\)" str)
       (match-string 0 str))

Previous Next

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