Minor doc fix for string predicates.
doc/lispref/strings.texi (Text Comparison): Mention equal-including-properties for when text properties of the strings matter for comparison.
This commit is contained in:
parent
bc0650fdb6
commit
402a211fd3
2 changed files with 10 additions and 2 deletions
|
@ -1,3 +1,9 @@
|
|||
2014-04-24 Eli Zaretskii <eliz@gnu.org>
|
||||
|
||||
* strings.texi (Text Comparison): Mention
|
||||
equal-including-properties for when text properties of the strings
|
||||
matter for comparison.
|
||||
|
||||
2014-04-21 Eli Zaretskii <eliz@gnu.org>
|
||||
|
||||
* text.texi (Registers): Document register-read-with-preview.
|
||||
|
|
|
@ -423,8 +423,10 @@ the symbol names are used. Case is always significant, regardless of
|
|||
|
||||
This function is equivalent to @code{equal} for comparing two strings
|
||||
(@pxref{Equality Predicates}). In particular, the text properties of
|
||||
the two strings are ignored. But if either argument is not a string
|
||||
or symbol, an error is signaled.
|
||||
the two strings are ignored; use @code{equal-including-properties} if
|
||||
you need to distinguish between strings that differ only in their text
|
||||
properties. However, unlike @code{equal}, if either argument is not a
|
||||
string or symbol, @code{string=} signals an error.
|
||||
|
||||
@example
|
||||
(string= "abc" "abc")
|
||||
|
|
Loading…
Add table
Reference in a new issue