GitLab

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Povilas Kanapickas <povilas@radix.lt>

Signed-off-by: Povilas Kanapickas <povilas@radix.lt>

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>

Signed-off-by: Povilas Kanapickas <povilas@radix.lt>

This was a copy-paste error from TOUCHCLASS. The protocol structs use
uint8_t for num_touches.
Signed-off-by: Povilas Kanapickas <povilas@radix.lt>

The actual protocol structs use uint8_t.
Signed-off-by: Povilas Kanapickas <povilas@radix.lt>

Signed-off-by: Povilas Kanapickas <povilas@radix.lt>

TODO, while useful for grepping, does not actually mean anything, so
completely useless.
Signed-off-by: Povilas Kanapickas <povilas@radix.lt>

Signed-off-by: Povilas Kanapickas <povilas@radix.lt>

Signed-off-by: Povilas Kanapickas <povilas@radix.lt>

Signed-off-by: Povilas Kanapickas <povilas@radix.lt>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Olivier Fourdan authored Mar 09, 2021 and Peter Hutterer committed Apr 29, 2021

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>

This way we pass make check/ninja test even where the module is not available

See !31 (comment 879823)

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Fixes #20

Build and install with meson, build and install with autotools and then run
diff to compare the two directory trees. They should be the same.

This does not install the legacy protocols, they're behind a configure switch.
The spec-build is disabled in autotools because we know meson doesn't do that
yet, so no point in comparing those.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

This now matches the autotools installation
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Generated outputs are identical
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

autotools can't pass arguments, so let's default to 'verify' in the script
itself and for distcheck to succeed, we need to set an environment variable to
search for the header (it's an out-of-tree build).

And due to the very faint chance of there being no python during the
xorgproto build, let's make that conditional too.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

More readable grouping this way
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

An alphabetically ordered list is nice, but it's harder to figure out
based on a diff whether a commit affects the legacy protocols or not.
Let's group those separately, first the normal protocol files, then all the
legacy-only ones.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

No change to the header, comments only.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

These keysyms were already present in 2.6.11 which is the first tag in git.

A few notes on specific keys here:
- KEY_EJECTCLOSECD is theoretically different to XF86XK_Eject (kernel
  KEY_EJECTCD) but the actual usage in the hwdb remappings seems to be
  random. Either way it's already mapped to XF86XK_Eject in
  symbols/inet so let's just add an entry for the sake of documenting it.
- XF86XK_CycleAngle seems like the best match for KEY_ANGLE
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

A few notes on specific keys here:
- Some existing keysyms used some brand names. e.g. KEY_WORDPROCESSOR ->
  existing XF86XK_Word. This introduces some minor inconsistency with
  unbranded new keys like KEY_GRAPHICSEDITOR -> XF86XK_GraphicsEditor.
- XF86XK_DisplayToggle is *not* XF86XK_Display (which represents
  KEY_SWITCHVIDEOMODE)
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

A few notes on specific keys here:
- There are exiting XF86XK_ZoomIn/Out keys, but they don't seem appropriate
  for KEY_CAMERA_ZOOMIN and friends. New symbols are introduced here.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>