procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

merge from trunk

Browse source
This commit is contained in:
Joakim Verona 2013-09-13 10:41:15 +02:00
commit e4ccda9e00
2 changed files with 11 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
doc/lispref/ChangeLog
View file

@ -1,6 +1,11 @@
2013-09-13 Eli Zaretskii <eliz@gnu.org>
* text.texi (Not Intervals): Minor wording fix.
2013-09-12 Xue Fuqiao <xfq.free@gmail.com>
* functions.texi (Obsolete Functions): Add an index for obsolete functions.
* functions.texi (Obsolete Functions): Add an index for obsolete
functions.
2013-09-11 Xue Fuqiao <xfq.free@gmail.com>

9
doc/lispref/text.texi
View file

@ -3920,10 +3920,11 @@ between one interval and two.
Insertion of text at the border between intervals also raises
questions that have no satisfactory answer.
However, it is easy to arrange for editing to behave consistently for
questions of the form, ``What are the properties of this character?''
So we have decided these are the only questions that make sense; we have
not implemented asking questions about where intervals start or end.
However, it is easy to arrange for editing to behave consistently
for questions of the form, ``What are the properties of text at this
buffer or string position?'' So we have decided these are the only
questions that make sense; we have not implemented asking questions
about where intervals start or end.
In practice, you can usually use the text property search functions in
place of explicit interval boundaries. You can think of them as finding