From 9c35a57cfe97ab26835a052bba1b8d554ce259a6 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Wed, 11 Dec 2024 09:23:11 +1000 Subject: [PATCH] doc: fix some linewrapping issues Part-of: --- src/libei.h | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/src/libei.h b/src/libei.h index beb96a6..7670be3 100644 --- a/src/libei.h +++ b/src/libei.h @@ -60,13 +60,11 @@ extern "C" { * libei clients come in @ref ei_new_sender "sender" and @ref ei_new_receiver * "receiver" modes, depending on whether the client sends or receives events * from the EIS implementation. See @ref libei-sender and @ref libei-receiver - for - * API calls specific to either mode. + * for API calls specific to either mode. * * @note A libei context is restricted to either sender or receiver mode, not * both. The EIS implementation however may accept both sender and receiver - clients, - * and will work as corresponding receiver or sender for this + * clients, and will work as corresponding receiver or sender for this * client. It is up to the implementation to disconnect clients that it does not * want to allow. See eis_client_is_sender() for details. * @@ -92,7 +90,7 @@ extern "C" { * The sender client API is available only to clients created with * ei_new_sender(). For those clients the EIS implemententation creates * devices and but it is the libei client that sends events **to** EIS - implementation. + * implementation. * The primary use-case is input emulation from a client, akin to xdotool. * * It is a client bug to call any of these functions for a client created