Mercurial > hg > xemacs-beta
annotate man/lispref/index.texi @ 5879:77d7b77909c2
Move extents.c to working in byte positions only; fix a bug, extent_detach()
src/ChangeLog addition:
2015-03-27 Aidan Kehoe <kehoea@parhasard.net>
Fix a small bug, extent_detach(); minimise needless char-byte
conversion, extents.c, sticking to byte positions in general in
this file.
* extents.c:
* extents.c (signal_single_extent_changed):
Pass byte endpoints to
gutter_extent_signal_changed_region_maybe(),
buffer_extent_signal_changed_region().
* extents.c (extent_detach):
Call signal_extent_changed() correctly, pass both extent endpoints
rather than just the byte and character variants of the start.
* extents.c (struct report_extent_modification_closure):
Do this in terms of byte positions.
* extents.c (report_extent_modification_mapper):
Use byte positions, only converting to characters when we are
definitely calling Lisp.
* extents.c (report_extent_modification):
Use byte positions in this API, move the byte-char conversion to
our callers, simplifying extents.c (it all now works in byte
positions).
* extents.h:
Update report_extent_modification's prototype.
* gutter.c (gutter_extent_signal_changed_region_maybe):
Use byte positions here, avoids needless byte-char conversion.
* gutter.h:
Update the prototype here.
* insdel.c:
* insdel.c (buffer_extent_signal_changed_region):
Implement this in terms of byte positions.
* insdel.c (signal_before_change):
* insdel.c (signal_after_change):
Call report_extent_modification() with byte positions, doing the
char->byte conversion here rather than leaving it to extents.c.
* insdel.h:
* insdel.h (struct each_buffer_change_data):
The extent unchanged info now describes bytecounts.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Fri, 27 Mar 2015 23:39:49 +0000 |
| parents | 576fb035e263 |
| children |
| rev | line source |
|---|---|
| 398 | 1 @c -*-texinfo-*- |
| 2 @setfilename ../../info/index.info | |
| 3 | |
| 4 @c Indexing guidelines | |
| 5 | |
| 6 @c I assume that all indexes will be combined. | |
| 7 @c Therefore, if a generated findex and permutations | |
| 8 @c cover the ways an index user would look up the entry, | |
| 9 @c then no cindex is added. | |
| 10 @c Concept index (cindex) entries will also be permuted. Therefore, they | |
| 11 @c have no commas and few irrelevant connectives in them. | |
| 12 | |
| 13 @c I tried to include words in a cindex that give the context of the entry, | |
| 14 @c particularly if there is more than one entry for the same concept. | |
| 15 @c For example, "nil in keymap" | |
| 16 @c Similarly for explicit findex and vindex entries, e.g. "print example". | |
| 17 | |
| 18 @c Error codes are given cindex entries, e.g. "end-of-file error". | |
| 19 | |
| 20 @c pindex is used for .el files and Unix programs | |
| 21 | |
| 22 @node Index, , Standard Hooks, Top | |
| 23 @unnumbered Index | |
| 24 | |
| 25 @ignore | |
| 26 All variables, functions, keys, programs, files, and concepts are | |
| 444 | 27 in this one index. |
| 398 | 28 |
| 29 All names and concepts are permuted, so they appear several times, one | |
| 30 for each permutation of the parts of the name. For example, | |
| 31 @code{function-name} would appear as @b{function-name} and @b{name, | |
| 32 function-}. Key entries are not permuted, however. | |
| 33 @end ignore | |
| 34 | |
| 35 @c Print the indices | |
| 36 | |
| 37 @printindex fn |