-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
programs.sway: always wrap the provided package #4039
base: master
Are you sure you want to change the base?
Conversation
@@ -335,7 +328,7 @@ in { | |||
|
|||
package = mkOption { | |||
type = with types; nullOr package; | |||
default = defaultSwayPackage; | |||
default = pkgs.sway; | |||
defaultText = literalExpression "${pkgs.sway}"; |
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.
While you're at it
defaultText = literalExpression "${pkgs.sway}"; | |
defaultText = literalExpression "pkgs.sway"; |
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've used swayfx
to show something different than the default.
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.
also it should have been sway-unwrapped anyway
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.
The defaultText
should show what the default
value is. Use example
for an example.
3fb5f15
to
9d893bb
Compare
so I lost a few minutes before discovering the tests ran with a mock/stub "sway". It's pretty smart but the module needs to override sway which broke with the stub. It was simpler to remove the stub so that's what I have done. My changes to the tests fixed |
b4c40d1
to
3dd6e0f
Compare
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
this requires some changes tin nixpkgs to work, so I will try to merge NixOS/nixpkgs#237044 first |
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
when swapping the default package with another (e.g., "swayfx") we lose all kinds of HM properties like the session variable / extra options etc for no reason. It's inconsistent with how the neovim module behaves too. If someone wants to bypass the HM wrapping, it's still possible to wrap the package with a function .
it's easier to use overrideAttrs than override IMO, and for the home-manager module I would like to be able to configure sway forks the same way as the original sway which is not possible currently see nix-community/home-manager#4039
Thank you for your contribution! I marked this pull request as stale due to inactivity. Please read the relevant sections below before commenting. If you are the original author of the PR
If you are not the original author of the PR
|
Thank you for your contribution! I marked this pull request as stale due to inactivity. Please read the relevant sections below before commenting. If you are the original author of the PR
If you are not the original author of the PR
|
The sway-stubs.nix file contains Does this change mean that the CI will download Sway and its dependencies? |
when swapping the sway package with another (e.g., "swayfx") we lose HM's wrapping like session variables, command line arguments etc for no reason. It's inconsistent with how the neovim module behaves too.
If someone wants to bypass the HM wrapping, it's still possible to wrap the package with a function .
Description
Checklist
Change is backwards compatible.
Code formatted with
./format
.Code tested through
nix-shell --pure tests -A run.all
ornix develop --ignore-environment .#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