Minor fix of a recently installed documentation change
* doc/emacs/search.texi (Lax Search): Don't use ".." inside @samp, it looks confusing, especially in print. (Bug#51020)
This commit is contained in:
parent
4d76765b6c
commit
1b383ac424
2 changed files with 3 additions and 3 deletions
|
@ -1331,8 +1331,8 @@ matches @w{@samp{foo bar}}, @w{@samp{foo@ @ bar}},
|
||||||
precisely, Emacs matches each sequence of space characters in the
|
precisely, Emacs matches each sequence of space characters in the
|
||||||
search string to a regular expression specified by the variable
|
search string to a regular expression specified by the variable
|
||||||
@code{search-whitespace-regexp}. For example, to make spaces match
|
@code{search-whitespace-regexp}. For example, to make spaces match
|
||||||
sequences of newlines as well as spaces, set it to
|
sequences of newlines as well as spaces, set it to the regular expression
|
||||||
@samp{"[[:space:]\n]+"}. The default value of this variable considers
|
@samp{[[:space:]\n]+}. The default value of this variable considers
|
||||||
any sequence of spaces and tab characters as whitespace.
|
any sequence of spaces and tab characters as whitespace.
|
||||||
|
|
||||||
If you want whitespace characters to match exactly, you can turn lax
|
If you want whitespace characters to match exactly, you can turn lax
|
||||||
|
|
2
etc/NEWS
2
etc/NEWS
|
@ -1168,7 +1168,7 @@ search string is at least this long. 'lazy-highlight-initial-delay'
|
||||||
still applies for shorter search strings, which avoids flicker in the
|
still applies for shorter search strings, which avoids flicker in the
|
||||||
search buffer due to too many matches being highlighted.
|
search buffer due to too many matches being highlighted.
|
||||||
|
|
||||||
---
|
+++
|
||||||
*** The default 'search-whitespace-regexp' value has changed.
|
*** The default 'search-whitespace-regexp' value has changed.
|
||||||
This used to be "\\s-+", which meant that it was mode-dependent whether
|
This used to be "\\s-+", which meant that it was mode-dependent whether
|
||||||
newlines were included in the whitespace set. This has now been
|
newlines were included in the whitespace set. This has now been
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue