Looking for resource on setting up history callback for shells

9 More Discussions You Might Find Interesting

1. What is on Your Mind?

The Great History of UNIX (1969-1999) | 30 Years of UNIX History | YouTube Video

I am pleased to announce this new video in 1080 HD for UNIX lovers honoring thirty years of UNIX history spanning from 1969 to 1999 presented in 150 seconds (two and a half minutes) in 1080 HD, celebrating the 50th anniversary of UNIX. The Great History of UNIX (1969-1999) | 30 Years of UNIX...

2. UNIX for Dummies Questions & Answers

History to Another file [local user history , but root access]

Hi all, My need is : 1. To know who , when , which command used. 2. Local user should not delete this information. I mean , with an example , i can say i have a user user1 i need to give all the following permissions to user1, : a. A specific directory other than his home...

3. UNIX for Advanced & Expert Users

History to Another file [local user history , but root access]

4. UNIX for Dummies Questions & Answers

How to review the history and the commands that has been done in this history?

Hello every body, Kindly inform me How Do i find out the time I executed a command previously on UNIX Solaris?? To be more specific and more clear about what i want to know is that I want a command the enables me to know the history and which command i run at this history/time. FYI I used...

5. Shell Programming and Scripting

Setting Up the Command History Counter

Hey there, I would like to set the bash command history counter to start from, say 101, instead of 1 (assuming the history was cleared with the 'unset HISTFILE' in .bashrc)? For instance, if setting PS1 as PS1='\! ' this would start counting from either 1 or the last number of the command...

6. UNIX for Dummies Questions & Answers

PATH Setting for all shells of a user

How can I modify the path variable of a particular user in all shells? I searched in this forum and as per the advice in some threads created a new file .profile in $HOME directory with the new PATH, but it did not work.

7. IP Networking

Connect to RAS callback server: route problem

I'm trying to use my Gentoo Linux home workstation for connecting to a Windows RAS callback server through analogic telephone line (PSTN). I'm using pppd and successfully configured pppd's options and chat files, both for the outgoing call and for receiving the incoming callback. All seems going...

8. UNIX for Dummies Questions & Answers

setting command history

Hi all is there anyway to setup AIX to get previous command like in dos with up and down arrow thanks

9. Cybersecurity

J need help to make callback by Modem (AIX)

Are there any of you who have a description which can help me to make a callback on AIX. My user�s call in by a telefonnumber at I want AIX to disconnect the line and make a callback to the user who had logged on AIX. The advantage of this is we have security on who we allow to call our...

LEARN ABOUT DEBIAN

devel::repl::plugin::readlinehistory

Devel::REPL::Plugin::ReadLineHistory(3pm)		User Contributed Perl Documentation		 Devel::REPL::Plugin::ReadLineHistory(3pm)

NAME

       Devel::REPL::Plugin::ReadLineHistory - Integrate history with the facilities provided by Term::ReadLine

DESCRIPTION

       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 Term::ReadLine::Gnu. 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 "Term::ReadLine" attribute "history_quotes_inhibit_expansion":

	 $_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;

CONFLICTS

       Note that Term::ReadLine::Perl does not support a history expansion method.  In that case, you may wish to use the Devel::REPL History
       plugin which provides similar functions.  Work is underway to make use of either History or ReadLineHistory consistent for expansion with
       either the Term::ReadLine::Gnu support or Term::ReadLine::Perl.

perl v5.14.2							    2010-06-13				 Devel::REPL::Plugin::ReadLineHistory(3pm)

UNIX for Advanced & Expert Users