This is intended to be used by screen lockers, where the server must
exit if the screen locker does, to avoid a security hole. As suggested
by Alan Coopersmith, this is implemented using a new flag for the
disconnect mode of the XFixes extension. Includes wording suggestions
from Peter Hutterer.
Signed-off-by: Demi Marie Obenour <demiobenour@gmail.com>
Adding index() and rindex() as macros wreaks havoc with several libc++
headers, which liberally use the name 'index' for variables, functions,
and more. Get the declarations from <strings.h> instead, where they have
been for at least two decades.
Signed-off-by: Dimitry Andric <dimitry@andric.com>
The new names (`dead_schwa` and `dead_SCHWA`) fit much better with
the `dead_a`, `dead_A` scheme for the other vowels, and also with
how other upper- and lowercase schwa symbols are named.
The old names are deprecated, and can be removed quite soon because
they are not used anywhere -- not in xkeyboard-config at least.
(The dead vowel symbols were introduced fifteen years ago in commit
935dd37be4, to support compose sequences for Amharic, but neither
libX11 nor xkeyboard-config were ever updated to make use of them.)
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
Ten years ago, in commit 6d4acb0e3a, these four keysyms were added
to support new compose sequences that then could be typed with the
newish German T3 layout -- or at least, that was the intention.
The commit was in response to https://bugs.freedesktop.org/62189,
right before I retracted the patch after learning that there are no
precomposed characters that use those four symbols as diacritics.
The commit should have been reverted then, but... it lingered and
was forgotten. No layout in xkeyboard-config uses these symbols
(obviously, as they serve no purpose) and meanwhile the T3 layout
itself has become obsolete [1], so... it's time to clean up.
[1] https://de.wikipedia.org/wiki/DIN_2137#Neufassung_2018
"die Belegung T3 wird nicht mehr definiert, da die Erfahrung gezeigt
hat, dass eine solche Tastatur ohnehin nicht produziert wird"
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
They have been deprecated for more than twenty years,
and were either misspelled or too specifically named.
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
The symbolic name for the feminine ordinal indicator is 'ordfeminine',
so the name for the masculine ordinal indicator should be 'ordmasculine'
instead of just 'masculine'. Deprecate this latter form.
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
And deprecate the misspelled ones -- guillemots are seabirds [1],
guillemets are the sideways double chevrons [2].
[1] https://en.wikipedia.org/wiki/Guillemot
[2] https://en.wikipedia.org/wiki/Guillemet
This will allow to finally use properly spelt symbol names
in the layouts of xkeyboard-config.
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
Fixes compiler errors of "unexpected ';' before ')'" when calling
the SIZEOF macro on XvMC requests.
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
PM_spec is the spec for the Proxy Management Protocol, and the other
files for that protocol are only installed if legacy protocols
are requested from configure or meson
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Fixes deprecation warning for meson 0.56.0 and later.
Raises minimum meson version to 0.56.0.
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Sets minimum meson version to 0.50.0 due to use of:
* 0.49.0: {'/ with string arguments'}
* 0.50.0: {'install arg in configure_file'}
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
We could not find any evidence it was ever used, but defining it
caused C++11 compilers to complain:
/usr/X11R6/include/X11/Xfuncproto.h:173:24:
warning: ISO C does not permit named variadic macros [-Wvariadic-macros]
#define _X_NONNULL(args...) __attribute__((nonnull(args)))
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
The actual protocol and implementation details are unaffected - both
here and in xcb. Only the description/diagram section is off.
Noticed while skimming through the new 1.3 additions.
Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
This extension exists to serve one purpose: reliably identifying
Xwayland. Previous attempts at doing so included querying root window
properties, output names or input device names. All these attempts are
somewhat unreliable. Instead, let's use an extension - where that
extension is present we have an Xwayland server.
Clients should never need to do anything but check whether the extension
exists through XQueryExtension/XListExtensions.
This extension provides a single QueryVersion request only, and
that is only to provide future compatibility if we ever need anything
other than "this extension exists" functionality.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Olivier Fourdan <ofourdan@redhat.com>
Workaround the collision between ControlMask #defined in X11/X.h and
ControlMask used as the name of a structure member in
w32api/processthreadsapi.h in w32api 10.0.0
DRI3SetDRMDeviceInUse is a hint that lets a client tell the server
what DRM device it is currently using. This lets the server make
more informed decisions for what modifiers to return to the client.
This is needed for proper linux dmabuf feedback with Xwayland
All modern compilers (GCC>=4.6, Clang>=3.0) define this macro, so we can
use it to detect 64-bit longs without adding to the architecture list.
This change allows me to successfully run a simple X11 window on a
64-bit FreeBSD RISC-V QEMU VM via SSH forwarding. Without this change
I get an error that DISPLAY cannot be opened.
Signed-off-by: Alex Richardson <Alexander.Richardson@cl.cam.ac.uk>
The Xserver itself is capable of terminating itself once all X11 clients
are gone, yet in a typical full session, there are a number of X11
clients running continuously (e.g. the Xsettings daemon, IBus, etc.).
Those always-running clients will prevent the Xserver from terminating,
because the actual number of X11 clients will never drop to 0.
To solve this issue directly at the Xserver level, this add new entries
to the XFixes extension to let the X11 clients themselves specify the
disconnect mode they expect.
Typically, those X11 daemon clients would specify the disconnect mode
XFixesClientDisconnectFlagTerminate to let the Xserver know that they
should not be accounted for when checking the remaining clients prior
to terminate.
Signed-off-by: Olivier Fourdan <ofourdan@redhat.com>
