-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
sway: Various improvements (package, module, and documentation) #121925
base: master
Are you sure you want to change the base?
Conversation
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.
Added some quick notes (reasons for changes and things that might require a discussion).
@@ -87,20 +89,35 @@ in { | |||
type = with types; listOf package; | |||
default = with pkgs; [ | |||
swaylock swayidle alacritty dmenu | |||
rxvt-unicode # For backward compatibility (old default terminal) |
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.
Not sure if that requires a release notes entry. It's likely annoying if starting a terminal doesn't work anymore but Sway users will hopefully be skilled enough by figuring this out quickly (e.g. resorting to dmenu
).
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.
Maybe we could add a wrapper that launchers alacritty but displays a warning?
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 thought about that but not sure if it's a good idea / if a nice implementation is possible (would have to be a graphical warning and then it get's hacky quickly). Do you have something concrete in mind?
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.
You could display a warning in the shell itself: alacritty -e sh -c 'echo WARN; exec $SHELL'
I don't know exactly how you'd make sure the real rxvt-unicode
overrides this fake rxvt-unicode.
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.
You could display a warning in the shell itself:
alacritty -e sh -c 'echo WARN; exec $SHELL'
That looks and sound super hacky to me (haven't tried if it even works or if exec $SHELL
resets the output).
Users could be very confused by this.
And, while I haven't thought about that yet, launching Alacritty for users that expect rxvt-unicode also sounds wrong.
Anyway, if someone ACKs that I'd be ok with that but to me it doesn't really sound like a good idea (the intentions are good but I feel like I'd be super confused).
I don't know exactly how you'd make sure the real rxvt-unicode overrides this fake rxvt-unicode.
There's the lowPrio
function ( meta.priority
) that should be able to handle that.
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.
Please no, wofi
on nixpkgs master segfaults when I run it.
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.
Great, can you get a backtrace and open an issue?
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.
Either way we should add a release notes entry, so people will not be too surprised about this.
How does #127927 look?
Also, wouldn't it be sensible to go with wofi until we have wmenu?
Our programs.sway.extraPackages
is "unopinionated", we're simply sticking to the upstream defaults (i.e. Drew's opinion / default configuration). dmenu certainly isn't ideal but is seems like there's still no good enough replacement for it: swaywm/sway#5112
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.
Great, can you get a backtrace and open an issue?
The opposite of great. I was under the impression that we don't push broken packages to solicit bug reports.
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.
Great(, that this problem is so reproducible for you), it would probably help you and others if we could report this issue upstream, hopefully with a backtrace (coredumpctl debug
).
nixos/modules/programs/sway.nix
Outdated
# To run Qt5 applications natively on Wayland: | ||
qt5.qtwayland | ||
# Status bars: | ||
i3status i3status-rust waybar | ||
# Notification daemon: | ||
mako | ||
# Screenshots | ||
grim slurp sway-contrib.grimshot | ||
# dmenu replacements: | ||
bemenu rofi | ||
# Redshift | ||
gammastep wlsunset | ||
# Alternative terminals: | ||
foot termite | ||
# Backlight management: | ||
brightnessctl light |
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 guess it's highly debatable what to include here :o We could also leave this empty and maybe install qt5.qtwayland
by 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.
It's just an example I guess, so don't think this is controversial in any way.
FYI, |
@ehmry thanks, that's good to know. I plan on dropping Anyway, if |
Maybe it will build again for awhile, but I'm wary of my system depending on anything written in rust. |
This was done only for backward compatibility and is not required by the default configuration anymore. Unfortunately this might be a breaking change for some users.
f65815a
to
dd97746
Compare
I marked this as stale due to inactivity. → More info |
Motivation for this change
Feedback is welcome but unfortunately I don't have that much time for this so concrete changes / actionable feedback would be ideal/preferred (discussions are fine too - I'd just like to avoid updating commits multiple times). It might also make sense to split this into individual PRs but let's see first if there's a need for that.
Note: This isn't tested yet - it's basically an RFC.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)