all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Worik Stanton <worik.stanton@gmail.com>
Cc: 8688@debbugs.gnu.org, Glenn Morris <rgm@gnu.org>
Subject: bug#8688: 23.2; search-whitespace-regexp not working as documented
Date: Sat, 04 Dec 2021 21:20:54 +0100	[thread overview]
Message-ID: <87bl1w3yvt.fsf@gnus.org> (raw)
In-Reply-To: <4DD41E32.8070305@gmail.com> (Worik Stanton's message of "Thu, 19 May 2011 07:29:54 +1200")

Worik Stanton <worik.stanton@gmail.com> writes:

> And executed it.  (regex-search works as expected now).
>
> But C-h v search-whitespace-regexp  says it is set to...
>
> search-whitespace-regexp's value is "[     ^M\n]+"
>
> I was about to report that the custom-set-variables command did not work...
>
> Thanks for your help, all the serious problems are solved.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

It seems like the problems in this bug report stem from the various ways
Emacs presents and represents strings, and Emacs has many ways of doing
that.  For instance:

(let ((print-escape-newlines t))
  (prin1 "[ \t\r\n]+" (current-buffer)))
"[ 	^M\n]+"

(let ((print-escape-control-characters t))
  (prin1 "[ \t\r\n]+" (current-buffer)))
"[ \11\15\12]+"

etc.

This is, unfortunately, just the way it is, so I don't think there's
anything actionable in this bug report, and I'm closing it.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-12-04 20:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 23:36 bug#8688: 23.2; search-whitespace-regexp not working as documented Worik Stanton
2011-05-18  7:15 ` Glenn Morris
2011-05-18  8:08   ` Andreas Schwab
2011-05-18 16:20     ` Glenn Morris
2011-05-18 22:14       ` Stefan Monnier
2011-05-18 19:29   ` Unknown
2021-12-04 20:20     ` Lars Ingebrigtsen [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bl1w3yvt.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=8688@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    --cc=worik.stanton@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.