1,270 reputation
217
bio website codegnome.com
location
age
visits member for 2 years, 8 months
seen 1 hour ago

Twitter

Follow me on Twitter @_CodeGnome. If your tweets are mostly about coding, project management, or Linux, I will follow you back.

Open-Source Projects

I'm actively involved in the open source community. I contribute to various projects, and make many of my own tools available under the GPL. Some of my recent projects include:

  • ruby-dev
    • Automate builds of fully-functional Ruby on Rails VMs for quick-start development.
  • tempgit
    • Integrate Git with TDD: mechanize temporary Git repositories during testing.

Dec
11
awarded  Popular Question
Dec
8
answered Print numbers from 1-50
Nov
27
awarded  Nice Answer
Nov
16
revised Why does my grep expression need to use $'string' to match tab characters?
Clarify question and retrofit for the Q&A format. Retagging.
Nov
16
answered What return/exit values can I use in bash functions/scripts?
Nov
16
suggested approved edit on Why does my grep expression need to use $'string' to match tab characters?
Nov
16
revised Why does my grep expression need to use $'string' to match tab characters?
deleted 17 characters in body
Nov
16
revised Why does my grep expression need to use $'string' to match tab characters?
added 199 characters in body
Nov
16
answered Why does my grep expression need to use $'string' to match tab characters?
Oct
24
comment Linux log file structure change, abnormal (?) sed behaviour
od is from coreutils. xxd comes from vim-common. Either way, what makes you think a tcp dump can't include space characters? Think telnet or an http stream, for example.
Oct
24
comment Linux log file structure change, abnormal (?) sed behaviour
@mikeserv That won't work reliably. See my comments below your answer for an example of how it can break.
Oct
24
comment Linux log file structure change, abnormal (?) sed behaviour
For example, echo 'foo bar' | xxd | sed 's/.* //' will strip out the hex but will incorrectly return bar.
Oct
24
comment Linux log file structure change, abnormal (?) sed behaviour
sed 's/.* //' won't do what you expect if there are literal spaces in the ASCII dump section. It works for the OP's posted corpus, but it's not reliable unless you know the data will never contains spaces.
Oct
24
answered How to assign a string value to a variable over multiple lines while indented?
Oct
24
answered Linux log file structure change, abnormal (?) sed behaviour
Sep
30
awarded  Explainer
Sep
24
awarded  Autobiographer
Sep
3
comment Adding Text After Specific Line of File in Bash Script
@NecNecco If you want to edit the file in-place, rather than redirecting output to another file, then just add the --in-place flag when you call GNU sed.
Sep
3
answered Adding Text After Specific Line of File in Bash Script
Aug
11
revised How to source /etc/profile and .bashrc while starting vncserver
added 111 characters in body