Comment by ~geb on ~geb/dotool
Ah the issue is that dotool simulates keys with its own virtual keyboard (uinput device), so the keyup doesn't change the state assigned to your real keyboard. Similar to if you had two keyboards plugged in, releasing the modifiers of one isn't enough. I can't think of an easy solution though I'm afraid.
Comment by ~geb on ~geb/dotool
You should be able to find the names of the modifiers keys you want in the output of --list-keys
For example: dotool --list-keys | grep alt
Hope that helps!
REPORTED
RESOLVED CLOSEDComment by ~geb on ~geb/dotool
Hi Matteo, you could do something like:
echo 'typedelay 0 typehold 0 type text example' | dotool
By the way, don't worry but this todo is only for tracking bugs to fix and features to implement and the mailing list or the matrix chat is where to ask questions: https://lists.sr.ht/~geb/numen
REPORTED
RESOLVED CLOSEDComment by ~geb on ~geb/dotool
Great! Thanks for reporting back with the solution!
REPORTED
RESOLVED CLOSEDComment by ~geb on ~geb/dotool
I'm not sure why the udev rule isn't working, being in the group (can check
id -Gn
for certainty) and rebooting should be enough normally.It's the permissions of /dev/uinput which are the issue, and what the udev rule is supposed to set. Here's what I get running
ls -l /dev/uinput
:crw-rw---- 1 john input 10, 223 Aug 10 11:08 /dev/uinput
You could
chown
/chmod
/dev/uinput as a sad workaround, it would need to be done every reboot.The udev rule could technically be being overridden by another udev rule, but that's never came up before. A systemd release last year broke its support for uinput udev rules, but the next release resolved it: https://bugs.archlinux.org/task/79391
Ticket created by ~geb on ~geb/numen
Yeah, I've since decided against command model switching, there's little to justify it. There's WIP transcription model switching on the "switching" branch.
On the branch there's a new
--models
argument (but might revert to an environment variable) and atmodel
action to switch transcription model. I thought about a@transcribe
parameter also, but I think atmodel
action and a special<transcription>
phrase that runs before transcription (no implemented yet) would give the most flexibility with the least funkiness. That way you could switch model and keep using the same "scribe" phrases (in addition to being able to have a dedicated "french scribe" phrase), and<transcription>
would also be useful in it's own right for playing a sound or displaying a notification or whatever on transcription.