On Wed, May 13, 2009 at 11:01 AM, Timothy Ball timb...@tux.org wrote:
On Wed, May 13, 2009 at 09:53:42AM -0400, Andrew Farnsworth wrote:
Just thought I would post this one...
/bin/bash ~/.bash_history
bwahahahahahahahahaa
--timball
That's awesome.
Now you have me tempted, just to
On Thu, May 14, 2009 at 9:21 AM, Andrew Farnsworth farn...@gmail.com wrote:
By default, .bash_history is not set executable nor does it have the
necessary #! line at the beginning of it, therefore this won't work. My
method of calling bash and passing it your .bash_history file as a
On Thu, May 14, 2009 at 9:53 AM, Brandon Valentine
bran...@brandonvalentine.com wrote:
sourcing
your bash_history is functionally identical to sourcing it inside a
running shell.
That rather muddled clause should read: sourcing your bash_history
inside a running shell is functionally
On Thu, May 14, 2009 at 10:55 AM, Brandon Valentine
bran...@brandonvalentine.com wrote:
On Thu, May 14, 2009 at 9:53 AM, Brandon Valentine
bran...@brandonvalentine.com wrote:
sourcing
your bash_history is functionally identical to sourcing it inside a
running shell.
That rather
On Wed, May 13, 2009 at 09:53:42AM -0400, Andrew Farnsworth wrote:
Just thought I would post this one...
/bin/bash ~/.bash_history
bwahahahahahahahahaa
--timball
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
