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:
OpenDocument documents from OpenOffice.org,LibreOffice
and other applications, are actually ZIP archives.
Useful informations in these archives are in XML format.
Here we like it or do not. Anyway, the XML files have the unfortunate tendency to
not be indented, and for good reason: they consist of only one line!
To solve the problem and to use a proper editor on the content,
I proceed as follows.
Required xmlindent
You can also use :
zip document.odt content.xml
And it works with vi instead of nano !
Like `tidy`, `xmllint` can be used to prettify XML files.
The --nsclean option is also useful to remove redundant namespaces.
The XML document can be transformed to text, XML, HTML or anything else. The --stringparam option allows to set XSL variables externally.
This will indent the input to be more readable. Warnings and messages are not send to STDOUT so you can just use a pipe to create the formatted outputfile, like:
tidy -i -xml in.xml > out.xml
xmllint2 comes with GNU libxml2 library.
(based on: http://vim.wikia.com/wiki/Format_your_xml_document_using_xmllint)
This function uses xmllint to evaluate xpaths.
Usage: xpath /path/to/element XMLfile
Diffs two xml files by formatting them first using xmllint and then invoking diff.
Usage: diffxml XMLFile1 XMLFile2
Removes all lines between the lines containing "" and "", including these lines itself
Backdrop:
Sometimes when working with XML files without an graphical editor, large comment-/annotation-blocks taper the readability to walk through the file. I like to create a copy of such documents without these annotations. As the documentation itself is in documentation tags inside the annotation tags an therefore graphical editors tend to put the annotation tags in their own lines, this command removes all documentations within annotation-tags.
If everything validates, there's no output. Can be handy to run on a cron job set up to email output.
I use this command in my Conky script to display the number of messages in my Gmail inbox and to list the from: and subject: fields.
Gets the latest podcast show from from your favorite Podcast. Uses curl and xmlstarlet.
Make sure you change out the items between brackets.
Ever wanted to stream your favorite podcast across the network, well now you can.
This command will parse the iTunes enabled podcast and stream the latest episode across the network through ssh encryption.
Might be able to do it in less steps with xmlstarlet, although whether that would end up being shorter overall I don't know - xmlstarlet syntax confuses the heck out of me.
Prompts for your password, or if you're a bit mental you can add your password into the command itself in the format "-u user:password".
This one will work a little better, the regular expressions it is not 100% accurate for XML parsing but it will suffice any XML valid document for sure.
Limited, but useful construct to extract text embedded in XML tags. This will only work if bar is all on one line.
If nobody posts an alternative for the multiline sed version, I'll figure it out later...