-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request] Make the local settings dir(s) configurable? #10
Comments
Hey @absolutejam , thanks for the feedback I totally miss your suggestion. Sorry for the late reply. Current implementation regularly checks a single git repository which is tldr-pages official repo. I guess your current suggestion will add a little bit complexity to the code. That is what I try to avoid. However, I am thinking a workaround; you can manually add those files to the repo and if they won't conflict with repo files, it will work as you expected. Still, this issue can stay opened so that we can hear others thoughts. |
for a simple workaround maybe make the upstream repo configurable. then the user could make/add their own snippets, but it would be on them to maintain sync with tldr master. i've got half an idea for managing multiple data dirs while (hopefully) keeping complexity down i might play with. |
I would like something like this (but maybe depend on an ENV variable to set the location for the clone) This would cover the original-bug intent (TLDR_DATA=/personal tldr special_command vs. TLDR_DATA=/global tldr regular_command) |
Hey, great work on this version of a tldr client 👍
I've recently started using tldr quite a lot, but I also have my own collection of markdown snippets which I've typically accessed via. vim in the past. It would be really be nice if I could consolidate them into tldr.
Is there any possibility of either a way to override the config directory and/or add another directory to index, so tldr could scan both the canonical resource and my own folder(s)? That way I could use my own snippets - some of which can't be contributed upstream to tldr - using the same tool.
For example, functionality like the following to override and use only my own resources, would be awesome.
Cheers,
James.
The text was updated successfully, but these errors were encountered: