xsession: windowManager.command is flawed

[ckiee]

Hello!

I have been on a quest to figure out why my systemd-ified polybars wouldn't launch after my i3's already listening, and after some digging and rediscovery of the undocumented NixOS display-manager.service->home-manager handoff process (#2205 would be nice, but: this, this, and finally this)

I would now like i3 to use its sd-notify integration here, so I can wait on it like this person, but for my polybars. Maybe also upstream that.

Description

We use this accursed xsession.windowManager.command thing in bspwm, i3/sway, xmonad, awesome, etc.. I would like it if we had a window-manager.service user unit. That'd be healthy. Maybe even a window-manager.target and i3wm/….service, that person from earlier has that, and I am intrigued by the Alias.

Things to do that I probably don't have time for

• [ ] Consider upstreaming my individually-systemdified polybars
• [ ] Remove xsession.windowManager.command
• [x] Get a version of that (MIT-licensed) i3wm.service running in home-manager: here.

I tried to work-around this for a while but there are too many constraints. (sorry for that 1/2 patch, unrelated)

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

[ckiee]

Using a stale bot is disrespecting of contributor's time, and this is still relevant.

Read more: https://blog.benwinding.com/github-stale-bots/

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

[ckiee]

Using a stale bot is disrespecting of contributor's time, and this is still relevant.

Read more: blog.benwinding.com/github-stale-bots

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

[ckiee]

Using a stale bot is disrespecting of contributor's time, and this is still relevant. Read more: blog.benwinding.com/github-stale-bots

Still a problem. @rycee would you like to take a look?