- This topic has 99 replies, 13 voices, and was last updated Aug 19-2:48 pm by andyprough.
-
Posts
-
Brian Masinick
I like the way linux dabbler sets up DWM, also like the way he applies patches.
This guy is a genius, incredible video, thanks very much. I’m learning and taking notes like crazy.
I’ll make sure to not only view, but also take his ideas into consideration.
I’m also contemplating creating my own interface bindings, depends on what time I have and also what I observe and learn along the way.
In any case this has already been fun and interesting!
--
Brian Masinick
anticapitalista
Not to discourage people from using dwm on antiX (it is a great tiler), but only to point out to those that want to try a tiling wm that we have the wonderful herbstluftwm already included on antiX base and full.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Brian Masinick
Not to discourage people from using dwm on antiX (it is a great tiler), but only to point out to those that want to try a tiling wm that we have the wonderful herbstluftwm already included on antiX base and full.
This is definitely true. I’ll say this: for our community, without question herbstluftwm is capable and much easier to use and understand.
dwm is a wonderful geek tool; that’s the difference! 😃😎💪
--
Brian Masinick
andyprough
I installed the systray to give some typical taskbar functions to dmenu. I did it for version 6.2 of DWM. Here are the steps:
1. Go to your DWM folder and download the systray patch version 6.2:
$ cd /usr/src/dwm/ $ wget https://dwm.suckless.org/patches/systray/dwm-systray-6.2.diff2. Based on the video from LinuxDabbler, first remove the config.h. When you run the make command, a new config.h will be recreated. But the patch will install better if you remove the current config.h
$ sudo rm config.h3. Install the systray patch
$ patch -p1 < dwm-systray-6.2.diff4. Hopefully the patch installed without error. Now make and install:
$ sudo make install5. Hopefully that command completed without errors. It did on my system. Now log out of DWM and log back in. You should have a “volumeicon-alsa-legacy” package running in a systray now in dmenu at the far right side.
Start dmenu with Alt-P or Super-P or whatever your dmenu key combination is, and type “clipit” and hit your Enter key. The clipit clipboard manager should now be in your systray.
Start dmenu again, and type “cmst” and hit Enter. Now you should have a connman systray icon in the systray, ready to respond to right or left mouse clicks to do different network functions.
For a very simple battery monitor, you can install the fdpowermon and fdpowermon-icons packages. fdpowermon will give you a very simple systray battery icon, you can move your mouse over the icon and your battery percentage will pop up.
$ sudo apt install fdpowermon fdpowermon-icons- This reply was modified 1 year, 9 months ago by andyprough.
- This reply was modified 1 year, 9 months ago by andyprough.
- This reply was modified 1 year, 9 months ago by andyprough.
olsztyn
I installed the systray to give some typical taskbar functions to dmenu. I did it for version 6.2 of DWM. Here are the steps
Thank you andyprough for the systray! It is greatly appreciated and I will implement shortly…
I did watch this video of LinuxDabbler and experimented more with dwm the past few days so as to become more acquainted and performed more testing. It already became my second most used WM on all my antiX instances, even before implementation of systray…Considering also herbstluftwm, which anticapitalista pointed out is already included with antiX, which I also tested alongside dwm:
As these WM designs are new to me experience I wanted to not only become familiar with them and evaluate usability but also and more importantly – test their resilience to misbehaving apps, perhaps you or other experts much more familiar with these WM architectures can shed some more light on the following observations out of my testing:– Both dwm and herbstluftwm appear to be very similar in design and aside from different keyboard mappings for functions and maneuvering tiles, both appear to be based on the same concept. Although on surface and practical operation appear the same concept the only significant architecture difference appears to be that configuration of WM is dynamically loaded by Herbstluftwm while configuration of dwm is statically compiled.
Is this my observation correct?– My testing of resilience of WM against misbehaving apps: I was using Badwolf for this purpose, as from my testing it was most capable of killing IceWM, Fluxbox and JWM. So Badwolf appeared to be perfect for testing Herbsluftwm and dwm, to be consistent… Admittedly I did not spend the entire day testing in a perfectly scientific manner but gave it about five rounds, so as to have some confidence in results.
Now, the findings of my rudimentary testing were somewhat surprising:
Dwm (as reported before) was quite resilient to this misbehaving Badwolf app and continued functioning normally with only Badwolf tag frozen. However in case of Herbstluftwm, in spite of the same design as dwm, Badwolf was able to freeze it a few times under the same condition.
Now my question is: Is this lower resilience of Herbstluftwm a result of dynamically loaded configuration file an perhaps some other files while in case of dwm nothing is being loaded (or required) dynamically as all dwm is pre-compiled into executable? Or is this due to some other architectural difference?I am very curious of some light on the above questions…
Although from my rudimentary testing (and perhaps someone can prove or disprove more scientifically) dwm seems most resilient, I want to stress again that the included with antiX IceWM, Fluxbox and JWM are much more user friendly WMs for mainstream use and it is rare that a misbehaving app is able o kill them. Badwolf proved to be exceptionally capable for such task…
Thanks and Regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersBrian Masinick
The question here seems to be:
Which window managers can be locked up by a program that consumes and locks resources?Several of the window managers were designed before the widespread existence of 4, 6, 8 + processors.
Such things did exist, but only in high end mainframe computer systems back in the nineties.
Mutual exclusion, thread locks and other technology techniques were applied only in expensive systems. Today even our phones and appliances have many of these capabilities.
--
Brian Masinick3. Install the systray patch
$ patch -p1 < dwm-systray-6.2.diffApplying patch:
4 out of 35 hunks FAILED — saving rejects to file dwm.c.rej
Failed at 193, 473, 787 and 820.
I will look into these rejects. Must be some typos or syntax issue…
Thanks and Regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersandyprough
Applying patch:
4 out of 35 hunks FAILED — saving rejects to file dwm.c.rej
Failed at 193, 473, 787 and 820.
I will look into these rejects. Must be some typos or syntax issue…
Thanks and Regards…Patch failures with DWM are usually just a matter of the patch program not being able to figure out the correct places to insert lines of code. It’s simple to fix – here’s a very good video by DistroTube on patching DWM and fixing patch errors that will help you: https://yewtu.be/watch?v=3dwoC0EYStw
Patch failures with DWM are usually just a matter of the patch program not being able to figure out the correct places to insert lines of code.
Great info to know…
Thanks again…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersBrian Masinick
Patch failures with DWM are usually just a matter of the patch program not being able to figure out the correct places to insert lines of code.
Great info to know…
Thanks again…I agree; chances are that something, somewhere along the way, added (or removed) a few identification lines or added something that caused the line numbers to differ – even “off by one” would be enough.
Find it and fix it, then retry; chances are much better that it’ll work then.
--
Brian MasinickPatch failures with DWM are usually just a matter of the patch program not being able to figure out the correct places to insert lines of code. It’s simple to fix
Well, in my case it was something different: Replacements in diff file referred to ‘sw’, while in the c source code of dwm.c those C statements had ‘tw’.
First I modified the patch diff file to reflect the original c code of dwm.c, which reduced the number of errors to 2, after which I modified the remaining 2 c code statements manually in dwm.c.
I am still getting compile error:
”
dwm.c: At top level:
dwm.c:1007:1: error: conflicting types for ‘getsystraywidth’
getsystraywidth()
^~~~~~~~~~~~~~~
dwm.c:477:48: note: previous implicit declaration of ‘getsystraywidth’ was here
else if (ev->x > selmon->ww – TEXTW(stext) – getsystraywidth())
^~~~~~~~~~~~~~~
make: *** [Makefile:18: dwm.o] Error 1
”
It has been a long time since I had to do anything with C code so it takes me some time to figure this out… Eventually I will…
Thanks and Regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametershere’s a very good video by DistroTube on patching DWM and fixing patch errors that will help you: https://yewtu.be/watch?v=3dwoC0EYStw
Thanks for the link…
Just to mention, recently I saw another review video by the same presenter, presenting Badwolf as the best lightweight web browser in existence…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersanticapitalista
Thanks for the link…
Just to mention, recently I saw another review video by the same presenter, presenting Badwolf as the best lightweight web browser in existence…Just goes to show that you can’t trust anyone these days … 🙂
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Just goes to show that you can’t trust anyone these days …
Indeed… Sometimes not easy to tell the form from the substance…
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
Xecure
badwolf’s strength is bworsing with JS-disabled. Outside that, it is not the ideal browser.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
- You must be logged in to reply to this topic.
