Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

RESH: Rich Enhanced Shell History

github.com

Post reply on HN
Print view View original

1–10 of 24 posts

Re: RESH: Rich Enhanced Shell History

#3

Post by smartmic »

The example shows many fields which are stored in the JSON for each command. I wonder how the file size will blow up after some time. Also, how are duplicates handled? Looking at all the details which are kept in context of a command, removing duplicate commands seems not to be an option without loosing the rich context.

Re: RESH: Rich Enhanced Shell History

#4

Post by o_____________o »

smartmic wrote: post #3

The example shows many fields which are stored in the JSON for each command. I wonder how the file size will blow up after some time. Also, how are duplicates handled? Looking at all the details which are kept in context of a command, removing duplicate commands seems not to be an option without loosing the rich context.

Yeah, based on the issues that might be a fair assumption:

https://github.com/curusarn/resh/issues

more expected issues from relying on a big JSON file:

https://github.com/curusarn/resh/issues/171

Re: RESH: Rich Enhanced Shell History

#5

Post by ape4 »

My favorite shell keystroke saver now is tab-completion. Its wonderful that it works for things besides files. eg `systemctl iso` gives 'systemctl isolate`

Its great but it could be even better. For example if there is ambiguity the possible choices are shown but not as a menu.

Re: RESH: Rich Enhanced Shell History

#7

Post by trulyrandom »

pepemon wrote: post #2

Is there something similar available for fish?

I believe fish already does some of these things. For example: if there is no binary available in PATH for one of the commands in your history, that command won't be suggested. Same goes for commands that have file/directory names in them that don't exist.

Re: RESH: Rich Enhanced Shell History

#9

Post by phiresky »

Alternatives (without judgement):

https://github.com/cantino/mcfly

https://github.com/jcsalterego/historian

https://github.com/larkery/zsh-histdb + https://github.com/m42e/zsh-histdb-fzf

https://github.com/ellie/atuin

All of these except the OP (I think) use SQLite databases.

Personally I use zsh-histdb, which is great but only for ZSH. I'm working on adding a rich SQLite history to nushell so I can finally try nu: https://github.com/nushell/reedline/pull/401 .

Post reply on HN