From the ARB_create_context_profile standard:
On failure glXCreateContextAttribsARB returns NULL and generates an
X error with extended error information.
Some NVIDIA drivers on Linux won't return a core profile. When they don't,
they're supposed to return NULL as well as generate an X error, but they
only generate an X error and return a non-NULL, garbage context. This is
not only nonstandard behavior, but lame. It's a major pain to check for X
errors. But whatever, NVIDIA, you big old gorilla.
This may or may not fix segfaults some people are having with Pict3D. If
it does, they won't have to use (current-pict3d-legacy? #t) anymore.
Get data from a clipboard client before going into atomic mode. This
correction can avoid an "about to suspend in atomic mode" failure,
particularly if a snip fails to copy correctly.
This drawing bug was that the DC's state wasn't being
initialized all of the way. In particular, the text-mode
wasn't being set and so, in rare occasions, other drawing
code would (legally) leave it in 'solid mode with a non-white
background color also set. Which would cause those two things
to draw incorrectly.
In particular, restore key handling that makes Ctl-Space produce an
event with a Space character. Also, restore `special-option-key`
support, while correcting the documentation to say what
`special-option-key` and `special-control-key` actually do.
Closes PR 14934
Bindings for UCKeyTranslate.
UCKeyTranslate converts a combination of a key-code, a modifier key state, keyboard layout and dead key state to a unicode string.
output during flushes instead of collecting the entire
contents of the buffer before flushing (at least in the
more common case)
original commit: a12f77f36e5e88d55ebdde0a8ec6e4a6ca708394
Break large inserts into smaller chunks by successively halving the
chunk, instead of successviely peeling off a small part. Also, avoid
traversals and re-traversals of a long line while checking and
breaking up lines.
original commit: ac5961eae9a4d5c24f78e1d8f7d531c7f7881783
by splitting them up and using separate events so other work
can also happen while the insertion is going on.
This change also changes the queue-callback for IO insertion
to be a low-priority callback. This should have been the case
before, I think, but it is a bit surprising it wasn't and so
this may also cause other problems
closes PR 14851
original commit: 8027e4872ad53ec74f43de033bae6e387b57da02
Button-click handling foir `choice%` could continuously
re-queue an event that isn't handled by default, leading
to stack overflow and a crash.
original commit: c7688818fafb478c5ed4afa4c9772c86201386ad
