103 reputation
3
bio website
location Bronx, NY
age 42
visits member for 1 year, 8 months
seen 2 days ago

Advanced Beginner learning how to program. Mostly Ruby, Ruby on Rails, some Linux.


Jun
14
awarded  Editor
Jun
14
revised Hardware concerns for optimal ruby on rails development on ubuntu machine
added 4504 characters in body
Jun
14
comment Hardware concerns for optimal ruby on rails development on ubuntu machine
Thanks! That's a lot of info. I'll add some relevant parts to my question above.
Jun
14
comment Hardware concerns for optimal ruby on rails development on ubuntu machine
Hmmm... doesn't seem to work. Got -bash: dmidecode: command not found
Jun
14
comment Hardware concerns for optimal ruby on rails development on ubuntu machine
Thanks for comment, @AndrewCrawford. RoR development requires using the terminal extensively so I'm pretty familiar with it and using basic unix commands there. I'm not really sure what my specs are, though. I hope to get some insight here.
Jun
14
asked Hardware concerns for optimal ruby on rails development on ubuntu machine
Nov
25
awarded  Scholar
Nov
25
accepted How do I create a “here document” within a shell function?
Nov
25
comment How do I create a “here document” within a shell function?
@glennjackman Using spaces instead of tabs could indeed be the source of my problem. I've arranged my text editor to use two spaces instead of tab by default. Thanks!
Nov
24
comment How do I create a “here document” within a shell function?
That worked for me, @Ярослав_Рахматуллин. I don't think that the [-] is an option for Darwin's here files. cat << _EOF_ not cat <<- _EOF_
Nov
24
comment How do I create a “here document” within a shell function?
Thanks @Ярослав_Рахматуллин Though adding the - to << didn't solve my problem, removing the whitespace before the _EOF_ did. Perhaps "here documents" with cat << works in Darwin but not cat <<-. It's a shame since <<- is so useful. Move your comment into your answer and I will accept it. Addendum: bash may in fact be broken. Possibly broken by me, possibly Mac's Darwin's limitations...
Nov
24
asked How do I create a “here document” within a shell function?
Nov
10
comment Is there a simpler form of find . -name “*substring_of_filename*” on Mac OS X and Linux?
Thanks, @user_unknown. I couldn't figure out why I wasn't getting find ~ -name "*.pdf" to work on my mac os x until I tried leaving out the quotes. In Mac OS X, it seems that one must leave out the quotes.
Nov
10
awarded  Supporter