-
Notifications
You must be signed in to change notification settings - Fork 416
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
Not able to restore grunt #32
Comments
Hi, thanks for reporting the issue. This is a bug and I don't know how to handle it for now. To clarify:
Weird env variables Thinking about other solutions to handle this, we could have a user option like this:
The above states: to restore |
Hi @bruno- , yes I think having that feature would help. Anyway, I thought a feature that is almost similar to that already exists? I saw this in the docs:
and
I also tried them btw but it didn't solved the issue. There was no output unlike the setting I used on my 1st comment - #32 (comment)
and
|
Yea, those features are similar, but not really what we need here. Okay, I'll work on a feature that will hopefully help with this and then let you know. |
Hi, this feature should now be implemented.
Now, when Let me know if it works! |
Have you tried save/restore the whole command instead of the process? Grunt is a bad example because it eats up the arguments.
|
I just tested the command I'd love to improve the "process" for saving commands! Currently this is pretty isolated in this function here. I encourage you to submit a pull request that improves on that. Also feel free to ask related questions if there's any. |
@bruno- For some reason, it still doesn't work. Here's the contents of ~/.tmux/resurrect/last:
Here's my tmux.conf:
|
It doesn't work here :( I created a new issue #43 |
@basco-johnkevin thanks for the patience with this. After a while, I realized what's the problem:
The above is actually considered to be a feature that makes Here are the steps to solve the problem and test if grunt is restoring properly:
Hopefully it works for you now! |
Any updates on this @basco-johnkevin ? |
Hey guys, I'm doing a small issues cleanup. This feature seems to work now, please reopen or report again if you find any issues. |
Should run grunt using "grunt development"
I'm using this setting in .tmux.conf: set -g @resurrect-processes ':all:'
This is the output in the console when resurrecting:
grunt ARCHFLAGS=-arch i386 -arch x86_64 Apple_PubSub_Socket_Render=/tmp/launch-Ou97Qf/Render
➜ pdm git:(master) ✗ grunt ARCHFLAGS=-arch i386 -arch x86_64 Apple_PubSub_Socket_Render=/tmp/launch-Ou97Qf/Render
Warning: Task "ARCHFLAGS=-arch" not found. Use --force to continue.
The text was updated successfully, but these errors were encountered: