GNU bug report logs - #8688
23.2; search-whitespace-regexp not working as documented

Previous Next

Package: emacs;

Reported by: Worik Stanton <worik.stanton <at> gmail.com>

Date: Tue, 17 May 2011 23:37:02 UTC

Severity: normal

Found in version 23.2

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


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

From: Glenn Morris <rgm <at> gnu.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: 8688 <at> debbugs.gnu.org, Worik Stanton <worik.stanton <at> gmail.com>
Subject: Re: bug#8688: 23.2; search-whitespace-regexp not working as documented
Date: Wed, 18 May 2011 12:20:45 -0400
Andreas Schwab wrote:

> Glenn Morris <rgm <at> gnu.org> writes:
>
>> I think you're being confused by the way customize treats regexps (it
>> confuses me as well; I'm not sure it is helpful).
>
> They are just literal strings, without lisp-level quoting.

I know, but I find it confusing, and it seems others do too (eg this;
also bug#2666). It makes it difficult to write doc-strings for 'regexp
defcustoms, as we see in both of these cases.

>> Oh, it's not possible to type a TAB, or ctrl-M, or newline, in a custom
>> field
>
> C-q works fine.

Yes, but that's not what the doc says people should type, and IMO
"ctrl-q ctrl-j" is a lot more confusing than "\n", especially in an
interface that is supposed to make life easier.





This bug report was last modified 3 years and 171 days ago.

Previous Next


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