Fluent-Search VS ydotool

Then found https://github.com/adirh3/Fluent-Search/issues/850

Nope.

Maybe it's Wox (https://github.com/Wox-launcher/Wox) which is no longer maintained. Out of all these Spotlight alternatives, I think Fluent search is the best https://github.com/adirh3/Fluent-Search

A bit more about mouseless navigation is here - https://fluentsearch.net/posts/no-more-mouse

You could make plugins - https://fluentsearch.net/posts/c-plugins-developer-guide

A hawk eye view of list of features - https://fluentsearch.net/posts/fluent-search-features-guide

Github repo if you delve deep - https://github.com/adirh3/Fluent-Search

You can also search browser tabs, in-app content, files and more. Settings are insanely customizable.

A case study done on it - https://tolgee.io/blog/case-study-fluent-search

Avolonia UI itself does an interview - https://twitter.com/AvaloniaUI/status/1492277669618229252

You can do macros and more with it - https://fluentsearch.net/posts/fluent-search-tasks-nightly-t...

All of this is done single handedly by @adirh3

Hidden gems of features are elaborated in changelog blog posts.

+1 for Fluent Search Fluent search github

Fluent Search and Everything

Try Fluent Search (https://github.com/adirh3/Fluent-Search). In addition to being a search utility (similar to Mac Spotlight), it has a feature called "search in-app using search screen hotkey" activated by CTRL+M. Sounds like what you're looking for.

Is this the right github repo? I can only see Issues.

Search like Spotlight: https://github.com/adirh3/Fluent-Search/

Wayland provides little by design, so this is quite typical. For example:

Screensharing is handled by pipewire [0], changing keyboard layouts aren't defined [1] by wayland, and generally anything Wayland devs think would 'corrupt' their protocol.

They leave most things to the compositor to implement, which leads to significant fragmentation as every compositor implements it differently.

Long gone are the days of xset and xdotool working across nearly every distro due to a common base, now the best you'll get is running a daemon as root to directly access `/dev/uinput` [2] or implementing each compositors accessibility settings (if they have them) as a workaround.

[0] https://superuser.com/questions/1221333/screensharing-under-...

[1] https://unix.stackexchange.com/questions/292868/how-to-custo...

[2] https://github.com/ReimuNotMoe/ydotool

I personally use libinput-gestures to call commands using touchpad gestures. You can also combine it with ydotool to bind macros and such to your gestures, e.g. 4 fingers swipe down closes the current window, 3 fingers swipe left or right changes workspace, etc

Have you tried using the systemd unit file supplied with ydotool? It's probably installed somewhere on your system. Else you can get it here and just change the install location of ydotoold.

For simulated keyboard there are tools such as dotool or ydotool and KeePass extensions such as KPUInput that work by giving the user access to /dev/uinput. That works, but it's a bit inelegant; I guess in the future a Wayland protocol for simulated keyboard input will emerge, like wlroots already has, also for virtual pointers.

ydotool is the generic equivalent. It works on both X11 and Wayland environments.

Autokey does not work yet, but there is Hawck and Espanso that you could play around with. And there is ydotool if all you need is simulating basic input (as in ydotool mousemove -x -10 -y -10, ydotool type 'Hello world!' and so on).

Does ydotool do what you need? I haven't even tried Wayland in years. I'm sure someday I'll find the need.