Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Saving first n lines of history Post 303030563 by milhan on Tuesday 12th of February 2019 06:03:35 PM
Old 02-12-2019
in your .bash_profile (or .profile) you could do:
Code:
HISTFILESIZE= 
HISTSIZE=

to make your bash history unlimited; this way they won't be overwritten.
This User Gave Thanks to milhan For This Post:
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Extracting lines and saving - awk

Hi All, I am trying to extract lines bsed on pattern matching../mp straight-flow/ Extracted output should be saved in meta_string , but the code is not working in that manner,saving repeated lines. can anyone please suggest where am i going wrong. /mp straight-flow/ {... (6 Replies)
Discussion started by: madhaviece
6 Replies

2. UNIX for Dummies Questions & Answers

Alternative to saving history

Hi! We have a non-root account in which history is disabled. Is there any other way to save commands that get executed through that account. I don't have root privileges on the system. Please suggest... Thanks, Jack. (1 Reply)
Discussion started by: jacki
1 Replies

3. 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 Replies)
Discussion started by: ahmedamer12
5 Replies

4. UNIX for Advanced & Expert Users

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 Replies)
Discussion started by: linuxadmin
3 Replies

5. UNIX for Dummies Questions & Answers

The history command: See other users command history

Can anyone tell this: If two users are logged into the same server from different locations. Is there a way to see the history command of the other user? I tried the history command, but it is showing me only the commands I used. Thanks in advance for your help. Iamnew2solaris (1 Reply)
Discussion started by: iamnew2solaris
1 Replies

6. UNIX for Dummies Questions & Answers

Help with deleting lines and saving them

I have a directory question where I ask the user which entry he wants to delete... echo "Which entry?" read entry sed '/^'$entry'/d' file This code does in fact delete that particular entry... HOWEVER, when I go to inquire about that same entry, it still populates like it was never... (4 Replies)
Discussion started by: itech4814
4 Replies

7. 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... (1 Reply)
Discussion started by: sriky86
1 Replies

8. 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... (8 Replies)
Discussion started by: Neo
8 Replies
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)
All times are GMT -4. The time now is 01:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy