931 reputation
1612
bio website
location
age
visits member for 4 years, 5 months
seen Jan 26 at 10:38

Nov
11
awarded  Yearling
Nov
11
awarded  Yearling
Nov
6
awarded  Notable Question
Aug
31
awarded  Nice Answer
May
14
awarded  Famous Question
Feb
16
comment awk/sed + replace only the second char with one space
@Eytan the <<<'34.34.55.4' part was just an example for input. Simply replace it with a file name, or pipe something to it with echo. The sed command will certainly work.
Feb
16
comment awk/sed + replace only the second char with one space
@Zoredache although I usually recommend awk as well, its not so painful in sed ;)
Feb
16
answered awk/sed + replace only the second char with one space
Feb
15
comment Sed for windows
I would highly recommend cygwin, the windows shell is such a PITA for unix-like commands. However, if you are planning on sticking with the windows shell, the easiest way ive found to run sed or awk is by creating a script file and then calling the file with the -f flag. For example sed -f some_sed_script.sed or awk -f some_awk_script.awk
Feb
13
answered Find how much filespace specific filetype is taking under a directory?
Feb
6
answered how to redirect output of command line execution to more than one file according to weight of output
Feb
5
revised How to remove duplicated files in a directory?
deleted 14 characters in body
Feb
5
revised How to remove duplicated files in a directory?
deleted 27 characters in body
Feb
5
revised How to remove duplicated files in a directory?
added 334 characters in body
Feb
5
answered How to remove duplicated files in a directory?
Feb
4
comment How different shell scripts map to different OSes
@Telemachus I should have clarified that I meant using #!/bin/bash as the interpreter
Feb
4
answered How different shell scripts map to different OSes
Jan
27
revised Find all files older than one minute
added 6 characters in body
Jan
27
answered Find all files older than one minute
Jan
27
comment Learning Shell Script, What's Next?
The faster you forget about The Advanced Bash-Scripting Guide the better off you'll be. As the bash FAQ I linked to above puts it "The infamous "Advanced" Bash Scripting Guide should be avoided unless you know how to filter out the junk. It will teach you to write bugs, not scripts. In that light, the BashGuide was written: mywiki.wooledge.org/BashGuide"