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

Don't create window with polybar -s #1314

Closed
eadwu opened this issue Jul 14, 2018 · 6 comments
Closed

Don't create window with polybar -s #1314

eadwu opened this issue Jul 14, 2018 · 6 comments

Comments

@eadwu
Copy link

eadwu commented Jul 14, 2018

Is there any way I can remove the empty window or maybe set monitor to null? Trying to get the output onto xsetroot -name for dwm. Besides the window, polybar adds %{r} to the beginning and module/alsa outputs %{A1:volmute: A4:volup: A6:voldown:} ... %{A A A} which isn't really desired for the statusbar (or at least for me). For the text, manipulating it with sed and cut is working fine though the window is the problem.

Looks like polybar -s does its intended behavior as it only says it won't draw it to the window. So my question is better worded as is there a way to prevent the window from being created while using polybar -s.

@eadwu eadwu changed the title polybar -s still creates window while outputting to stdout Don't create window with polybar -s Jul 16, 2018
@NBonaparte
Copy link
Member

There isn't a way to do that right now.

Just curious, why are you using polybar as a text output rather than a complete bar?

@eadwu
Copy link
Author

eadwu commented Jul 18, 2018

Since dwmstatus reads from stdout while I don't seem be able to get xworkspaces to work.

@NBonaparte
Copy link
Member

Does this help? 6d93437

@eadwu
Copy link
Author

eadwu commented Jul 19, 2018

Sorry for the late response, the commit does stop the window from being created but at the same time, nothing is being outputted to stdout (https://imgur.com/t6uj8vB). The vim command was just to add a value to monitor for whatever reason I thought it would allow it to output, which it of course didn't.

@NBonaparte
Copy link
Member

This should work now: 757545f

@eadwu
Copy link
Author

eadwu commented Jul 19, 2018

Just tested it and it works, thanks! I'll leave this open until the pull request is merged.

patrick96 pushed a commit to patrick96/polybar that referenced this issue Jul 24, 2018
patrick96 pushed a commit to patrick96/polybar that referenced this issue Jul 25, 2018
patrick96 added a commit to patrick96/polybar that referenced this issue Jul 28, 2018
Changelog

Fixes:
* fix(ramp): Evenly distribute states (polybar#1340), see polybar#1328
* fix(i3): Play nice with workspace_auto_back_and_forth (polybar#1312)
* fix(controller): don't draw window if writing to stdout (polybar#1322), see polybar#1314
patrick96 added a commit that referenced this issue Jul 30, 2018
Changelog

Fixes:
* fix(ramp): Evenly distribute states (#1340), see #1328
* fix(i3): Play nice with workspace_auto_back_and_forth (#1312)
* fix(controller): don't draw window if writing to stdout (#1322), see #1314
patrick96 added a commit that referenced this issue Jul 30, 2018
Changelog

Fixes:
* fix(ramp): Evenly distribute states (#1340), see #1328
* fix(i3): Play nice with workspace_auto_back_and_forth (#1312)
* fix(controller): don't draw window if writing to stdout (#1322), see #1314
eadwu added a commit to eadwu/dotfiles that referenced this issue May 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants