-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
conf.d load order changed in 3.1.0 release #6593
Comments
Yeah, I can reproduce. The order of globs changed. As a workaround I recommend calling the file |
This is due to 74a22ff discussed in #5634 (comment) |
I'm not sure that the order of globs is guaranteed anywhere, though I agree that it's a bit obnoxious for it to change. |
I feel like the glob order should be uncoupled from the file completion order. |
Yeah, I've now reverted the changes to glob ordering since 3.1, but only to glob ordering. It's now uncoupled from completion ordering, so we can change that to our heart's content. |
Glob ordering is used in a variety of places, including figuring out conf.d and really needs to be stable. Other ordering, like completions, is really just cosmetic and can change if it makes for a nicer experience. So we uncouple it by copying the wcsfilecmp from 3.0.2, which will return the ordering to what it was in that release. Fixes #6593 (cherry picked from commit f053cd2)
Prior to updating to fish 3.1.0, I was able to predict the load order of files in my
.config/fish/conf.d/
folder. I designed this folder with a___env.fish
file to set some global exported variables that could be shared among configuration files that would load later.Now, after updating to fish 3.1.0, the
__env.fish
file loads last instead of first.The text was updated successfully, but these errors were encountered: