I'll help you out with picom first then we can figure out the volume issue. The left bar issue is related to picom as well, try copying the picom config at awesome/configuration/mirage/picom.conf to .config/picom.conf and run picom with picom --experimental-backends

If any issues arise please respond with he output

We'll get this working :)

Hey, thanks for that. The blur works perfectly now and so do the animations, but the sidebar is still the same.

Also, the buttons on the title bar of each window have really jagged edges (no anti aliasing perhaps?) and the rounded corners are too close to the buttons (it doesnt look as refined as what was in your screenshot). How can I fix that?

Thanks for the quick reply :)

EDIT: I copied your alacritty config, and the font is all garbled now. Any idea why?

Download MesloLGS font (its in the README under "fonts to install") to fix the terminal text. I have a suspicion on whats causing the titlebar button issue, ill investigate in a VM since I think I know what the problem is and its an easy fix (has to do with screen DPI). Are the volume buttons still giving you trouble? Also, try reloading awesomewm with win + r to see of that fixes the panels. If not I'll investigate and should be able to fix since I had that issue in earlier iterations (but thought I fixed it)!

If you'd like to wrap up your picom problem replace the picom line in the autostart part of the rc.lua with the command you used to get it to work. The command i provided in the autostart assumes you don't have my picom.conf in your .config folder

Hey, thank you so much for replying so fast. Means a lot :)

What is fixed:

1. The font on the terminal is now perfect (cant believe I overlooked that part)
2. The left sidebar is now perfect
3. Picom loads properly

What still doesnt work:

1. The jagged buttons, and corners being too close to the buttons.

Again thank you very much, cant be happier.

No problem! I will adjust the buttons on my end tomorrow and let you know when they're done

I have a question for you too now, what prompt are you using under the fish shell? It looks like powerlevel10k but it was my understanding that's only for zsh

I have a question for you too now, what prompt are you using under the fish shell? It looks like powerlevel10k but it was my understanding that's only for zsh

Ah, I'm using the Tide prompt. It's a really great prompt.

Also, kudos to the amazing work you have done. I am absolutely loving your setup. I just have to change a few keybindings, and I'll be right at home.

And yeah, I forgot to mention it before, the volume buttons still dont work. Any idea why?

I was facing the same issue, where picom would not start correctly (also affecting all other commands placed in run_on_start_up). I am as well using the fish shell and was able to fix it, by changing line 71 in rc.lua:

- awful.spawn.with_shell(string.format("pgrep -u $USER -x %s > /dev/null || (%s)", findme, app), false)
+ awful.spawn.with_shell(string.format("pgrep -u $USER -x %s > /dev/null || %s", findme, app), false)

As far as I understand, the problem is, that in fish the rounded brackets indicate a command substitution, similar to $(...) in bash. If I run the original line in fish, it gives me the following output:

> pgrep -u $USER -x echo > /dev/null || (echo "Test")
fish: Command substitutions not allowed

Maybe, there is a way to change that line to something that works in both shells? Or, if that's not possible, check the shell first and adjust the command accordingly?

Anyways, thanks for the amazing work!

I was facing the same issue, where picom would not start correctly (also affecting all other commands placed in run_on_start_up). I am as well using the fish shell and was able to fix it, by changing line 71 in rc.lua:

- awful.spawn.with_shell(string.format("pgrep -u $USER -x %s > /dev/null || (%s)", findme, app), false)
+ awful.spawn.with_shell(string.format("pgrep -u $USER -x %s > /dev/null || %s", findme, app), false)

As far as I understand, the problem is, that in fish the rounded brackets indicate a command substitution, similar to $(...) in bash. If I run the original line in fish, it gives me the following output:

> pgrep -u $USER -x echo > /dev/null || (echo "Test")
fish: Command substitutions not allowed

Maybe, there is a way to change that line to something that works in both shells? Or, if that's not possible, check the shell first and adjust the command accordingly?

Anyways, thanks for the amazing work!

Oh wow, I didnt know this. Thank you very much for shedding light upon this. It'll be very useful for others who default to the fish shell

I was facing the same issue, where picom would not start correctly (also affecting all other commands placed in run_on_start_up). I am as well using the fish shell and was able to fix it, by changing line 71 in rc.lua:

- awful.spawn.with_shell(string.format("pgrep -u $USER -x %s > /dev/null || (%s)", findme, app), false)
+ awful.spawn.with_shell(string.format("pgrep -u $USER -x %s > /dev/null || %s", findme, app), false)

As far as I understand, the problem is, that in fish the rounded brackets indicate a command substitution, similar to $(...) in bash. If I run the original line in fish, it gives me the following output:

> pgrep -u $USER -x echo > /dev/null || (echo "Test")
fish: Command substitutions not allowed

Maybe, there is a way to change that line to something that works in both shells? Or, if that's not possible, check the shell first and adjust the command accordingly?

Anyways, thanks for the amazing work!

Wow good catch, thanks for the insight! I was having a hard time diagnosing this. I'll look into adding an elegant way of addressing this

I have a question for you too now, what prompt are you using under the fish shell? It looks like powerlevel10k but it was my understanding that's only for zsh

Ah, I'm using the Tide prompt. It's a really great prompt.

Also, kudos to the amazing work you have done. I am absolutely loving your setup. I just have to change a few keybindings, and I'll be right at home.

And yeah, I forgot to mention it before, the volume buttons still dont work. Any idea why?

I'll have to look into it on my end as I'm not quite sure, shouldn't be too hard to fix though!

@anandrajaram21 would you be able to confirm that the volume buttons are still not working after pulling in the recent changes to the repo? On my testing device it seems to work now (potentially an issue with fish that was indirectly resolved in the startup fix I published) but I'd like to confirm it works across all devices before closing

I just pulled the new version, but the volume doesnt work.