commandlinefu.com is the place to record those command-line gems that you return to again and again.
Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
Hold ctrl and press z to pause the current thread. Run
fg
to resume it.
There is 1 alternative - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
@mallegonian what shell are you using for that?
Here in Linux bash, it is also ctrl-z to pause
then it's "bg %1" to background it
or "fg %1" to foreground it (bring it back as before the ctrl-z).
In fact, this can be done with multiple jobs which you can switch between background and foreground with
"bg %n" and "fg %n" (where n is the job number).
This also works in Korn shell (ksh).
fg will put it in the foreground. bg will put it in the background, and you don't need '%1' if that is the only job running.
If you put it in background, remember to run "disown" to SIGHUP won't be sent to the process if the shell is closed.
It's not a thread, it's a job