mirror of
https://github.com/cowmonk/cowmonk.github.io.git
synced 2025-10-27 14:43:26 +00:00
DWM LESS IS MORE (edit)
This commit is contained in:
parent
54fc7baf64
commit
4528ba722c
2 changed files with 10 additions and 8 deletions
9
atom.xml
9
atom.xml
|
|
@ -135,10 +135,11 @@ package manager. Once you’ve done that here are the general steps:</p>
|
|||
<li><p>Find a Patch: Head over to the dwm patches page. Find a patch you like. Let’s say you want the autostart patch,
|
||||
which allows you to run commands automatically when dwm starts (I highly reccomend this especially if you’re running from a display manager!).</p></li>
|
||||
<li><p>Download the Patch: Download the .diff file for the patch. Save it somewhere, perhaps in a patches subdirectory within your dwm source folder.</p></li>
|
||||
<li><p>Apply the Patch: In your dwm source directory, use the patch command:
|
||||
<code>bash
|
||||
patch -Np1 -i patchfile.diff
|
||||
</code></p></li>
|
||||
<li><p>Apply the Patch: In your dwm source directory, use the patch command:</p></li>
|
||||
</ol>
|
||||
<pre><code class="language-bash"> patch -Np1 -i patchfile.diff
|
||||
</code></pre>
|
||||
<ol start="4">
|
||||
<li><p>Resolve Conflicts (If Any): Sometimes, patches might conflict, especially if they modify the same lines of code or if you’re applying a patch meant
|
||||
for an older version of dwm. This will result in .rej (rejected) files. You’ll need to manually edit the source files to resolve these conflicts, looking
|
||||
at the .rej files to see what couldn’t be applied. This is the trickiest part, but it gets easier with practice. Start with simple, popular patches.</p></li>
|
||||
|
|
|
|||
|
|
@ -157,10 +157,11 @@ package manager. Once you’ve done that here are the general steps:</p>
|
|||
<li><p>Find a Patch: Head over to the dwm patches page. Find a patch you like. Let’s say you want the autostart patch,
|
||||
which allows you to run commands automatically when dwm starts (I highly reccomend this especially if you’re running from a display manager!).</p></li>
|
||||
<li><p>Download the Patch: Download the .diff file for the patch. Save it somewhere, perhaps in a patches subdirectory within your dwm source folder.</p></li>
|
||||
<li><p>Apply the Patch: In your dwm source directory, use the patch command:
|
||||
<code>bash
|
||||
patch -Np1 -i patchfile.diff
|
||||
</code></p></li>
|
||||
<li><p>Apply the Patch: In your dwm source directory, use the patch command:</p></li>
|
||||
</ol>
|
||||
<pre><code class="language-bash"> patch -Np1 -i patchfile.diff
|
||||
</code></pre>
|
||||
<ol start="4">
|
||||
<li><p>Resolve Conflicts (If Any): Sometimes, patches might conflict, especially if they modify the same lines of code or if you’re applying a patch meant
|
||||
for an older version of dwm. This will result in .rej (rejected) files. You’ll need to manually edit the source files to resolve these conflicts, looking
|
||||
at the .rej files to see what couldn’t be applied. This is the trickiest part, but it gets easier with practice. Start with simple, popular patches.</p></li>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue