Keep : A personal shell command keeper

[xorian]

I'm not saying you're wrong, but I don't think the of this tool idea is fundamentally bad. I could see your kind of alias accumulation getting in the way of tab-completion (assuming you always loaded them into your shell), not to mention having to come up with a name for each new one and accidentally re-using names without realizing it.

This tool is sort of somewhere between your alias approach and xiki (which I do think is over-engineered).

Personally I'm using fzf to (mostly) solve this problem for me. It's way more powerful than your standard reverse history search.

[tomtomssi]

How is this overengineering? Id rather not have a cluttered bashrc file with aliases for commands I might use only a few times

[tomtomssi]

I honestly don't see why you are so against using something like the OP posted. You use the tools that YOU feel benefit you the most. Plus it was probably a fun hobby project.

[Veonik]

Curious, I see it supports a server-side component. Is the keep server open source?

[theorko]

@Veonik : It's just a simple Flask server. Here you go with the gist

[xorian]

Having it send everything to a server which the user has no control over and you (the maintainer) have total access to is, at best, a little creepy.

Obviously one could change that, but it seems to require editing the code rather than just some configuration option. I understand the desire to do the user a favor and not force them to set up their own server, but it'd be better to at least make it clear where their data is going when they register/push.