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
run_after doesn*t work #123
Comments
|
Which guide did you follow? I'm currently reworking that entire
functionality but haven't released the latest changes as a gem yet.
I would need to know more about the script and when you're expecting it
to run, and how you know it isn't. What does the script do? Are you
seeing any errors? I can tell you that this feature is working for me,
but I haven't tested it on anything but my one specific dev setup.
The new Hooks feature coming in 2.0 is way better, though :)
…-Brett
On 29 Oct 2021, at 4:31, can-I-do wrote:
hey,
first thx for the tool and the nice guide putting it into the status
bar from iterm!
I just followed the guide and the "run_after" command doesnt seem to
do anything for me :(
i just added a new line at the bottom:
run_after: /path/smth.sh
also tried
run_after: "/path/smth.sh"
any advice here?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#123
|
|
https://brettterpstra.com/2021/10/15/see-what-youre-doing-in-the-iterm-status-bar/ |
|
What version of doing is shown when you run `doing -v`?
…On 29 Oct 2021, at 6:10, can-I-do wrote:
https://brettterpstra.com/2021/10/15/see-what-youre-doing-in-the-iterm-status-bar/
that is the guide, and wanted to start the small script provided
there, but it is not starting anything, also no other scripts :)
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#123 (comment)
|
|
doing -v |
|
I also tried it with hooks, as I found it in the docs ;) but still doesn't seem to work. Maybe smth is wrong with my system... |
|
Hooks won't do anything unless you install 2.0pre from source, which I wouldn't recommend yet. It's a new feature under development.
But I think when they are released, they might solve the issue. They're more reliable than run_after, overall. You might have to wait a bit, though.
- Brett
…On Nov 3, 2021, 2:34 AM -0500, can-I-do ***@***.***>, wrote:
I also tried it with hooks, as I found it in the docs ;) but still doesn't seem to work. Maybe smth is wrong with my system...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
|
so, I installed 2.0, first of all thx for the update!
if I manually run /bin/bash ~/after_doing.sh it is working, but from doing now or finish it is not |
|
Does the debug log show up when you run a command? (be sure to run with |
|
Also try running |
This seems to work. Same with but still it is not doing smth :/ I am really not sure why ... probably some really silly mistake on my side than. |
|
- I doubt it will help, but just to be sure could you try with an
absolute path instead of the `~` in the hook?
- Also, have you tested with any other scripts to see if there's
something specific about after_doing.sh that might be causing issues?
- And does after_doing.sh have executable (`chmod a+x`) permissions? (I
know running via /bin/bash shouldn't require it, but it could be a
general permissions issue).
…On 23 Nov 2021, at 2:01, can-I-do wrote:
```
❯ doing now test hook
New entry: added "Test hook" to Currently
❯ DOING_PLUGIN_DEBUG=true doing
> Logging at level: debug
8:47am: Test hook (Currently)
> Plugin Manager: Registered export plugin "csv"
> Plugin Manager: Registered export plugin "html"
> Plugin Manager: Registered export plugin "timeline"
> Plugin Manager: Registered export plugin "markdown"
> Plugin Manager: Registered export plugin "taskpaper"
> Plugin Manager: Registered export plugin "template"
> Plugin Manager: Registered export plugin "doing"
> Plugin Manager: Registered import plugin "calendar"
> Plugin Manager: Registered import plugin "doing"
> Plugin Manager: Registered import plugin "timing"
> Hook Manager: Registered post_write hook
> Config: Local config files found:
> ENV: No EDITOR environment variable, testing available
> editors
```
This seems to work. Same with `Doing.logger.warn`
```❯ doing now test hook
New entry: added "Test hook" to Currently
> Hooks: /bin/bash ~/after_doing.sh```
but still it is not doing smth :/ I am really not sure why ...
probably some really silly mistake on my side than.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#123 (comment)
|
really strange :/ and sad, but I guess it is something on my side if it works for others. dont want to bother you further with my problems :D |
|
Echoing to STDOUT may or may not show up at all, given it's running
inside a process, but the Doing.logger statements definitely should.
I don't mind debugging this with you, I'd like this feature to work for
everyone, but I'm not sure what else to try right now. If I think of
anything else, I will let you know. And if you come up with any more
clues, please let me know!
…-Brett
On 23 Nov 2021, at 6:26, can-I-do wrote:
- no doesn't work
- tried it with an echo "test" script -> didn't work
- yes after and test.sh are executable
really strange :/ and sad, but I guess it is something on my side if
it works for others. dont want to bother you further with my problems
:D
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#123 (comment)
|
|
thanks for your help! I will try my best to figure it out |
I followed these instructions: https://brettterpstra.com/2021/10/15/see-what-youre-doing-in-the-iterm-status-bar/ With the hooks mod from here: ttscoff/doing#123 https://github.com/ttscoff/doing/wiki/Hooks And my fix from here: ttscoff/doing#130 On branch main Your branch is ahead of 'origin/main' by 3 commits. (use "git push" to publish your local commits) Changes to be committed: modified: bash_prompt

hey,
first thx for the tool and the nice guide putting it into the status bar from iterm!
I just followed the guide and the "run_after" command doesnt seem to do anything for me :(
i just added a new line at the bottom:
run_after: /path/smth.sh
also tried
run_after: "/path/smth.sh"
any advice here?
The text was updated successfully, but these errors were encountered: