-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Allow setting environment variable with path to config file #375
Comments
Thank you for your feedback. I think it is a good idea to support this. Another question is if we want to set the default path on Mac OS to |
I'd love to help with this is it already being worked? |
@deg4uss3r I don't think so. |
Great! @sharkdp do you think just adding in logic to |
Closed via #380 by @deg4uss3r. |
This is now available in bat 0.9. |
I hope this isn't rude to comment on a closed issue, but since the question was asked recently I figured it'd be ok to offer my 2¢ in response. I just updated Homebrew, which pulled down bat 0.9, so I checked the release notes and found that italics went away. I read the background issues to learn the rationale and then went to set up a bat config file, and was surprised to learn that the config file is in I understand the rationale and that the behavior is inherited from an underlying library. FWIW there is no other command line tool I use that stores its config there. As a programmer I expect any command line tool to use the XDG standard location (or less-preferred, |
I think we should change the default path on Mac OS, see #419 |
#338 added support for a config file. On mac (at least my machine), it's saved to
$HOME/Library/Preferences/bat/config
. I'd love for there to be an environment variable named e.g.$BAT_CONFIG_PATH
that allowed me to define a custom path. My use case is that I like to keep config in$HOME/.config
as I check it into VCS.This would also match e.g. ripgrep: https://github.com/BurntSushi/ripgrep/blob/fb622666206089cf7092ae116612898ac358c91c/GUIDE.md#configuration-file (although they only support a path as env variable, no defaults)
The text was updated successfully, but these errors were encountered: