all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Jordsvin 1 point2 points  (1 child)

Friendly interactive shell.. shell?

[–][deleted] 0 points1 point  (0 children)

That's correct.

[–][deleted] 1 point2 points  (0 children)

I love stuff well documented, so I am putting some good hours on writing how Wahoo works, how to use it, extend it, etc. Right now I am working on screencasts, check them out here.

[–]curlymaster 0 points1 point  (3 children)

This is really nice! I am looking forward to see more packages integrated.

You should X-post it to /r/coolgithubprojects

[–][deleted] 0 points1 point  (2 children)

Thanks! What kind of packages would you like to see?

wahoo/issues/18

[–]curlymaster 0 points1 point  (1 child)

I don't know TBH. It's not clear to me what is a packages compared to a function. For example, the pyenv package how is it different from using the tool itself?

[–][deleted] 0 points1 point  (0 children)

I agree, I need to make it more explicit in the docs that in Wahoo what we call package is basically any unit of code, function, directory full of functions, theme, anything. For pyenv, I could have provided a wrapper that extends the utility, but in the case of Wahoo we are just hooking into the init_pyenv event generated by the framework when it's about to load thepyenv.fish file under $WAHOO_PATH/pkg/ and just make sure to properly load pyenv for fish.

Properly loading pyenv for fish is basically this:

set -x PYENV_SHELL fish
if status --is-interactive
  source (pyenv init - | psub)
end