pawamoy/shell-history

Charts ideas

pawamoy opened this issue · 2 comments

pawamoy commented

Post your ideas here!

Reminder of the available fields for analysis:

  • start: command start time
  • stop: command stop time
  • duration: duration of the command
  • uuid: session id, shared with subshells
  • parents: process parents, newline-separated commands, something like: 
    /bin/bash
/usr/bin/python /usr/bin/x-terminal-emulator
sh -c x-terminal-emulator
tint2 -c /home/pawamoy/.config/tint2/tint2rc
/sbin/init
  • host: hostname
  • user: username
  • tty: something like /dev/pts/0 or /dev/tty1
  • path: command working directory
  • shell: shell used (/bin/bash, /bin/zsh, etc.)
  • level: shell level (usually 2 in a GUI, 1 in a Ctrl-Alt-F1/6 TTY)
  • type: command type (builtin, alias, function, file, keyword, none)
  • code: command return code
  • cmd: the command itself

Boost priority

  • Boost priority in our backlog through Polar.sh. Higher pledge, higher priority.
  • Minimum pledge by user/organization is $5, minimum amount for boost is $30.
  • View all issues with pledges.
  • We receive the funds once the issue is completed and confirmed by you.
  • Features with the insiders label are released to sponsors first, and tied to a funding goal.
Fund with Polar
pawamoy commented

Usage of builtins, aliases, functions, GNU tools. Maybe it would require a new field to be added to history, because we might not be able to determine afterwards the type of the command. We would add a type field whose contents are the result of type -t for Bash and type -w for Zsh.

EDIT: done

pawamoy commented