Now I am on Void Linux though, and even if I have access to the latest and greatest software. I decided to return for dwm for a while. Maybe permanently?
I managed to patch everything I ever wanted. Even if I had to do quite a bit of manual work. What I did was use the patching guide by uoou, which used git branches for every patch you apply, and, in my case as suggested by a comment. A “build” branch where I merge all the branches into one, which leads to less errors? Maybe its a placebo, but its quite easy to do.
In the post I mentioned before, I had already mentioned some of my reasoning behind the patches I’ve used. Here I’ll just list them again in case you are too lazy to check that other post. They can be found in dwm’s website.
For my bar, I went with the default and used aslstatus. Its pretty good! I am using the same configuration I shared in my previous post. Pretty much exactly, even though some more features were added to the tool that you may wanna check out.
Picom, the compositor I use, makes window borders transparent. A couple of lines fix it pretty nicely.
Right now I am still using some systray stuff, like volumeicon, which kinda duplicates the volume info. I will fix it one of these days…
Regardless, here’s how its looking!
In the end I am quite happy with my current setup. Everything works just fine. I had heard that the systray patch was hard to apply. I don’t know if its the relatively recent patch for dwm 6.4 or if its just that the patching method I mentioned is better. All I did was create a branch with every c+patch applied, then a branch specifically for the systray patch, and I merged them both, there were no errors at all. Thankfully I doubt I’ll add any more patches anytime soon. This is great as it is.
You can find my configuration here. Just build it and it will be good to go.
This is day 13 of #100DaysToOffload
]]>/home partition, I was unable to restore the Thunderbird profile I used to have.
No big deal, I decided to just download the tarball provided in their website, and simply use that. It worked fine, but when I tried to add my existing profile folder, the program just crashed, and I was unable to restore my settings, my gpg keys, filters, calendars and so on.
This is what ultimately made me go and try out Neomutt, and I have been using it ever since.
My last post I talked about a terminal application known as khal, and how to integrate it with my Nextcloud server via CalDAV. So i just wanted to say what I’ve done for contacts for neomutt, as well as my android device.
I went ahead and tried khard, a tool that works similarly to khal, integrating with vdirsyncer to keep my contacts synced with Nextcloud, the setup is pretty similar to what I did for my calendars, and you can read their documentation to check out how to do it. Adding a cronjob to automate these updates and checks was no big deal.
I also integrated it with Mutt, so now when filling up the To: in an email I can just hit
When it comes to android, I think I’ve already mentioned it in other posts, but it doesn’t matter, DAVx5 is a fantastic app that allows me to add a DAV account and sync everything, it integrates wonderfully with the contacts and calendar apps I use, it just works.
If you have the Nextcloud app installed, you can also auto-connect to DAVx5 in the settings, so its not even that complicated to setup, just do it once, and forget about it.
So, both vdirsynced and DAVx5 are amazing applications that allow me to easily access my contacts and events in a pretty easy way.
The UNIX philosophy is pretty interesting. Programs and tools dedicated to one thing, able to simply be connected to each other and delegate tasks to whatever does the job best.
I am particularly amazed at how my contacts and calendars are now simply a set of files and folders in my Linux system, that can be integrated with these simple programs without too much trouble. I am really happy with how it works, no longer will I deal with random broken profiles and settings, hopefully. And its pretty easy to backup too!
This has been day 88 of #100DaysToOffload
]]>