Bug #48459 for Devel-REPL: ReadLineHistory plugin causes annoying interpretation of !

Wed Aug 05 14:18:10 2009 spang [...] mit.edu - Ticket created

Subject:

ReadLineHistory plugin causes annoying interpretation of !

When I enable the ReadLineHistory plugin (using Term::ReadLine::Gnu), it causes ! to be interpreted in a shell-like manner, which essentially makes it so that I cannot use the ! character. Disabling the plugin makes this behaviour go away. Here's an example of what happens: Show quoted text

> my $var = "foo!";

!";: event not found Show quoted text

> my $var = '!!!';

!';: event not found I've tried this using 1.003006 (Debian package) and 1.003007 (from CPAN) on Debian GNU/Linux (unstable). Thanks for Devel::REPL!

Wed May 12 22:44:12 2010 chm [...] cpan.org - Correspondence added

Are you sure this is from the ReadLineHistory plugin? I think the !-expansion is from the History plugin. At any rate, in double quotes you can escape the special meaning of the ! by back-slashing it: Show quoted text

> my $var = "foo\!";

foo! This doesn't work for the single quoted string but if you replace the single quotes by double quotes there it will work too: ? my $var = "\!\!\!"; !!! --Chris On Wed Aug 05 14:18:10 2009, spang wrote: Show quoted text

> When I enable the ReadLineHistory plugin (using Term::ReadLine::Gnu), it > causes ! to be interpreted in a shell-like manner, which essentially > makes it so that I cannot use the ! character. Disabling the plugin > makes this behaviour go away. > > Here's an example of what happens: >

> > my $var = "foo!";

> !";: event not found >

> > my $var = '!!!';

> !';: event not found

Wed May 12 22:44:15 2010 The RT System itself - Status changed from 'new' to 'open'

Tue Jun 01 12:34:41 2010 chm [...] cpan.org - Correspondence added

The 'event not found' message is actually from the GNU history library which is actually doing history expansion on its own. See the GNU History library manual for details. Two suggested work arounds: (1) escape the history character with \, e.g. "foo\!" (2) use Term::ReadLine::Perl which does not do history expansion (instead of Term::ReadLine::Gnu which does). You'll need to be using Devel::REPL version 1.003010 or higher. --Chris On Wed Aug 05 14:18:10 2009, spang wrote: Show quoted text

> > When I enable the ReadLineHistory plugin (using Term::ReadLine::Gnu), > it causes ! to be interpreted in a shell-like manner, which > essentially makes it so that I cannot use the ! character. > Disabling the plugin makes this behaviour go away. > > Here's an example of what happens: >

> > my $var = "foo!";

> !";: event not found >

> > my $var = '!!!';

> !';: event not found > > I've tried this using 1.003006 (Debian package) and 1.003007 > (from CPAN) on Debian GNU/Linux (unstable). > > Thanks for Devel::REPL!

Tue Jun 01 12:43:56 2010 chm [...] cpan.org - Correspondence added

TO DO: document this in the Devel::REPL::Plugin::ReadLineHistory documentation as to how to quote history characters (a la bash) or how to configure to use Term::ReadLine::Perl with Devel::REPL. On Tue Jun 01 12:34:41 2010, CHM wrote: Show quoted text

> > Two suggested work arounds: > > (1) escape the history character with \, e.g. "foo\!" > > (2) use Term::ReadLine::Perl which does not do history > expansion (instead of Term::ReadLine::Gnu which does). > You'll need to be using Devel::REPL version 1.003010 > or higher.

Wed Jun 02 08:08:28 2010 chm [...] cpan.org - Correspondence added

I've confirmed that this is the GNU readline/history doing the expansion. If you wish to disable history expansion, just set $_REPL->term->Attribs->{do_expand} = 0; or use quotes to avoid the expansion as below. Using Term::ReadLine::Perl also will not do the expansion. Show quoted text

> On Tue Jun 01 12:34:41 2010, CHM wrote:

> > > > Two suggested work arounds: > > > > (1) escape the history character with \, e.g. "foo\!" > > > > (2) use Term::ReadLine::Perl which does not do history > > expansion (instead of Term::ReadLine::Gnu which does). > > You'll need to be using Devel::REPL version 1.003010 > > or higher.

Thu Jun 03 23:32:55 2010 frioux [...] gmail.com - Status changed from 'open' to 'resolved'