prettierHEADmaster

4 files changed, 36 insertions, 32 deletions

diff --git a/content/posts/2018-08-01-dxvk-gentoo.es.md b/content/posts/2018-08-01-dxvk-gentoo.es.md
index 0a899a3..dea8bc9 100644
--- a/content/posts/2018-08-01-dxvk-gentoo.es.md
+++ b/content/posts/2018-08-01-dxvk-gentoo.es.md
@@ -2,15 +2,18 @@
 layout: post
 title: Compilando las DLLs de DXVK en Gentoo
 tags:
-- wine
-- dxvk
-- gentoo
+  - wine
+  - dxvk
+  - gentoo
 
 TocOpen: true
 ShowToc: true
 ---
 
-La forma mas sencilla de compilar DXVK en Gentoo es con una chroot de Debian, pero... Donde está la diversión en eso? La primera vez que lo intenté me topé con varios problemas y no encontré documentado el proceso en ningún sitio. Esta entrada es un intento de resolver ese problema.
+La forma mas sencilla de compilar DXVK en Gentoo es con una chroot de Debian,
+pero... Donde está la diversión en eso? La primera vez que lo intenté me topé
+con varios problemas y no encontré documentado el proceso en ningún sitio. Esta
+entrada es un intento de resolver ese problema.
 
 <hr>
 
@@ -18,10 +21,10 @@ La forma mas sencilla de compilar DXVK en Gentoo es con una chroot de Debian, pe
 
 Según la documentación oficial necesitamos:
 
- - wine 3.10 or newer
- - Meson build system (at least version 0.43)
- - MinGW64 compiler and headers (requires threading support)
- - glslang front end and validator
+- wine 3.10 or newer
+- Meson build system (at least version 0.43)
+- MinGW64 compiler and headers (requires threading support)
+- glslang front end and validator
 
 Todas menos MinGW las puedes instalar directamente:
 
@@ -34,8 +37,8 @@ emerge virtual/wine dev-util/meson dev-util/glslang
 Se necesita MinGW con threads de POSIX. Por suerte existe `crossdev`, el
 problema es que por defecto compila GCC con threads de Win32.
 
-Se crea primero la toolchain, la tupla para x86 es `i686-w64-mingw32` y para
-x64 `x86_64-w64-mingw32`.
+Se crea primero la toolchain, la tupla para x86 es `i686-w64-mingw32` y para x64
+`x86_64-w64-mingw32`.
 
 ```
 crossdev -t i686-w64-mingw32
@@ -47,18 +50,18 @@ threads y las librerías que hacen falta para compilarlo.
 
 1. Habilita los POSIX threads:
 
-    ```
-    mkdir /etc/portage/{env,package.env}
-    echo 'EXTRA_ECONF="--enable-threads=posix"' > /etc/portage/env/mingw32_posix_threads
-    echo -e 'cross-i686-w64-mingw32/gcc mingw32_posix_threads\ncross-x86_64-w64-mingw32/gcc mingw32_posix_threads' > /etc/portage/package.env/mingw32_posix_threads
-    ```
+   ```
+   mkdir /etc/portage/{env,package.env}
+   echo 'EXTRA_ECONF="--enable-threads=posix"' > /etc/portage/env/mingw32_posix_threads
+   echo -e 'cross-i686-w64-mingw32/gcc mingw32_posix_threads\ncross-x86_64-w64-mingw32/gcc mingw32_posix_threads' > /etc/portage/package.env/mingw32_posix_threads
+   ```
 
 1. Añade la `USE` `libraries`:
 
-    ```
-    cross-i686-w64-mingw32/mingw64-runtime libraries
-    cross-x86_64-w64-mingw32/mingw64-runtime libraries
-    ```
+   ```
+   cross-i686-w64-mingw32/mingw64-runtime libraries
+   cross-x86_64-w64-mingw32/mingw64-runtime libraries
+   ```
 
 Por último recompila `mingw64-runtime` y `gcc` por separado, en ese orden:
 
@@ -68,8 +71,8 @@ emerge -1 cross-i686-w64-mingw32/gcc cross-x86_64-w64-mingw32/gcc
 ```
 
 Dependiendo de la versión del runtime, puede que se instalen algunas librerias
-en el lugar equivocado y esto impide compilar GCC, si es el caso basta con
-hacer enlaces (Bug #653246):
+en el lugar equivocado y esto impide compilar GCC, si es el caso basta con hacer
+enlaces (Bug #653246):
 
 ```
 ln -s /usr/x86_64-w64-mingw32/usr/lib64/{libmangle.a,libpthread.a,libpthread.dll.a,libwinpthread.a,libwinpthread.dll.a,libwinpthread.la} /usr/x86_64-w64-mingw32/usr/lib/
@@ -103,6 +106,7 @@ $ meson configure -Dbuildtype=release
 $ ninja
 $ ninja install
 ```
+
 ```
 $ ls /some/install/prefix/bin
 d3d11.dll  dxgi.dll  setup_dxvk.sh
@@ -122,7 +126,7 @@ cross-x86_64-w64-mingw32/gcc-7.3.0-r3
 cross-x86_64-w64-mingw32/mingw64-runtime-5.0.4
 ```
 
-----
+---
 
 **Fuentes**:
 
diff --git a/content/posts/2018-08-01-dxvk-gentoo.md b/content/posts/2018-08-01-dxvk-gentoo.md
index 93b554b..d0aec93 100644
--- a/content/posts/2018-08-01-dxvk-gentoo.md
+++ b/content/posts/2018-08-01-dxvk-gentoo.md
@@ -2,9 +2,9 @@
 layout: post
 title: Building DXVK's DLLs on Gentoo
 tags:
-- wine
-- dxvk
-- gentoo
+  - wine
+  - dxvk
+  - gentoo
 
 TocOpen: true
 ShowToc: true
@@ -58,8 +58,8 @@ cross-x86_64-w64-mingw32/mingw64-runtime libraries
 ```
 
 Rebuild `mingw64-runtime` and `gcc`. Order matters, `mingw64-runtime` with
-`libraries` provides `pthreads.h` and other stuff that's required to compile
-GCC with the POSIX thread model.
+`libraries` provides `pthreads.h` and other stuff that's required to compile GCC
+with the POSIX thread model.
 
 ```
 emerge -1 cross-i686-w64-mingw32/mingw64-runtime cross-x86_64-w64-mingw32/mingw64-runtime
diff --git a/content/posts/2019-3-11-cpanm-module-error.md b/content/posts/2019-3-11-cpanm-module-error.md
index 698ba71..c7ac6cd 100644
--- a/content/posts/2019-3-11-cpanm-module-error.md
+++ b/content/posts/2019-3-11-cpanm-module-error.md
@@ -14,6 +14,6 @@ If you ever get this error while installing a module `cpanm`:
 ! Couldn't find module or a distribution install
 ```
 
-The problem is caused by not having the `LWP::Protocol::https` module
-installed, and the solution is to run `cpanm` with the `--no-lwp` option or
-installing `LWP::Protocol::https`.
+The problem is caused by not having the `LWP::Protocol::https` module installed,
+and the solution is to run `cpanm` with the `--no-lwp` option or installing
+`LWP::Protocol::https`.
diff --git a/content/posts/2021-02-03-gentoo-no-desktop-lag.md b/content/posts/2021-02-03-gentoo-no-desktop-lag.md
index d5c9d20..21076b9 100644
--- a/content/posts/2021-02-03-gentoo-no-desktop-lag.md
+++ b/content/posts/2021-02-03-gentoo-no-desktop-lag.md
@@ -25,8 +25,8 @@ tags:
 
    `CPUShares` option defaults to 1024, `systemd` will create a user slice for
    each user with an active session, and all processes that user run will be
-   assigned to that slice, anything that a user may run will receive 4 times
-   the CPU time of processes assigned to the portage slice.
+   assigned to that slice, anything that a user may run will receive 4 times the
+   CPU time of processes assigned to the portage slice.
 
    ```sh
    ➜  ~ cat /sys/fs/cgroup/cpu,cpuacct/user.slice/cpu.shares