I went very minimalist a few months ago, as I found out that ricing (while fun) can be very distracting. My bar (py3status) today only has 2 'modules': the workspace numbers (to know where I am) and the date/time (to know when I am...?). On my laptop, I connect to the Internet through cli, so no need for the network applet. Volume and battery indication is through dunst. For those apps that need it, a tray is enabled but it is invisible when not in use. (Also got rid of my i3 gaps so I don't have to worry about wallpaper, transparency, rounded corners, etc.) So my wm is as plain as can be. In terms of productivity, this has worked tremendously well!
Kind of the direction I'm heading. Gaps, for me, are not so much to make things look good but more to give me a more defined separation for each window, I'm not concerned about seeing my wallpaper through them, besides my wallpaper is pretty plain anyway.
Very nice, never knew you could slap on such status bars and make them interactable, I've only used the text function xsetroot and the clickable part was for the fancier WM, but I was wrong.
Nice! I like simplicity. I just have updates, volume, weather and date on my bar but I do like the your little yad program. Dan over at Miyo is doing some nice stuff with yad.
Hey Jack, nice video and script. I never heard of yad. Simple and effective. I know you didn't ask for a code review, however it's always nice to get some input in order to make your work more robust. 1st, you will have to move the upd, instance and list assignations within the while loop since they will never get updated during the loop 2nd, it's good practice to wrap all paths with variable expansion in double quotes to avoid errors with white spaces 3rd, avoid using variables such as $HOME in scripts that will be launched automatically by a background processes, it might cause unwanted behavior I recommend to all my colleagues to pass shell scripts through shellcheck; it really helped me sharpening my bash scripting skills. Cheers from Montreal, Canada!
Thank you, and you are absolutely correct about the script, it needed some correction, I always appreciate constructive critique on my work, if I'm doing something wrong, I want to know. I have been stubborn about using shellcheck and need to just install it. Thanks for watching and sharing your thoughts and tips.
Instead of gaps, I would make a window border and give it a well defined color so you could differentiate from the background. In cases where the background is similar in color it could make it easier. For easiest visibility, hot pink is good. You'll never mistake that for anything else. ;)
I use borders too, but still just feels crowded when I don't have a little bit of space between windows, I struggle with that when I run splits in vim as well.
@@JakeLinux As do I. That's also why I started using tabs and why I use multiple terminal windows because the border is so thin. Thanks to whoever gave me that tip. Was that you or someone else? I can't remember now, but I'm loving tabs in vim.
@@JakeLinux Then it probably was. I watch a lot of videos on Linux but I only remember one talking about tabs. I might be getting old because they do say the memory is the first to go.
I'm playing with Openbox after a long while and think it's absolutely fantastic without a bar. No bar just feels like I'm worrying about less overall lol. Good watch!
Just between you and me, the GUI configuration methods are kinda lackluster compared to editing the dizzying .XML file directly. You go farther just editing that. It's rather powerful and is capable of keychains/keychords like sxhkd.
Dang, I love yer fzf menus; I wanna do this, but I gotta pick a tiling window manager... I don't love AWESOME, thinking about checking out yer suggestion, but I gotta setup my own bars and stuff - do you GitHub yer .config files?
I've riced Polybar, Conky-status, and Bumblebee-status way more than necessary by any conventional measure, but it's been a couple of weeks since I asked myself considering all I prefer doing fullscreen, why have a bar in the first place? I know what apps are in what workspaces, and system info in the terminal is system info, so I can figure it out from there. :) A systray as a scratchpad would be the cat's ass. Lemon water with a touch of honey would be my recommendation instead of, for instance, good old-fashioned water.
Good point, but that's just how I do things. I use bash, so when I write scripts, that's what I write them for, it's easy enough for a person to change if they want to use one of my scripts but use a different posix shell.
I went very minimalist a few months ago, as I found out that ricing (while fun) can be very distracting. My bar (py3status) today only has 2 'modules': the workspace numbers (to know where I am) and the date/time (to know when I am...?). On my laptop, I connect to the Internet through cli, so no need for the network applet. Volume and battery indication is through dunst.
For those apps that need it, a tray is enabled but it is invisible when not in use. (Also got rid of my i3 gaps so I don't have to worry about wallpaper, transparency, rounded corners, etc.) So my wm is as plain as can be. In terms of productivity, this has worked tremendously well!
Kind of the direction I'm heading. Gaps, for me, are not so much to make things look good but more to give me a more defined separation for each window, I'm not concerned about seeing my wallpaper through them, besides my wallpaper is pretty plain anyway.
Very nice, never knew you could slap on such status bars and make them interactable, I've only used the text function xsetroot and the clickable part was for the fancier WM, but I was wrong.
You can do just about anything with a bar on almost any window manager now. (With some exceptions of course)
Nice! I like simplicity. I just have updates, volume, weather and date on my bar but I do like the your little yad program. Dan over at Miyo is doing some nice stuff with yad.
Thanks! I'll have to check that out, is it a TH-cam channel?
@@JakeLinux MiyoLinux on YT Jake... He is fun to watch...
LLAP
@@JakeLinux Yep Miyo Linux
Hey Jack, nice video and script. I never heard of yad. Simple and effective. I know you didn't ask for a code review, however it's always nice to get some input in order to make your work more robust.
1st, you will have to move the upd, instance and list assignations within the while loop since they will never get updated during the loop
2nd, it's good practice to wrap all paths with variable expansion in double quotes to avoid errors with white spaces
3rd, avoid using variables such as $HOME in scripts that will be launched automatically by a background processes, it might cause unwanted behavior
I recommend to all my colleagues to pass shell scripts through shellcheck; it really helped me sharpening my bash scripting skills.
Cheers from Montreal, Canada!
Thank you, and you are absolutely correct about the script, it needed some correction, I always appreciate constructive critique on my work, if I'm doing something wrong, I want to know. I have been stubborn about using shellcheck and need to just install it. Thanks for watching and sharing your thoughts and tips.
Instead of gaps, I would make a window border and give it a well defined color so you could differentiate from the background. In cases where the background is similar in color it could make it easier. For easiest visibility, hot pink is good. You'll never mistake that for anything else. ;)
I use borders too, but still just feels crowded when I don't have a little bit of space between windows, I struggle with that when I run splits in vim as well.
@@JakeLinux As do I. That's also why I started using tabs and why I use multiple terminal windows because the border is so thin. Thanks to whoever gave me that tip. Was that you or someone else? I can't remember now, but I'm loving tabs in vim.
@@anon_y_mousse not sure if it was me or not, I did release a video recently about tabs and splits.
@@JakeLinux Then it probably was. I watch a lot of videos on Linux but I only remember one talking about tabs. I might be getting old because they do say the memory is the first to go.
@@anon_y_mousse I know that's true! My memory is getting horrible.
I'm playing with Openbox after a long while and think it's absolutely fantastic without a bar. No bar just feels like I'm worrying about less overall lol. Good watch!
Never could get into openbox, not sure why everyone loves it so much, maybe have to give it another go.
Just between you and me, the GUI configuration methods are kinda lackluster compared to editing the dizzying .XML file directly. You go farther just editing that. It's rather powerful and is capable of keychains/keychords like sxhkd.
Do it your way Jake that makes for great viewing. GVJ
Thanks!
Dang, I love yer fzf menus; I wanna do this, but I gotta pick a tiling window manager... I don't love AWESOME, thinking about checking out yer suggestion, but I gotta setup my own bars and stuff - do you GitHub yer .config files?
Thanks, I think my fzf menus are my favorite build. I do have most of my configs on GitHub/gitlab but I need to do some updating on some of it.
Sorry Jake, I wan it all on my bar... LOL
Great video. Awesome Yad menu too...
LLAP 🖖
It's all good Bruce, to each his own.
I've riced Polybar, Conky-status, and Bumblebee-status way more than necessary by any conventional measure, but it's been a couple of weeks since I asked myself considering all I prefer doing fullscreen, why have a bar in the first place? I know what apps are in what workspaces, and system info in the terminal is system info, so I can figure it out from there. :)
A systray as a scratchpad would be the cat's ass.
Lemon water with a touch of honey would be my recommendation instead of, for instance, good old-fashioned water.
I have a simple script that toggles polybar on for about 30 seconds then hides it again.
@@JakeLinux I tried Polybar-autohide and it wasn't smooth at all, so that was that. I'll look for the script some time. Thanks.
@@thenextpoetician6328 never heard of polybar autohide
Did you put config of this bar on your hub/lab page. I need simple bar like this, just wanna check config file and change it to my needs.
I have not yet, I need to make a couple of commits and update some repos, will be doing it soon.
8:19 why bash? just use program called "[" or "test" and use sh for posix complaint shell
Good point, but that's just how I do things. I use bash, so when I write scripts, that's what I write them for, it's easy enough for a person to change if they want to use one of my scripts but use a different posix shell.
i probably will "steal" that update icon script...:)
Still need a little clean up, will be pushed to GitHub/lab soon.
looks very minimal and clean thanks jake 😁😁
Thanks, and you're welcome!