The Waybar launch.sh to source the .bashrc

[zzvara]

Supports use-cases for custom Python venvs, for example, for plugins like nextmeeting.

[mylinuxforwork]

Hi. Could this cause any side effects? I will test.

[mylinuxforwork]

@zzvara What happens if someone switched to zsh? Is it the required to source the .zshrc?

[phoekjelle]

I don't understand what is the benefit of this?

[zzvara]

@mylinuxforwork I indeed use .zshrc, but I had to replicate my .zshrc setup to .bashrc, because some programs that interface with bash use .bashrc, not .zshrc. I define Python, sdkman and other development environment stuff to .zshrc and .bashrc and by default these programs add themselves to these rc files.

I realized, that Waybar could not call nextmeeting Python program that uses gcalcli, because nextmeeting lives in my Python venv. While I customize Waybar, I add custom modules that make calls to programs that work correctly after .rc files are loaded.

Maybe sourcing these .rc files in the Waybar launch.sh is not the best way, but I could not find a better place globally, and it worked.

[zzvara]

@mylinuxforwork I now have a python env, scala, java, sdkman and soon other stuff which requires that .rc files to be loaded for Waybar. I love how customizable it is.

I now have Teleport VPN login panels, meeting monitors, indoor and outdoor air quality monitors with notifications for me to open the window to get some fresh air inside, because of high CO2.

These all need .rc files to be loaded, because the runtimes required for these also add themselves to the .rc file by default, during their installation.

[JumpIn-Git]

I would just add a option to the ml4w app