Hacker News new | past | comments | ask | show | jobs | submit login

https://unix.stackexchange.com/questions/572616/run-a-bash-c...

You can do that with the regular shell, just `^Z%; $next_command`, but I agree that nq might be more practical if that kind of workflow is done often.




That requires you still have the original shell open that ran the earlier commands; nq doesn't appear to have that limitation.


Ok, that sheds light into the kind of workflow this might be useful in, like calling stuff from a launcher instead of a terminal or something like that and having them go through nq automatically. Personally, I would just keep the shell open, but options are cool.


You can use e.g. the "screen" utility to detach from a shell and later re-attach. I use this often: start something at work, detach, then go home, re-attach.

You can have multiple sessions, give them names, etcetera.


I'm well aware of screen/tmux/dtach/&c.

If you accidentally exit the shell with all the jobs, you are done adding jobs to the queue, no?


nohup detatches the process from the shell


...but doesn't queue jobs




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: