Skip to content
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

i3bar: No tray with `tray_output primary` when there is no primary output #1144

i3bot opened this Issue Dec 30, 2013 · 2 comments


None yet
2 participants
Copy link

i3bot commented Dec 30, 2013

[Originally reported by i3-new-ticket]
(Since commit cce3c80, using the tray_output primary directive when no output is set as primary means that no tray will be created. There is a fallback for this situation (to the first available output) when handling client messages, so I assume that this is not the intended behavior, but that fallback seems to be rendered ineffective since no trays are even initialized.


This comment has been minimized.

Copy link

i3bot commented Dec 30, 2013

[Original comment by TonyC]

The system tray with multiple bar configs is not completely supported right now, but when it is, that fallback will be changed.

The rationale for this change was to make configuring multiple bars easier. So if I have two bar configs with different output directives and identical tray_output directives, only the correct tray_output directive will initialize a tray.

I think this behavior is more consistent and easier to understand than the old behavior. The new behavior is:

If the bar is not on the tray output specified, do not initialize a tray.

The old behavior makes a special exception to this rule in the case of the primary monitor, where it chooses a sensible default.

It makes the manual a little shorter.

But that's just my opinion ¯_(ツ)_/¯


This comment has been minimized.

Copy link

i3bot commented Dec 31, 2013

[Original comment by anonymous]

Sure, that makes sense. I don't have a strong opinion on this. It's just that I had seen two people on IRC who were confused that their tray was gone in 4.7 and from the code, it looked like that might have been an unintended consequence. If you want to be more strict about primary outputs, I don't mind.

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.