Mercurial > hg > xemacs-beta
annotate lib-src/config.values.in @ 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 | 772c80e0e180 |
| children |
| rev | line source |
|---|---|
| 428 | 1 ;;; Do not edit this file! |
| 2 ;;; This file was automatically generated, by the config.values.sh script, | |
| 3 ;;; from configure, which was itself automatically generated from configure.in. | |
| 4 ;;; | |
| 556 | 5 ;;; See lisp/config.el for details on how this file is used. |
| 428 | 6 ;;; |
| 7 ;;; You are trapped in a twisty maze of strange-looking files, all autogenerated... | |
| 8 | |
| 9 ;;; configure is created, from configure.in, by autoconf | |
| 10 ;;; config.values.in is created, from configure, by config.values.sh | |
| 11 ;;; config.values is created, from config.values.in, by configure | |
| 556 | 12 ;;; config.values is read by lisp/config.el, |
| 428 | 13 ;;; to create the (Lisp object) config-value-hash-table |
| 14 | |
| 15 ;;; Variables defined in configure by AC_SUBST follow: | |
| 16 ;;; (These are used in Makefiles) | |
| 17 | |
| 18 | |
| 19 ;;; Variables defined in configure by AC_DEFINE and AC_DEFINE_UNQUOTED follow: | |
| 20 ;;; (These are used in C code) | |
| 21 |