cowmonk/cowmonk.based.pt
1
0
Fork 0
mirror of https://github.com/cowmonk/cowmonk.github.io.git synced 2025-10-27 06:33:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

DWM - Less is more!

Browse source
This commit is contained in:
cowmonk 2025-05-06 19:55:37 -07:00
parent 4528ba722c
commit e72fd7d4b2
2 changed files with 6 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

7
atom.xml
View file

@ -143,11 +143,10 @@ which allows you to run commands automatically when dwm starts (I highly reccome
<li><p>Resolve Conflicts (If Any): Sometimes, patches might conflict, especially if they modify the same lines of code or if you&#8217;re applying a patch meant
for an older version of dwm. This will result in .rej (rejected) files. You&#8217;ll need to manually edit the source files to resolve these conflicts, looking
at the .rej files to see what couldn&#8217;t be applied. This is the trickiest part, but it gets easier with practice. Start with simple, popular patches.</p></li>
<li><p>Recompile: After applying a patch (and resolving any conflicts), you need to recompile!
<code>bash
$ sudo make clean install
</code></p></li>
<li><p>Recompile: After applying a patch (and resolving any conflicts), you need to recompile!</p></li>
</ol>
<pre><code class="language-bash"> $ sudo make clean install
</code></pre>
<p>And that&#8217;s the patching dance! It can be a bit fiddly, especially when patches conflict, but it gives you incredible control over your window manager.
Also, a quick note! Some patches might change the config.def.h, add these new changes to your config.h since they are default configs for the new patches.</p>
<h2 id="next-steps-the-suckless-mentality">Next Steps &#38; The Suckless Mentality</h2>

7
blog4.html
View file

@ -165,11 +165,10 @@ which allows you to run commands automatically when dwm starts (I highly reccome
<li><p>Resolve Conflicts (If Any): Sometimes, patches might conflict, especially if they modify the same lines of code or if you&#8217;re applying a patch meant
for an older version of dwm. This will result in .rej (rejected) files. You&#8217;ll need to manually edit the source files to resolve these conflicts, looking
at the .rej files to see what couldn&#8217;t be applied. This is the trickiest part, but it gets easier with practice. Start with simple, popular patches.</p></li>
<li><p>Recompile: After applying a patch (and resolving any conflicts), you need to recompile!
<code>bash
$ sudo make clean install
</code></p></li>
<li><p>Recompile: After applying a patch (and resolving any conflicts), you need to recompile!</p></li>
</ol>
<pre><code class="language-bash"> $ sudo make clean install
</code></pre>
<p>And that&#8217;s the patching dance! It can be a bit fiddly, especially when patches conflict, but it gives you incredible control over your window manager.
Also, a quick note! Some patches might change the config.def.h, add these new changes to your config.h since they are default configs for the new patches.</p>
<h2 id="next-steps-the-suckless-mentality">Next Steps &#38; The Suckless Mentality</h2>