-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
zsh: adjust initContent priorities #6676
Conversation
(lib.mkIf (cfg.initExtraFirst != "") (mkOrder 550 cfg.initExtraFirst)) | ||
(lib.mkIf (cfg.initExtraFirst != "") (lib.mkBefore cfg.initExtraFirst)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wasn't sure if we wanted an easy migration of prio here so it's just using the mkBefore
prio instead of an arbitrary number.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's fine. We should get rid of it anyway
(lib.mkIf (cfg.initExtra != "") (mkOrder 1200 cfg.initExtra)) | ||
(lib.mkIf (cfg.initExtra != "") cfg.initExtra) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing custom prio here allows migration to be easier for initExtra
to initContent
To support easier migration of deprecating old zsh options. We can adjust the internal priorities to fit within the `mkBefore` (500) and default (1000). Makes it easier for `initExtraFirst` migrationg to `mkBefore` and `initExtra` to default prio.
To support easier migration of deprecating old zsh options. We can adjust the internal priorities to fit within the `mkBefore` (500) and default (1000). Makes it easier for `initExtraFirst` migrationg to `mkBefore` and `initExtra` to default prio.
To support easier migration of deprecating old zsh options. We can adjust the internal priorities to fit within the
mkBefore
(500) and default (1000). Makes it easier forinitExtraFirst
migrationg tomkBefore
andinitExtra
to default prio.Predecessor to #6664
We can iron out the priorities more, just wanted to quickly whip something up to get a discussion going.
Description
Checklist
Change is backwards compatible.
Code formatted with
./format
.Code tested through
nix-shell --pure tests -A run.all
or
nix build --reference-lock-file flake.lock ./tests#test-all
using Flakes.Test cases updated/added. See example.
Commit messages are formatted like
See CONTRIBUTING for more information and recent commit messages for examples.
If this PR adds a new module
Maintainer CC