Skip to content
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

Feature suggestion: Introduce environment variable TABTAB_AUTO_PATH #39

Open
yeonghoey opened this issue Mar 23, 2018 · 3 comments
Open

Comments

@yeonghoey
Copy link

TL;DR

How about providing TABTAB_AUTO_PATH option as an environment variable?
When it's defined, --auto installs/uninstalls its generated content into $TABTAB_AUTO_PATH.

Long Story

I usually use zsh but also use bash in times and manage them under a git repo.
They only contain common settings and I put all the other local system dependent settings into ~/.localrc.

As a result, my .bashrc and .zshrc both have following lines:

if [[ -f "$HOME/.localrc" ]]; then
  source "$HOME/.localrc"
fi

(It seems, as a matter of fact, that people who maintain their own dotfiles repos use patterns like this.)

Accordingly, I hope that every time I install some node packages which use tabtab, I want tabtab generated contents to be placed in .localrc.

@mklabs
Copy link
Owner

mklabs commented Apr 19, 2018

That's definitely something we can do. I like the idea.

Would you like to give it a try ? I would be more than happy to merge a PR implementing this. I can guide you through. I unfortunately don't have the time atm to work on this.

I'll eventually implement something similar, thanks for the feedback 👍

@yeonghoey
Copy link
Author

It's a good thing you like the idea. But, currently I don't have any practical node.js experience, and even though I think this thing is an excellent opportunity for getting some, I think I cannot afford to work on it by now. I'll update here when I get some free time to work on this.

@mklabs
Copy link
Owner

mklabs commented May 29, 2018

No worries. I'll do my best to try remedy the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants