-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
Fix shortcuts failing #496
Conversation
@kdheepak still doesn't fix it for me, but changed the error. Shortcut is definitely there and definitely executable, but for some reason taskwarrior-tui it's still saying "failed." |
Are you able to run the script from the command line? |
yes, no problem |
|
|
maybe when it fails, you could make it print the errno rather than the shortcut key number? that would probably be more valuable information |
Weird. Two things to check
|
It is already supposed to print stdout and stderr if it fails: Lines 1892 to 1905 in 1a9dedd
I think the path of the file is incorrect for some reason? What do you have in your |
It's hitting one of these two error conditions: Lines 1905 to 1910 in 1a9dedd
( btw I'll have update it to print different errors in the next version. ) I have to go through the rust docs again to see what the error case is for those. I think the first is it is not able to get the output of the script for some reason, which would be very weird. The second is that the script does not exist (which would match with the error code you are seeing, i.e. |
You mentioned you tried this:
Did you try |
yes, I tried passing gobbledygook to test.sh
I'll try to check out your source code above, but I'm not a rust programmer |
Also, I have two shortcuts programmed, and the error number it prints is the shortcut number, not the errno (unless it's just a coincidence that it's erroring 1 for sc 1 and 2 for sc 2) |
There's two This one prints something related to the error:
This prints something incorrect I think:
I'll have the change the second |
If you are interested in building from source, you should be able download the repo and just run Then you can modify If you add this environment variable too:
Then the logs will go in the current working directory. |
I'm using this package: https://github.com/dirs-dev/dirs-rs#features And it uses this code to get the location to put the log files in: Lines 61 to 67 in 1a9dedd
|
Also, my bad. It is not |
|
Can you add a |
Is this something you were able to look into? Maybe we should open a new issue to track it? |
Hi, I also have the exact same issue (same issue in the first place, then shortcut failed with error 1, and same logs), and I can help if necessary. We can open an issue at your convenience |
Can you try the latest |
Can you try the latest |
Can you try adding a |
It's working now ! Interesting |
Yay! |
I updated the documentation to reflect this. Hopefully this solves it for @vigilancetech-com too. |
Lovely. Thanks a lot ! |
And I made a new release with the fix. |
yes, it works for me now as long as it has a shebang line |
Fixes #494