Is there an equivalent in irb to command: history in bash?

[Stephen Bannasch]

Is there an equivalent in irb to the command history in bash?

After I've been doing a bunch of work in the shell I often use the
history command in bash to get a list of all the commands I've
executed which I copy and past into an editor to document the work I
did.

Is there an equivalent command for irb which would list by lines each
command I have entered? Rightnow I use readline to scan backwards
and copy and paste individually.

Thanks for any suggestions.

 

[Chris Shea]

Is there an equivalent in irb to the command history in bash?

After I've been doing a bunch of work in the shell I often use the
history command in bash to get a list of all the commands I've
executed which I copy and past into an editor to document the work I
did.

Is there an equivalent command for irb which would list by lines each
command I have entered? Rightnow I use readline to scan backwards
and copy and paste individually.

Thanks for any suggestions.

I think this irb_history business from Ben Bleything is what you want:
http://blog.bleything.net/pages/irb_history

HTH,
Chris

 

[Ben Bleything]

I think this irb_history business from Ben Bleything is what you want:
http://blog.bleything.net/pages/irb_history

I think so too

Ben

 

[Stephen Bannasch]

I think so too

Thanks ... perfect ;-)

 

[sishen]

Note: parts of this message were removed by the gateway to make it a legal Usenet post.

Hi, Ben. really great work,

One more feature request: Why not auto save the history in .irb_history,
just like what the history of bash does?

sishen

 

[Ben Bleything]

Hi, Ben. really great work,
Thanks!

One more feature request: Why not auto save the history in .irb_history,
just like what the history of bash does?

So that's something that should probably be documented better. The code
that I wrote relies on pre-existing history enabler code. It is meant
as a supplement to something like Michael Granger's persistent IRB
history:

http://www.rubygarden.org/Ruby/page/show/Irb/TipsAndTricks

or Wirble (gem install wirble), which just packages the above with some
other IRB hacks. If you set up Michael's code or install wirble and
enable history, it'll save your history between sessions.

My code does not replace that stuff; it serves a different purpose.
Mine is about accessing the history you already have. I've been meaning
to re-open a conversation I was having with wirble's author over a year
ago, to get my code included there. Once that happens (if Paul is still
interested), you'll be able to just install/enable wirble and have all
your history goodies for free.

Hope that answers your question

Ben

 

[Tomas Pospisek's Mailing Lists]

I think so too

Ben

Ben, don't you want to add a link from the blog entry to where people can
get the chunk of code that will perform the magic?
*t

 

[Ben Bleything]

Ben, don't you want to add a link from the blog entry to where people can
get the chunk of code that will perform the magic?

The link from the thread takes you to the actual code, and both blog
posts (linked below) link to it as well. Maybe it's not obvious enough?
Or are you talking about a different page?

http://blog.bleything.net/2006/10/21/shell-style-history-for-irb
http://blog.bleything.net/2007/7/30/announcing-shell-style-history-for-irb-the-fixed-edition

Ben

 

[sishen]

Note: parts of this message were removed by the gateway to make it a legal Usenet post.

Cool~,

 

[Tomas Pospisek's Mailing Lists]

The link from the thread takes you to the actual code, and both blog
posts (linked below) link to it as well. Maybe it's not obvious enough?
Or are you talking about a different page?

http://blog.bleything.net/2006/10/21/shell-style-history-for-irb
http://blog.bleything.net/2007/7/30/announcing-shell-style-history-for-irb-the-fixed-edition

Oh, I was coming from the "RubyConf stuff" blog entry which AFAICS doesn't
have a pointer to the code. I didn't verify the other blog entries links
:-o
*t

 

[Ben Bleything]

Oh, I was coming from the "RubyConf stuff" blog entry which AFAICS doesn't
have a pointer to the code. I didn't verify the other blog entries links
:-o

Woops! You're right, and I should fix that. And now I have. Thanks

Ben