X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=p5sagit%2FDevel-REPL.git;a=blobdiff_plain;f=lib%2FDevel%2FREPL%2FPlugin%2FReadLineHistory.pm;h=bae5df939706537d71bb6eecbd288a6c89b35f0e;hp=61ad9c09ed365a3a26075d08fd6af73ce3c16915;hb=master;hpb=4906ca4e09303a2703c2d0f93d0ea5c46ec900d5 diff --git a/lib/Devel/REPL/Plugin/ReadLineHistory.pm b/lib/Devel/REPL/Plugin/ReadLineHistory.pm index 61ad9c0..bae5df9 100644 --- a/lib/Devel/REPL/Plugin/ReadLineHistory.pm +++ b/lib/Devel/REPL/Plugin/ReadLineHistory.pm @@ -3,14 +3,19 @@ # # epitaph, 22nd April 2007 +use strict; +use warnings; package Devel::REPL::Plugin::ReadLineHistory; +# ABSTRACT: Integrate history with the facilities provided by L + +our $VERSION = '1.003030'; use Devel::REPL::Plugin; -use File::HomeDir; use File::Spec; +use namespace::autoclean; my $hist_file = $ENV{PERLREPL_HISTFILE} || - File::Spec->catfile(File::HomeDir->my_home, '.perlreplhist'); + File::Spec->catfile(($^O eq 'MSWin32' && "$]" < 5.016 ? $ENV{HOME} || $ENV{USERPROFILE} : (<~>)[0]), '.perlreplhist'); # HISTLEN should probably be in a config file to stop people accidentally # truncating their history if they start the program and forget to set @@ -18,28 +23,90 @@ my $hist_file = $ENV{PERLREPL_HISTFILE} || my $hist_len=$ENV{PERLREPL_HISTLEN} || 100; around 'run' => sub { - my $orig=shift; - my ($self, @args)=@_; - if ($self->term->ReadLine eq 'Term::ReadLine::Gnu') { - $self->term->stifle_history($hist_len); - } - if ($self->term->ReadLine eq 'Term::ReadLine::Perl') { - $self->term->Attribs->{MaxHistorySize} = $hist_len; - } - -f($hist_file) && $self->term->ReadHistory($hist_file); - $self->term->Attribs->{do_expand}=1; - $self->$orig(@args); - $self->term->WriteHistory($hist_file) || - $self->print("warning: failed to write history file $hist_file"); + my $orig=shift; + my ($self, @args)=@_; + if ($self->term->ReadLine eq 'Term::ReadLine::Gnu') { + $self->term->stifle_history($hist_len); + } + if ($self->term->ReadLine eq 'Term::ReadLine::Perl') { + $self->term->Attribs->{MaxHistorySize} = $hist_len; + } + if (-f($hist_file)) { + if ($self->term->ReadLine eq 'Term::ReadLine::Gnu') { + $self->term->ReadHistory($hist_file); + } + if ($self->term->ReadLine eq 'Term::ReadLine::Perl') { + open HIST, $hist_file or die "ReadLineHistory: could not open $hist_file: $!\n"; + while (my $line = ) { + chomp $line; + $self->term->addhistory($line); + } + close HIST; + } + } + + $self->term->Attribs->{do_expand}=1; # for Term::ReadLine::Gnu + $self->term->MinLine(2); # don't save one letter commands + + # let History plugin know we have Term::ReadLine support + $self->have_readline_history(1) if $self->can('have_readline_history'); + + + $self->$orig(@args); + + if ($self->term->ReadLine eq 'Term::ReadLine::Gnu') { + $self->term->WriteHistory($hist_file) || + $self->print("warning: failed to write history file $hist_file"); + } + if ($self->term->ReadLine eq 'Term::ReadLine::Perl') { + my @lines = $self->term->GetHistory() if $self->term->can('GetHistory'); + if( open HIST, ">$hist_file" ) { + print HIST join("\n",@lines); + close HIST; + } else { + $self->print("warning: unable to WriteHistory to $hist_file"); + } + } }; 1; __END__ -=head1 NAME +=pod -Devel::REPL::Plugin::ReadLineHistory - Integrate history with the facilities provided by L +=head1 DESCRIPTION -=cut +This plugin enables loading and saving command line history from +a file as well has history expansion of previous commands using +the !-syntax a la bash. + +By default, history expansion is enabled with this plugin when +using L. That means that +"loose" '!' characters will be treated as history events which +may not be what you wish. + +To avoid this, you need to quote the '!' with '\': + my $var = "foo\!"; + +or place the arguments in single quotes---but enable the +C attribute C: + + $_REPL->term->Attribs->{history_quotes_inhibit_expansion} = 1; + my $var = 'foo!'; + +and to disable history expansion from GNU readline/history do + + $_REPL->term->Attribs->{do_expand} = 0; + +=head1 CONFLICTS + +Note that L does not support a history +expansion method. In that case, you may wish to use the +L which provides similar functions. +Work is underway to make use of either L or +L> consistent for expansion with either the +L support or L. + +=cut