Various Feature Ideas

[therecluse26]

Hi, I was thinking a bit today about some features that could prove useful to users. I'd be happy to lend a hand in thinking through and building out some of them, if you're interested.

1. The ability to load various commands into "slots" or something similar, i.e. if someone finds themself repeating the same commands over and over, they can instead load them into a slot and then recall it like bh 3 to recall the command in slot 3

2. A listing of my most commonly-entered commands ordered by frequency.

3. A community-driven repo of helpful commands and scripts that users can search through to find help, ideas, etc for their own scripting needs (think like a "marketplace" for lack of a better term, but for shell scripts). This would obviously be the most work, but I think it could be enormously helpful for people. This could also potentially be integrated within #1, where you could select one of these commands and load it into whichever slot you choose.

Let me know what you think!

[simeg]

Hi @therecluse26.

1. How would this be different from defining an alias? alias my-cmd="something I want to run often"
2. This would maybe be interesting for some people. I found this SO post that explains how you can do it for your local history.

I'm not maintaining this project or anything, just my two cents.

[therecluse26]

@simeg In an isolated environment, it's not really all that different, however with this service, you'd have several advantages

1. It'd be transferrable between machines since it's tied to this service
2. With that transferrability, there would also be clarity with what's being run. Running an alias through BashHub's utility currently doesn't expose the underlying command, so if you try to run it on a new machine that doesn't have the alias defined, it'll lead to undesired results

What did you think about the third idea? Any thoughts on it?

[simeg]

@therecluse26 I can't quite figure out what use-case would 1) solve. Someone jumping between machines and can't be bothered to set up their dotfiles, but can be bothered to setup Bashhub?

I like the third idea and I feel like it's a problem that's probably been solved. There are lots of bash resources out there already and some of them live here on github => they are community driven. I guess what makes your idea different is being able to load them directly in to a slot to quickly be able to execute the command/script. Starting to sound like npm for bash commands :)

Personally I would have no use for it simply because it's quick and easy to copy-paste bash code. Also it's scary running unknown bash scripts. I'm also considering if it's outside the scope of bashhub, at least how I see it.

Sorry if I'm sounding negative, just trying to wrap my head around the use-cases!

[exic]

For 3) you might want to check http://cheat.sh/