Check These Out
If script.sh contains only these two lines:
$ uname -a
$ whoami
If you don't want to commit files to subversion, and don't want those file to show up when doing an "svn stat", this command is what you need
perl-less way
Like `tidy`, `xmllint` can be used to prettify XML files.
The --nsclean option is also useful to remove redundant namespaces.
swap out "80" for your port of interest. Can use port number or named ports e.g. "http"
fade [type] fade-in-length [stop-time [fade-out-length]]
Apply a fade effect to the beginning, end, or both of the audio.
An optional type can be specified to select the shape of the fade curve: q for quarter of a sine wave, h for
half a sine wave, t for linear (`triangular') slope, l for logarithmic, and p for inverted parabola. The
default is logarithmic.
A fade-in starts from the first sample and ramps the signal level from 0 to full volume over fade-in-length sec?
onds. Specify 0 seconds if no fade-in is wanted.
For fade-outs, the audio will be truncated at stop-time and the signal level will be ramped from full volume
down to 0 starting at fade-out-length seconds before the stop-time. If fade-out-length is not specified, it
defaults to the same value as fade-in-length. No fade-out is performed if stop-time is not specified. If the
file length can be determined from the input file header and length-changing effects are not in effect, then 0
may be specified for stop-time to indicate the usual case of a fade-out that ends at the end of the input audio
stream.
All times can be specified in either periods of time or sample counts. To specify time periods use the format
hh:mm:ss.frac format. To specify using sample counts, specify the number of samples and append the letter `s'
to the sample count (for example `8000s').
as per eightmillion's comment.
Simply economical :)
As of this writing, this requires a fairly recent version of util-linux, but is much simpler than the previous alternatives. Basically, lsblk gives a nice, human readable interface to all the blkid stuff. (Of course, I wouldn't recommend this if you're going to be parsing the output.) This command takes all the fun out of the previous nifty pipelines, but I felt I ought to at least mention it as an alternative since it is the most practical.
This command will find all occurrences of one or more patterns in a collection of files and will delete every line matching the patterns in every file