DanCardin
DanCardin
**Describe the bug** Either source behaves weirdly in combination with xdist, or the documentation around how source/include work could be improved. When supplying certain source/include values in particular ways with...
I've got bprev and bnext bound with `` mappings which make it pretty easy to chain them together more quickly than the animation can finish. It seems like, depending on...
The idea being that one could define their target handler using some predefined calling convention, and `sauce -t foo` or whatever to execute a specific subcategory of items; where the...
Suggested by someone to me: > I'd like to use it more, but I have a lot of inertia behind .envrc files > What would be awesome is if you...
In particular, if i define some top-level alias `push = git push origin master`, i would ideally like to not **have** to `sauce` to get that, while i may not...
Today autoload=true is essentially equivalent to `sauce` with no args. There's no reason we can't support `autoload-args` (valid globally or locally) as a setting `autoload-args = '--as prod -g 'FOO*'`...
This flag would cause `sauce shell init` to include `--color=never` flag, causing color to be disabled. Use `shell init` to customize behavior to avoid loading config on vanilla `sauce`-type commands...
This would enable one to simply kill the current shell to revert state. Due to lack of any (or at least consistent) support for running shell code on startup of...
I.e. Allow the ability to write ``` [alias.fish] foo = 'bar' ``` Even if, practically, it might be unlikely that someone would want/need cross-shell compatbility, `sauce` can be annoying to...