https://bugs.kde.org/show_bug.cgi?id=478219
--- Comment #17 from Jakob Petsovits <[email protected]> --- > But wait: wouldn’t *input methods* be more adapted for this task? E.g. detect > a modifier state and output specific string when matching some key combos? Indeed, on our Input Goal proposal at https://phabricator.kde.org/T17433, we included a bullet point "Expand configurable strings into pre-defined snippets" in the "Better IME support" section. I see no reason why an input method couldn't also handle shortcuts with modifiers to do the same thing. However, if the user already relies on a different input method, we will have to improve quick-switching between their current input method and this proposed new one. This ties back into https://invent.kde.org/teams/goals/we-care-about-your-input/-/issues/13 again. On the other hand, I also sneakily included a text snippet action into our designs for touch/stroke gesture actions, in https://invent.kde.org/teams/vdg/issues/-/issues/99 (Gesture Customization UX), search for "Assigning emulated key presses". This makes me think that perhaps an input method by itself is too limited a use case, and we may want to consider this kind of action as part of an overall Plasma/KWin automation push. I wonder if perhaps a KWin plugin is the right way to add this. I guess if it were a built-in input method, the plugin could briefly enable this IM and then switch back to whatever was active before. Lots of options to implement this. Also note that this bug report is listed on https://community.kde.org/Plasma/Wayland_Known_Significant_Issues#Keyboard/typing right now. -- You are receiving this mail because: You are watching all bug changes.
