| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is necessary to guarantee the same API in case future versions of
XInput decide to break backward compatibility in their defaults.
Quoting `man 3 xiqueryversion`:
> Clients are required to use XIQueryVersion instead of
> XGetExtensionVersion if they use XI2 calls. The server may treat a
> client differently depending on the supported version announced by the
> client.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Ref issue #2.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
GCC is failing with "undefined reference"
https://travis-ci.org/anko/xkbcat/jobs/636386190 for reasons I cannot
comprehend or reproduce anywhere else, but clang is passing like it's
supposed to, so I guess that's our life now.
|
| |/
|
|
|
|
| |
I have no idea how the build is failing with the $(CC) change. Flags
look the same. Only difference is it's defaulting to gcc. Let's see if
this changes anything.
|
| |
|
|
| |
The fancy one was unreliable.
|
| | |
|
| |
|
|
|
| |
Who knows what C compiler users like to use. This should cause the
right one to be chosen automatically.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Whoops.
|
| |
|
|
|
| |
Avoids errors when nothing is there to be cleaned up: that's a
successful cleanup too.
|
| |
|
|
|
| |
I think this is a remnant from some time ago when output executable
wasn't called "xkbcat", but it is now, so the .PHONY is unnecessary.
|
| | |
|
| | |
|
| |
|
|
| |
Simpler, now that we don't need the time structs anymore.
|
| |
|
|
| |
Neater implementation, better performance.
|
| | |
|
| | |
|
| |
|
|
| |
Undoing my unnecessary feature creep.
|
| | |
|
| |
|
|
| |
Ensures that all output is received immediately if it's being piped.
|
| |
|
|
|
|
| |
This is clearer to read, as the amount of state being passed into the
utility function caused more distracting boilerplate than having a
separate function was worth.
|
| |
|
|
| |
Yeah, that did look a bit arcane.
|
| |
|
|
|
| |
Means we need no separate declaration, and it's a lot easier to infer
that the function is pure.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
It's seconds since epoch. People tend to type faster than that, but this
is a standard format.
Existing options work the same way.
|
| | |
|
| | |
|
| |
|
|
|
| |
It's quite a mess, but these links might clear stuff up for someone who
wants to know more.
|
| |
|
|
| |
More standard this way.
|
| | |
|
| | |
|
| |
|
|
|
| |
Easier to read. (Compilers would probably optimise the `printf` into a
`puts` anyway.)
|
| |
|
|
|
| |
Since this thing runs many times a second, but is very small, optimise
aggressively.
|
| |
|
|
|
|
|
| |
Improved comments.
Moved declaration of `printKeyPress` further down to decrease cognitive
load.
|
| | |
|
| |
|
|
|
|
|
| |
Yep, `hostname` is a `const char *` too, even though it's potentially
being assigned to. This is
[unintuitive](http://stackoverflow.com/a/9834194/777586), but
intentional.
|
| | |
|
| |
|
|
|
| |
Since XKBlib pulls in all of our other X dependencies, there's no need
to separately `#include` them.
|
| |
|
|
|
|
|
|
|
| |
There's no need to copy strings around when all we want is to print it
anyway. This is faster and easier to read.
Also made the output format adapt to whether `printKeyUps` is set:
There's no need to print `+` and `-` if all that we're printing is
keydowns anyway.
|
| | |
|