Forum › Forums › New users › New Users and General Questions › dwm as default wm
- This topic has 99 replies, 13 voices, and was last updated Aug 19-2:48 pm by andyprough.
-
AuthorPosts
-
August 16, 2021 at 3:49 am #65098Moderator
BobC
::What I miss is a decent menu or toolbar. But I don’t want it eating memory or slowing things down much. Maybe dmenu has options I can use, or maybe 9menu or jgmenu… just thinking aloud. Hlwm has the same issue.
August 16, 2021 at 5:50 am #65104Member
andyprough
::What I miss is a decent menu or toolbar. But I don’t want it eating memory or slowing things down much. Maybe dmenu has options I can use, or maybe 9menu or jgmenu… just thinking aloud. Hlwm has the same issue.
I just pop up an instance of antiX’s great app-select menu with my Super-Shift-a keybinding when I need a full-featured menu, then dismiss it when I’m done. That way I don’t have a bigger menu that’s taking up resources 99% of the time.
xfce4-appfinder is another similar one that will install with just a very few dependencies. It has all the bells and whistles – more full featured than app-select. But it’s also one where you can call up an instance from dwm or herbstluft when you want it, and then just dismiss it.
August 18, 2021 at 1:54 pm #65178Memberolsztyn
::Just as this thread has be thoroughly discussed and many great thought have been shared I just have one remaining question that bugs me:
The peculiar DWM behavior described in post #84852, where occasionally on one of my instances an image of closed app remains in the screen, not being cleared, until a new app is started: Has anyone else experienced this behavior?I am trying to positively determine if it is a bug or just me. I have done lots of testing and it seems to happen on one my Live instance but not on others. This would indicate some difference in that instance and not a bug, not sure why though… Other than that DWM functions perfectly…
Any info will be appreciated. Thanks and Regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersAugust 18, 2021 at 3:40 pm #65180Member
andyprough
::Just as this thread has be thoroughly discussed and many great thought have been shared I just have one remaining question that bugs me:
The peculiar DWM behavior described in post #84852, where occasionally on one of my instances an image of closed app remains in the screen, not being cleared, until a new app is started: Has anyone else experienced this behavior?I am trying to positively determine if it is a bug or just me. I have done lots of testing and it seems to happen on one my Live instance but not on others. This would indicate some difference in that instance and not a bug, not sure why though… Other than that DWM functions perfectly…
Any info will be appreciated. Thanks and Regards…I don’t recall ever seeing that. If you only saw it on your Live instance and not on others, then you probably answered your own question. Probably some graphics aspect of the Live system.
With DWM, you can try different graphics compositors – maybe one of them would improve your graphics experience. A couple of common compositors are compton and picom, and you can use openbox and other compositors. Try installing compton with “sudo apt install compton”, and then use dmenu to start “compton”, and see if you get the graphics artifact. Or do the same with picom. If you find one that works, you can put it into your ~/.xinitrc file (or autostart file if you installed the dwm autostart patch) as just a single line: “compton &”, or “picom &”. compton and picom will also allow you to set transparency in some of your programs, such as with many of your terminal emulators, like roxterm.
Now that I’ve begun exploring herbstluftwm, I see how stuff like using compositors is easier than with DWM. Just put a “compton &” line in ~/.config/herbstluftwm/autostart, hit the Super-Shift-r key combination to refresh the window manager, and you are done.
Edit – picom, a lightweight version of compton, is not in the Debian repos, and would have to be built from source: https://github.com/yshui/picom. It’s available in the Arch AUR – I must have used it when I was trying Artix.
2nd Edit – I built picom – very easy using the instructions on the github page:
Install dependencies:
sudo apt install libxext-dev libxcb1-dev libxcb-damage0-dev libxcb-xfixes0-dev libxcb-shape0-dev libxcb-render-util0-dev libxcb-render0-dev libxcb-randr0-dev libxcb-composite0-dev libxcb-image0-dev libxcb-present-dev libxcb-xinerama0-dev libxcb-glx0-dev libpixman-1-dev libdbus-1-dev libconfig-dev libgl1-mesa-dev libpcre2-dev libpcre3-dev libevdev-dev uthash-dev libev-dev libx11-xcb-dev meson cmake
Clone the source and build and install:cd /usr/src/ sudo git clone https://github.com/yshui/picom cd picom/ sudo git submodule update --init --recursive sudo meson --buildtype=release . build sudo ninja -C build sudo ninja -C build install- This reply was modified 1 year, 8 months ago by andyprough.
- This reply was modified 1 year, 8 months ago by andyprough.
August 18, 2021 at 4:47 pm #65181Memberolsztyn
::I don’t recall ever seeing that.
Thank you andyprough!
This is good news. I have multiple Live instances and this happens on just one of them. As you have never seen this behavior and you have way more experience than I do, this confirms to me that it is not any bug of DWM but just some malfunctioning of that live instance.
This is all I wanted to know to put this issue to sleep…On compositors:
This is another new area to me to become familiar and I appreciate this info…
Thanks and Regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersAugust 19, 2021 at 6:48 am #65188Anonymous
::great info on picom @andyprough
had never heard of it.
If users edit line 31 of meson.build in the src directory
and change 1.12.0 to just 1.12 picom builds on antiX-17.4.1 full 64-bit.August 19, 2021 at 2:23 pm #65204Member
andyprough
::great info on picom @andyprough
had never heard of it.
If users edit line 31 of meson.build in the src directory
and change 1.12.0 to just 1.12 picom builds on antiX-17.4.1 full 64-bit.Looks like picom is available in Debian 11 Bullseye: https://packages.debian.org/bullseye/picom
So the next antiX should have it in the repos.August 19, 2021 at 2:33 pm #65205Anonymous
::DWM and picom build from git with no errors or need to edit on
antiX-bullseye-B1 install using your instructions in post #64268.
It also adds to the slim F1 selection.August 19, 2021 at 2:47 pm #65207Member
Xecure
::Looks like picom is available in Debian 11 Bullseye
picom replaces compton (it is its successor) (in bullseye:
This package is deprecated and will soon be removed, please switch to picom.
)
After bullseye, a dummy comptom package is used as a meta package to install picom directly.antiX Live system enthusiast.
General Live Boot Parameters for antiX.August 19, 2021 at 2:48 pm #65208Member
andyprough
::DWM and picom build from git with no errors or need to edit on
antiX-bullseye-B1 install using your instructions in post #64268.
It also adds to the slim F1 selection.Yes, slim is grabbing the DWM entry when you create the /usr/share/xsessions/dwm.desktop file. I think that pretty much all the login managers will grab the entry from that file.
-
AuthorPosts
- You must be logged in to reply to this topic.