https://bugzilla.redhat.com/show_bug.cgi?id=2130717
--- Comment #4 from Mike FABIAN <mfabian(a)redhat.com> ---
OK, in the last comment I explained what the situation is for input methods and
password prompts in terminals.
Not much can be done at the moment short of disabling the input methods in
terminals manually when needed, because the user knows when a password prompt
is shown.
*But* in this special case the user hasn’t even enabled ibus-typing-booster at
all, it has been enabled automatically by the on-screen-keyboard (OSK).
And there seems to be no way to manually temporarily disable it.
So what can we do then?
I was thinking about doing the following “hack” to make it less bad maybe:
*If* I can detect that OSK is shown *and* I can detect that the input is into a
terminal, *then* disable the (automatically enabled) ibus-typing-booster.
Of course that would have the disadvantage that the OSK would not show any
predictions in terminals, which might be bad for people who use chat or mail
programs in terminals. But apart from that, predictions are of rather limited
use in terminals anyway, terminals running shells usually offer other means to
complete, for example the bash completions (I sometimes use typing-booster
completions in terminals for some things which don’t work so well with bash
completions and bash completions for most stuff, but that is a very special
usecase).
So I think disabling the (automatically enabled) typing booster if OSK is shown
and input is into a terminal would be a resonable compromise.
*But*, unfortunately I cannot even do that at the moment because:
- I can detect that OSk is shown reliably only on Wayland, not on Xorg, see:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5865#note_1570500)
- I can detect that the current input goes into a terminal only on Xorg, not on
Wayland (I’ll open a new issue upstream for this ...)
So there is no way that I can detect both OSK and input into a terminal at the
moment.
I am at a loss what else I could do at the moment.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2130717