Olivia Kinnear

That makes sense. I wasn't suggesting a separate configuration file (maybe that should be split into a separate PR?), but I feel like it might be worth change the wrappers...

Couldn't shell aliases just be used? That, or any options provided to `tere init` could be inlined in the generated wrapper. I don't believe a configuration file is required for...

Okay, so instead of aliases it could just be part of `tere init`. As an example, running `tere init bash --mouse=on --folders-only` would expand to this (if `tere` was located...

I see your point. If @mgunyho is okay with a configuration file ([TOML](https://toml.io/en/), possibly?) I would be happy to implement that along with the `init` option, although it seems like...

Do we want to split these off into separate issues? Even if both of them get implemented, they can both be implemented in any order, and neither depend on each...

> Yeah you're right the config file doesnt belong here. What I meant to say is that their purpose overlaps, yet one is not as flexible as the other. So...

> Here are some thoughts I have related to the one-liner proposal. > > * `eval "$(tere init bash)"` already assumes that `tere` is globally installed (be it via cargo...

> Admittedly, these are mostly minor edge cases but I still would like to avoid creating them. > > Sorry if I sound like I'm just arguing for the sake...

If this feature is ever implemented, this change should also be made to the shell completions in the `autocomplete/` directory, as right now they are hard coded to `$HOME/.tldrc/tldr/pages/`.

I can submit a pull request with the proposed changes if that would be useful.