It has added support for it
---
hw/xfree86/common/xf86pciBus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/xfree86/common/xf86pciBus.c b/hw/xfree86/common/xf86pciBus.c
index bed4434..15bd59e 100644
--- a/hw/xfree86/common/xf86pciBus.c
+++ b/hw/xfree86/common/xf86pciBus.c
v4:
- Fix typo in description
- Use just 'dead_currency Er' instead of 'dead_currency Er Equals'
- Use also 'Compose/dead_currency Equals Pe'
>From ae1bf2fbd2c3893366198a80aed8743af656ee88 Mon Sep 17 00:00:00 2001
From: Victor Kustov
Date: Mon, 17 Oct 2016 19:44:36 +
Subject: [PATCH 1/5] Compo
v2 was assigning 'Compose Equals p/P' to rouble currency sign "₽".
Currencies also have a "canonical" form 'dead_currency ...';
in particular 'dead_currency P' results in pesetta sign "₧".
Assign the 'dead_currency Minus p/P' to pesetta,
and 'dead_currency Equals p/P' to rouble.
>From ae1bf2fbd2
On Thu, Nov 03, 2016 at 01:22:03PM +0100, Mariusz Mazur wrote:
> What I did:
> 1. Switched the overlay key to act as a modifier.
> interpret Overlay1_Enable+AnyOfOrNone(all) {
> -action= LockControls(controls=Overlay1);
> +action= SetControls(controls=Overlay1);
>
> 2. Bound i
I've noticed that the transformation matrices that this function builds for
rotated screens is not quite correct.
In particular, it consistently builds maps from 0 to width or height
instead of from 0 to width-1 or height-1.
This means that an inverted screen maps (0,0) to (width,height) instead
Short version: using keyboard overlay to send e.g. XF86LaunchA, then
intercepting that with something like xbindkeys and launching an app
often triggers a bug which messes up the 'keycombo intercept'
mechanism in xorg.
Long version: inspired by fully programmable keyboards like the
ergodox or UHK
Hi,
On 03-11-16 09:59, Olivier Fourdan wrote:
In glamor_init(), if the minimum requirements are not met, glamor may
fail after setting up its own CloseScreen() and DestroyPixmap()
routines, leading to a crash when either of the two routines is called
if glamor failed to complete its initializati
Hi,
On 02-11-16 21:39, Keith Packard wrote:
I think it is possible that output could get queued to a client during
CloseDownClient. After it is removed from the pending queue, active
grabs are released, the client is awoken if sleeping and any work
queue entries related to the client are process
In glamor_init(), if the minimum requirements are not met, glamor may
fail after setting up its own CloseScreen() and DestroyPixmap()
routines, leading to a crash when either of the two routines is called
if glamor failed to complete its initialization, e.g:
(EE) Backtrace:
(EE) 0: Xwayland (
