[BRLTTY] keycodes description
Shérab
Sebastien.Hinderer at ens-lyon.org
Tue Nov 26 01:25:34 EST 2019
Hi,
Aura Kelloniemi (2019/11/25 20:54 +0200):
> Or I might just push them to crates.io, which seems to be the Rust way of
> doing things. I don't know if distributing these bindings with BRLTTY would
> add any value, as Rust uses its own build system, and does not support
> installing any Rust libraries or interfaces system-wide, not at least in a
> standard way that I know of. This means that in order for anyone to use my
> bindings, they would need to have BRLTTY source code available. Maybe in the
> future Rust has better support for shared libraries/interfaces.
Is it really mutually exclusive? Do you have to choose between the two,
or could you somehow do both?
> I know. I just did not know if the library needs to send a command to the
> server to ask for the key press information, but apparently this is not the
> case.
You just have to enter tty mode. Once you have done that, key presses
are delivered to the client as they arrive, either as driver-specific
keycodes, or as brltty command codes, depending on what you requested
when entering tty mode.
Shérab.
More information about the BRLTTY
mailing list