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

Support setting a path for the .jjconfig.toml file through the JJ_CONFIG env var #5001

Open
poliorcetics opened this issue Feb 5, 2024 · 4 comments

Comments

@poliorcetics
Copy link
Contributor

Description

jujutsu default config file location is ~/.jjconfig.toml.

This location is configurable via the JJ_CONFIG env var.

It would be nice for programs.jujutsu to support it. Some other programs already allow overriding their config file path that way.

Thanks!

@SrEstegosaurio
Copy link

SrEstegosaurio commented Feb 26, 2024

Also, shouldn't it be placed by default under $XDG_CONFIG_HOME?

Related:
martinvonz/jj#84

@poliorcetics
Copy link
Contributor Author

Ah, martinvonz/jj#85 uses dirs, its choices are often questioned on macOS (see dirs-dev/directories-rs#47 for the longest discussion) :/ that's sad. Still, it will work on Linux at the very least

Copy link

stale bot commented May 31, 2024

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

  • If this is resolved, please consider closing it so that the maintainers know not to focus on this.
  • If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
  • If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

  • If you are also experiencing this issue, please add details of your situation to help with the debugging process.
  • If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

@stale stale bot added the status: stale label May 31, 2024
@SrEstegosaurio
Copy link

Still relevant to me.

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

No branches or pull requests

5 participants