On 7 November 2013 16:50, Stuart Ward wrote:
>
> On 7 November 2013 10:40, Alan Pope wrote:
>
>> awk '{print $1}' ~/.bash_history | sort | uniq -c
>> | sort -rn | head
>>
>
> ~$ awk '{print $1}' ~/.bash_history | sort | uniq -c | sort -rn | head
> 75 git
> 74 cd
> 57 sudo
> 3
On 7 November 2013 10:40, Alan Pope wrote:
> awk '{print $1}' ~/.bash_history | sort | uniq -c
> | sort -rn | head
>
~$ awk '{print $1}' ~/.bash_history | sort | uniq -c | sort -rn | head
75 git
74 cd
57 sudo
39 tail
37 ls
33 dig
20 man
13 python
13 c
The ranger CLI file manager is awesome too if your familiar with
vi/vim. I use it a lot for getting to where I need to be. S is your
friend (puts you in a shell in the directory you have selected in
ranger).
On 7 Nov 2013, at 15:09, Liam Proven wrote:
> On 7 November 2013 10:40, Alan Pope wrot
On 7 November 2013 10:40, Alan Pope wrote:
> Indeed, I type "ls" and "cd" way more than I should :)
Way back in the mists of ancient time, when I used to maintain just
half a dozen Unix boxes ever, I aliased just the bare command "l" -
lower-case L - to "ls -lah".
That saved me a /lot/ of keyst
On 6 November 2013 20:23, Alan Jenkins wrote:
> There is no problem with keeping a lengthy history per se, just
> sometimes those commands are often variations on the same thing
>
Indeed, I type "ls" and "cd" way more than I should :)
alan@deep-thought:~$ awk '{print $1}' ~/.bash_history | sort
On 06/11/13 20:23, Alan Jenkins wrote:
There is no problem with keeping a lengthy history per se, just
sometimes those commands are often variations on the same thing in
which case you may be better off creating scripts and aliases to save
yourself time and effort. Always seek quicker and easier
There is no problem with keeping a lengthy history per se, just
sometimes those commands are often variations on the same thing in
which case you may be better off creating scripts and aliases to save
yourself time and effort. Always seek quicker and easier ways to do
things as it makes your life e
Alan Jenkins wrote:
> Shell scripts and aliases are the way to go for common commands. What on
> earth are you using more than a 1000 commands in your history for? I
> recommend making yourself aliases and scripts for your most used commands
> which you should be able to discern from your history f
Shell scripts and aliases are the way to go for common commands. What on
earth are you using more than a 1000 commands in your history for? I
recommend making yourself aliases and scripts for your most used commands
which you should be able to discern from your history file.
On 5 Nov 2013, at 17:3
On 5 November 2013 17:18, Steven Roberts wrote:
> I just discovered that, as a default, only the last 1000 commands are
> stored in the bash history file. Pretty horrified! A quick bit of googling
> gave me the fix to increase the limit etc.
>
> Not sure if this is just Ubuntu or linux in general
I just discovered that, as a default, only the last 1000 commands are
stored in the bash history file. Pretty horrified! A quick bit of googling
gave me the fix to increase the limit etc.
Not sure if this is just Ubuntu or linux in general.
If you're into the command line 1000 commands don't cov
11 matches
Mail list logo
