between two unlike intervals via merge_properties_sticky.
(merge_properties_sticky): New function.
(graft_intervals_into_buffer): Leave handling of `sticky'-ness to
adjust_intervals_for_insertion, then merge properties of the
inserted text onto the old ones.
(textget_direct): New function.
(set_point): Fix calculating of fromprev.
(verify_interval_modification): Check for `read-only' property
and take its `sticky'-ness into account.
(set_point): Ignore `invisible' property unless property value is `hidden'.
use only what Man-reference-regexp matched.
(Man-reference-regexp): Don't match starting with a period.
(Man-first-heading-regexp): Allow leading space.
(Man-heading-regexp): Allow leading space.
(property_change_reply_identifier): Renamed from ...-tick.
(struct prop_location): Field `identifier' renamed from `tick'.
Various functions changed accordingly.
(x_handle_selection_request): Delete local struct var `reply'.
(wait_for_property_change_unwind): New function.
(wait_for_property_change): Add unwind protect.
(wait_for_property_change): Eventually time out with error.
(x_reply_selection_request): XFlushQueue and UNBLOCK_INPUT
before calling wait_for_property_change.
(x_get_window_property): Simplify input blocking/unblocking.
Don't delete the property here.
(receive_incremental_selection): Delete property here.
Call XSelectInput to enable and disable PropertyChangeMask.
(x_get_window_property_as_lisp_data): And here.
(BSTRING): #define this iff HAVE_BCOPY is #defined here. Ignore what
the system-description files say. They don't always make fine
enough distinctions between systems, and sometimes the bcopy
routines are available only with X windows.
LD_SWITCH_X_SITE and assume --with-x11.
Only look for X11 files if we weren't told about a window system
or if we were told to use X11 but not told where.
Search the libraries from the s and/or m files when checking for
functions.
* configure.in: Remove any trailing slashes in prefix and exec_prefix.
the filter's execution.
* gud.el (gud-gdb-marker-filter): If we received some text after
the position marker, append it to any text before the marker,
instead of throwing away the text before the marker.
markers from GDB will always be received in one chunk of input;
gud-gdb-marker-filter may be called several times, each time
providing a little more of the position marker.
(gud-gdb-marker-acc): New variable.
(gud-gdb-marker-filter): If we have received what could be the
beginning of a position marker, hold that text in
gud-gdb-marker-acc for the next time we get called, until we have
enough information to decide for sure.
* gud.el (gud-gdb-marker-filter): Only recognize GDB position
markers if they occur at the beginning of the line. They always
do, and this reduces the likelihood that the above change will
hold back output that isn't really a position marker.
