Skip to content

Latest commit

 

History

History
76 lines (62 loc) · 1.95 KB

README.md

File metadata and controls

76 lines (62 loc) · 1.95 KB

historian

Build Status

What's this?

If you are connected to servers with more than one session, you can run into some problems with your bash-history. This project seeks to offer a solution for this problem.

What's to do?

First of all you should edit your .bashrc and add the following to the botton:

export PROMPT_COMMAND='history 1 | cut -c 8- | historian save'

Or if you use zshell, edit .zshrc and add this to the bottom:

export PROMPT_COMMAND='history | tail -n 1 | cut -c 8- | historian save'
precmd() {eval "$PROMPT_COMMAND"}

Historian writes your commands into an sqlite db. With historian you can search for commands and the searched term will be highlighted if it was found.

Usage

Basic:

usage: historian [<flags>] <command> [<args> ...]

I store your history and search it for you

Flags:
  --help  Show context-sensitive help (also try --help-long and --help-man).

Commands:
  help [<command>...]
    Show help.

  save
    Save a command

  search [<criteria>...]
    search for a command

  integrate
    integrate the old historian version into your database

How to install?

Just download the file and put it somewhere where your $PATH points to. e.g.: /usr/bin

Add a config?

You can add a config in ~/.config/historian/config.yml. The colors are being edited with it.

datecolor: lightgreen
searchcolor: lightblue
secret: true
dateformat: 2006.01.02:15:04:05

The secret parameter lets you enter a command with a space in front of the command and it won't be saved in the database.

Available colors are:

  • lightblue
  • lightgreen
  • lightred
  • lightcyan
  • lightmagenta
  • lightyellow
  • lightgray
  • blue
  • green
  • red
  • cyan
  • magenta
  • yellow

About

Please keep in mind that this is software isn't finished and there can be bugs. If anyone has ideas to extend this project, you are welcome to tell me.