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:
Remove the dashes from a UUID using bash search and replace.
There is 1 alternative - vote for the best!
Remove dashes, also validates if it's a valid UUID (in contrast to simple string-replacement)
If you can do better, submit your command here.
You must be signed in to comment.
I'D say 's/slash/dash/g' ( '-' is dash. '/' is a slash)
Thanks, I'm aware :-)
[post edited]
The site copied the original mistake when I submitted my command.
The Python variant is more safe since it also validates the UUID (throwing errors if its not a valid UUID)
upvoted. I never knew bash could do that without a pipe through sed. This is documented where?
The bash manual page ;-)
man bashLook for section called "Parameter Expansion". The above example is doing a simple search and replace *inside* a shell variable. ${parameter/pattern/string}