On Sat, 18 Apr 2020 at 22:15, wrote:
> On Saturday, April 18, 2020 07:00:53 AM David wrote:
> > On Sat, 18 Apr 2020 at 20:20, Richard Owlett wrote:
> > > I can see any *ONE* previous commands by using the up-arrow key.
> > > But I need to see the *complete* history. F1 is no "Help".
> > > Obviou
On 18/4/20 10:14 pm, rhkra...@gmail.com wrote:
On Saturday, April 18, 2020 07:00:53 AM David wrote:
On Sat, 18 Apr 2020 at 20:20, Richard Owlett wrote:
I can see any *ONE* previous commands by using the up-arrow key.
But I need to see the *complete* history. F1 is no "Help".
Obviously its stor
On Sat 18 Apr 2020 at 09:31:10 (-0400), songbird wrote:
> David wrote:
> > On Sat, 18 Apr 2020 at 20:20, Richard Owlett wrote:
> >>
> >> I can see any *ONE* previous commands by using the up-arrow key.
> >> But I need to see the *complete* history. F1 is no "Help".
> >> Obviously its stored in a f
David wrote:
> On Sat, 18 Apr 2020 at 20:20, Richard Owlett wrote:
>>
>> I can see any *ONE* previous commands by using the up-arrow key.
>> But I need to see the *complete* history. F1 is no "Help".
>> Obviously its stored in a file. Where?
>
> Reading https://mywiki.wooledge.org/BashFAQ/088 give
t, the oldest are
dropped.
$HISTSIZE is the limit in within a terminal, the default is 500 -- setting it
to a negative number makes it unlimited
$HISTFILESIZE is a limit on the size of the command history file (in lines)
On Saturday, April 18, 2020 07:00:53 AM David wrote:
> On Sat, 18 Apr 2020 at 20:20, Richard Owlett wrote:
> > I can see any *ONE* previous commands by using the up-arrow key.
> > But I need to see the *complete* history. F1 is no "Help".
> > Obviously its stored in a file. Where?
> * so if a use
On Sat, Apr 18, 2020 at 06:52:23AM -0500, Richard Owlett wrote:
[...]
> There's one thing I don't understand - erasure of previous history.
> https://mywiki.wooledge.org/BashFAQ/088 states it as:
> >... it overwrites the existing history with the new version.
That's because it reads the history
On 04/18/2020 05:19 AM, Richard Owlett wrote:
I can see any *ONE* previous commands by using the up-arrow key.
But I need to see the *complete* history. F1 is no "Help".
Obviously its stored in a file. Where?
TIA
Using 'cat ~/.bash_history' gives desired format (i.e. without the line
numbers
On Sat, 18 Apr 2020 at 20:20, Richard Owlett wrote:
>
> I can see any *ONE* previous commands by using the up-arrow key.
> But I need to see the *complete* history. F1 is no "Help".
> Obviously its stored in a file. Where?
Reading https://mywiki.wooledge.org/BashFAQ/088 gives some tips
that might
On 18/04/2020 11:19, Richard Owlett wrote:
I can see any *ONE* previous commands by using the up-arrow key.
But I need to see the *complete* history. F1 is no "Help".
Obviously its stored in a file. Where?
TIA
Well, for Bash, the file is at ~/.bash_history (as set in $HISTFILE),
but, bew
On Sat, 18 Apr, 2020 at 05:19:40 -0500, Richard Owlett wrote:
> I can see any *ONE* previous commands by using the up-arrow key.
> But I need to see the *complete* history. F1 is no "Help".
> Obviously its stored in a file. Where?
> TIA
Use the 'history' command, or 'cat ~/.bash_history'. Assumes
I can see any *ONE* previous commands by using the up-arrow key.
But I need to see the *complete* history. F1 is no "Help".
Obviously its stored in a file. Where?
TIA
purpose i would like to know the command history that has
>> been ran via Web console. does linux provide any option by which i can
>> check the history of commands.
>
> The operating system is simply a framework on which applications run.
> The operating system will not keep
On Wed, May 2, 2012 at 3:21 AM, Muhammad Yousuf Khan wrote:
> Hello everyone,
>
>
> I am using few web front end tools in debian and other destros and for
> learning purpose i would like to know the command history that has
> been ran via Web console. does linux provide any opt
Hello everyone,
I am using few web front end tools in debian and other destros and for
learning purpose i would like to know the command history that has
been ran via Web console. does linux provide any option by which i can
check the history of commands.
Thanks,
MYK
--
To UNSUBSCRIBE
On Thu, Nov 24, 2011 at 10:01:00AM GMT, Sthu Deus wrote:
> Thank You for Your time and answer, Raf:
>
> >> I try to escaping saving double commands in shell command history.
> >
> >The subject is somewhat confusing - escaping in regards to shell
> >usually means s
Thank You for Your time and answer, Raf:
>> I try to escaping saving double commands in shell command history.
>
>The subject is somewhat confusing - escaping in regards to shell
>usually means something else :^)
Ahh. Seems alright to me. :o)
>> HISTCONTROL=ignoreboth
>
On Thu, Nov 24, 2011 at 05:54:27AM GMT, Sthu Deus wrote:
> Good time of the day.
G'day.
> I try to escaping saving double commands in shell command history.
The subject is somewhat confusing - escaping in regards to shell usually
means something else :^)
> env shows amon
Good time of the day.
I try to escaping saving double commands in shell command history.
env shows among other things:
SHELL=/bin/bash
HISTCONTROL=ignoreboth
as I understand, it should be enough to cease saving the already
had commands - but it is not so - the commands are saved still. What
On Thu, 2011-04-28 at 15:13 +0300, Sophoklis Goumas wrote:
> $ pgrep bash
> $ kill
or kill $$
I use that whenever I type/paste a password into my shell in the wrong
sequence :-)
(I actually kill -9 $$ just to be sure :-)
Richard
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian
On Jo, 28 apr 11, 15:13:11, Sophoklis Goumas wrote:
>
> Instead of tampering with your system what would you say on issuing those
> sensitive commands in a new shell and then KILL that shell?
Cool ideea ;)
> For example:
>
> $ echo "This will propably get into .bash_history."
> This will propab
(heh, just realized that my earlier reply didn't go to the list) at any rate,
thank y'all, preceding the command with space does the job just fine.
i'll have to read up on HISTCONTROL and HISTIGNORE. these look pretty
powerful (for my use).
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.d
Hi Shawn,
shawn wilson wrote:
Is there a way to have a command that does not show up in history? Or a
way to pipe a string where the string doesn't show up in history?
Ie, I set some passwords with:
echo "some string and stuff" ¦ sha512sum
(Probably with cut and awk and other such things)
And
On Wed, Apr 27, 2011 at 23:51, Vangelis Katsikaros wrote:
> On 04/28/2011 02:25 AM, Kamaraju S Kusumanchi wrote:
>>
>> shawn wilson wrote:
>>
>>> Is there a way to have a command that does not show up in history? Or a
>>> way to pipe a string where the string doesn't show up in history?
>>>
>>> Ie
On Thu, Apr 28, 2011 at 01:58, shawn wilson wrote:
> ...
>
> And I'd like a way for my system to not store my password scheme. I'd prefer
> something better than editing my history file.
Instead of tampering with your system what would you say on issuing those
sensitive commands in a new shell an
shawn wilson (ag4ve...@gmail.com on 2011-04-27 18:58 -0400):
> Is there a way to have a command that does not show up in history? Or
> a way to pipe a string where the string doesn't show up in history?
see the HISTIGNORE variable in the bash manual, and edit ~/.bashrc
accordingly. Most used is so
> Is there a way to have a command that does not show up in history?
> Or a way to pipe a string where the string doesn't show up in
> history?
>
> Ie, I set some passwords with:
> echo "some string and stuff" | sha512sum
> (Probably with cut and awk and other such things)
Apart from beginning th
On 04/28/2011 02:25 AM, Kamaraju S Kusumanchi wrote:
shawn wilson wrote:
Is there a way to have a command that does not show up in history? Or a
way to pipe a string where the string doesn't show up in history?
Ie, I set some passwords with:
echo "some string and stuff" ¦ sha512sum
(Probably w
shawn wilson wrote:
> Is there a way to have a command that does not show up in history? Or a
> way to pipe a string where the string doesn't show up in history?
>
> Ie, I set some passwords with:
> echo "some string and stuff" ¦ sha512sum
> (Probably with cut and awk and other such things)
>
>
Is there a way to have a command that does not show up in history? Or a way
to pipe a string where the string doesn't show up in history?
Ie, I set some passwords with:
echo "some string and stuff" ¦ sha512sum
(Probably with cut and awk and other such things)
And I'd like a way for my system to n
Hi, the two pkgs only fix the problem while debuging normal perl program. If I want to interactive debug modperl program using Apache::DB then they won't work, ) - :
On 2/10/06, linux china <[EMAIL PROTECTED]> wrote:
Thanks you very much, libterm-readline-perl-perl solved my issue.
On 2/10/06, Joe
Thanks you very much, libterm-readline-perl-perl solved my issue.
On 2/10/06, Joey Hess <[EMAIL PROTECTED]> wrote:
linux china wrote:> I use 'perl -d ' to debug my code, and use up and down arrow to view the> debugger command that I have inputed, but in my Debian
3.1 system, the up arrow> doesn't
linux china wrote:
> I use 'perl -d ' to debug my code, and use up and down arrow to view the
> debugger command that I have inputed, but in my Debian 3.1 system, the up
> arrow
> doesn't function. I don't know why, anyone could help?
Try installing libterm-readline-gnu-perl or libterm-readline-p
hi,
I use 'perl -d ' to debug my code, and use up and down arrow to view the debugger command that I have inputed, but in my Debian 3.1 system, the up arrow doesn't function. I don't know why, anyone could help?
Hi,
Is it correct for VIM to set history to 20 on every :sp command? On :e
the history is not changed. I have 'set hi=150' in /etc/vim/vimrc and
~/.vimrc.
Using:
VIM - Vi IMproved 6.1 (2002 Mar 24, compiled May 4 2002 18:31:09)
Included patches: 1-48
Compiled by Wichert Akkerman <[EMAIL PROTEC
On Sat, 09 Aug 1997 02:22:32 EDT Paul Miller ([EMAIL PROTECTED])
wrote:
> Is there any way to get bash to work like 4dos? -- If you type the first
> couple of characters of a command in history, it will only scroll through
> those commands begining with those characters...
^R aka CTRL-R
man rea
Is there any way to get bash to work like 4dos? -- If you type the first
couple of characters of a command in history, it will only scroll through
those commands begining with those characters...
-Paul
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
37 matches
Mail list logo
