https://bugs.documentfoundation.org/show_bug.cgi?id=174068
--- Comment #10 from Adalbert Hanßen <[email protected]> --- (In reply to BogdanB from comment #9) > Adalbert, see bug > https://bugs.documentfoundation.org/show_bug.cgi?id=139807. It's the same > issue? *It might be the same bug. It also might be another one.* #139807 uses xdotool, command-line X11 automation tool, which lets you programmatically simulate keyboard input and mouse activity, move and resize windows, etc. The other bug report is so brief that I first did not understand what he's doing there, why he's doing it, or what he expects to happen. Most importantly, he doesn't explain how his command ‘sleep 1; xdotool key --delay 0 a BackSpace b’—which he enters into a terminal—actually affects LibreOfficeWriter. xdotool is part of the Linux X11 environment. I don't know if it is still available under a more recent Linux version than mine, especially one which uses Wayland, which is mentioned in the other thread. There might be some Wayland emulation available under certain Wayland using Linux flavors, but they might also miss there (depriving us from many useful X11-capabilities). In the other bug report, he is pressing backspace very quickly between a and b. Processing backspace is different from adding another character. Adding a character is different from the backspace operation and it is different in insert mode (almost always used) and in overtype mode. When backspace is pressed, the character left to it has to be removed from some editing buffer and what's behind it, has to be shifted "to the left". The time for this shift operation depends on how much is right to the editing position in that editing buffer. It looks like that what is shown to the user in the document editing area is asynchronously updated. The different threads on such multitasking stuff has to be carefully secured against race conditions and the like. If the critical sections are not carefully designed and semaphores are not applied right, shit may happen. That's hard to *test*. One has to carefully *inspect* the code and ask questions about synchronisation. -- You are receiving this mail because: You are the assignee for the bug.
