• Stars
    star
    103
  • Rank 333,046 (Top 7 %)
  • Language
    Shell
  • License
    MIT License
  • Created almost 6 years ago
  • Updated over 3 years ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

ginh is not a histogram: visually evaluate your shell usage patterns

ginh.sh

Codacy Badge no. no.

ginh is not a histogram

Usage

Usage: `ginh [-h] [-a] [-n entries] [-f hist_file] [-c chart_char] [-l line_len]`

`ginh` generates a bar chart of your most frequently used shell commands,
according to your shell's history file.

Options:
  -a            disable reversing aliases to find the command they reference
  -n NUM        number of entries to include in the chart, default $num_entries
  -f FILE       history file use, default determined by the calling shell
  -c CHAR       character to use for chart bars, default '='
  -l NUM        width of chart, default width of terminal

Miscellaneous:
  -h            display this help message and exit
  -d            print useful debug info

Example:

entries=15, file=/Users/crclark/.bash_history, char==, len=78
-------------------------------------------------------------------------------
      git =================================================================  40
      cat ==================================  21
      vim =========================  15
       ls ====================  12
./ginh.sh ===============  9
       cd ============  7
       mv ==========  6
      sed =========  5
     echo =========  5
       rm =======  4
     find =======  4
  history =====  3
   export ====  2
      env ====  2
 diskutil ====  2
-------------------------------------------------------------------------------

Installation

From source

git clone https://github.com/crclark96/ginh.git
cd ginh
sudo make install

From packages

Debian

Debian packages are available here.

Arch

Install ginh through the Arch User Repositores

Help

if you don't see your graph updating after running a few commands, this is because the working history is stored in memory, and not the history file. running history -a should update the history file and you'll be good to go!