Our great sponsors
polybar | i3 | |
---|---|---|
279 | 200 | |
13,508 | 9,053 | |
1.2% | 1.7% | |
7.9 | 7.6 | |
10 days ago | 4 days ago | |
C++ | C | |
MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
polybar
-
Is there a way I can tell which exit node I am using from CLI in Linux?
I'd like to just be able to write a short shell script to check if an exit node is in use, and then pipe that output into polybar which I use anyway. The problem is that I can't find an option in the tailscale Linux CLI client that will show me whether I'm using an exit node or not. Is there a way to do this?
-
No monitor specified error
And I follow the step here. https://github.com/polybar/polybar/issues/763
-
Are there any tools to analyse/modify colours directly from a bash script?
I am on Arch Linux and I am using pywal to generate a colour palette from my wallpaper, which I then use throughout my system. In particular, i have a bash script which grabs these colours and uses them for polybar. The problem is that sometimes these colours do not have enough contrast, and the bar is hard to read. Is there any tool that would allow me to check the readability of my colours, and modify them accordingly, directly from my script? If not, how should I be approaching this issue?
- 長年MacだったからWindows試しに買ってみたんだけど
-
Polybar setup on XFCE
Hello, currently I am trying to get polybar setup on XFCE. I was getting an error along the lines of "background_manager: Failed to copy slice of root pixmap" and according to this GitHub issue, the only solution is to try and set the background another way, like using feh. My only issue now is that it seems like feh isn't actually doing anything whenever I use it to set a wallpaper. I believe this could be because of a conflicting system in XFCE that sets the wallpaper, how can I disable XFCE wallpapers?
-
how to make each polybar modules closer to each other
Refer to the "Formatting" section of the polybar wiki" (e.g. things like -padding, -margin, -spacing).
-
Tray module color not working properly (?)
As per the docs https://github.com/polybar/polybar/wiki/Configuration it uses a ARGB convention
-
How do I use polybar with Hyprland?
The short answer is you can't.
- cant find polybar's config.ini
-
[ noob ] Polybar is behind the another windows
There are a few different solutions here, try them out : https://github.com/polybar/polybar/issues/433
i3
-
Show HN: Chrome Reaper
While I believe Memory Saver was a great improvement, it only works if the tab is hidden or the window minimized. I recently learned the required state is not triggered if the tab is open but on another virtual desktop. At least this is the case with many of not all Linux window managers. Some of the many discussion threads on the topic:
https://github.com/i3/i3/issues/4353
-
Firefox 121 defaults to Wayland on Linux
> This is very true, and unfortunately there are very few people working on linux accessibility (including not me! I am part of the problem!).
Accessibility work itself ironically suffers from an accessibility problem. I brought up i3wm above, the issue for that is pretty illuminating: https://github.com/i3/i3/issues/3393
It's not that the devs are saying "this doesn't matter", the devs behind one of the most popular tiling window managers in the X11 ecosystem are saying, "this does matter, but we don't know how to fix it. We don't know what changes we'd need to make to get Orca working."
It's a really fundamental breakdown that's kind of a tragedy because I honestly believe that if accessibility communities were more heavily baked into testing and development in Linux and if this wasn't treated like two separate worlds, it would be better for everyone -- fixing accessibility concerns very often improves interfaces across the board and makes them more powerful.
But... how do you bridge that gap? I don't really know, I tried looking into Orca to see what would need to happen here and bounced off of it pretty hard, it's not a very approachable tech stack and there aren't tutorials or getting started guides. And on the other side of the issue I can preach about needing accessibility input during interface design, but I'm not in a position to give specific advice because I don't use screenreaders or alternate control schemes and I don't know what the biggest problems are.
The people who need to be involved in that process can't get involved because there's a tech barrier in place even for technically inclined people, and because the underlying software locks them out from the start. i3wm isn't ever going to get someone who's intimately familiar with Orca to jump into the conversation because the people who need to use Orca can't use i3wm. So that leaves the people who can address that tech barrier, but they don't know what to do or how to approach the problem because of the lack of involvement and because the communities are isolated from each other. So it's a chicken-and-egg problem and I don't know how to solve it.
-
"We understand" ;)
This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.
-
what machines have you used for development, and what do you prefer?
I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development.
-
The future of /r/i3wm
Even though, we have moved the official i3 support channel to GitHub discussions, i3's biggest community is still on reddit and if things continue like that there is going to be a lot of helpful content on an increasingly closed platform.
- while in i3wm, krita dockers move downwards a bit each time they're spawned - how do I fix this?
- i3wm-like window switching for Windows
-
egui_overlay - A transparent Overlay window where you can only click the "egui parts"
for example, take i3. https://github.com/i3/i3/issues/4478
- How to start on a Linux desktop environment?
-
Machine for pentesting and general use?
For daily usage I really like kubuntu with i3wm, but it takes some configuration and getting used to the shortcuts, but it's well worth it
What are some alternatives?
polybar-themes - A huge collection of polybar themes with different styles, colors and variants.
sway - i3-compatible Wayland compositor
tint2
awesome - awesome window manager
i3blocks-contrib - Official repository for community contributed blocklets
bspwm - A tiling window manager based on binary space partitioning
nerd-fonts - Iconic font aggregator, collection, & patcher. 3,600+ icons, 50+ patched fonts: Hack, Source Code Pro, more. Glyph collections: Font Awesome, Material Design Icons, Octicons, & more
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
conky - Light-weight system monitor for X, Wayland (sort of), and other things, too
xmonad - The core of xmonad, a small but functional ICCCM-compliant tiling window manager
rofi - Rofi: A window switcher, application launcher and dmenu replacement
tmux - tmux source code