-
-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Options possible #245
Comments
Yeah, can't do anything with mousemove, no matter what I try:
The other options also don't work:
let's try the absolute option:
|
I see the same problem "invalid option" everywhere when using build from present master
Version before #238 works. |
I compiled the master branch and had the same issue. Switching to commit e573cfb fixed this. |
I reverted back to the "old" way of doing it (but adding an option for version) and it seems to work fine. My coding skills are poor and I'm sure there are valid reasons to use the elegant getopt_long method, but for me it created more headache than it solved. So if this can be verified to work for others, perhaps someone can make the fix so that master works again? In more detaild what I did was: remove:
and then add back:
|
Pretty much sorry for that and for disappearing for so long. Hopefully now my smaller PR #252 cleans a bit more without making it impossible to use. We should consider adding some unit tests under here, to make it simpler to make sure basic functionality works. |
Note for peope who wanna build this for fedora silverblue. Build deps could also be in toolbox
|
There is a bug introduced by #238 (Client/ydotool.c#L137) that when you use
ydotool type -f file.txt
there is aNot a valid option
error.The problem is, that it is checked if the option is help or version else exit. But now you can't use other options in subcommands.
The text was updated successfully, but these errors were encountered: