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 request: configuration files #511
Comments
|
I would like this too. One suggestion would be to adhere to the XDG specification so our Dotfiles don't get so cluttered. With XDG, we could have this instead: NOTE: Doesn't have to be a YAML configuration but can be any configuration format that makes sense. |
|
Here’s a suggested, hypothetical config file, inspired by ui_styles.rs/default_theme.rs:
|
|
nice draft ariasuni. where would the file extension icon fit into this config? maybe |
|
Well a great first step would be to be able to have a configuration file at all. More advanced features, like colors based on file glob/pattern and custom file icons mapping, should probably be handled separately afterwards — e.g. to discuss if things like |
|
Is there currently any way to do this? I always run
Is there a way to set those defaults so I just need to type |
|
It could be a config file supporting simple options at first step, and after that extend to complex options/features. |
|
My workaround before official conf file (with zsh & exa installed by homebrew on macos):
#!/usr/bin/env zsh
args=($@)
opts_file=$HOME/.exarc
[[ -f $opts_file ]] || touch $opts_file
opts=(${(@f)$(<$opts_file)})
/opt/homebrew/bin/exa $opts $args
|
Having to configure exa using a shell alias is less than convenient. ripgrep allows you to set a RIPGREP_CONFIG_PATH environment variable to point to a file that contains a list of default options, one per line (https://github.com/BurntSushi/ripgrep/blob/master/GUIDE.md#configuration-file). I think exa should do this too.
The text was updated successfully, but these errors were encountered: