Meta: Prettier wird jetzt als Formattierer benutzt

content/blog/nix.md

@@ -3,15 +3,16 @@ title: Nix on macOS
 date: 2024-03-14
 description: Moving from Homebrew to Nix. Mostly.
 tags:
-- nix
+  - nix
 ---
+
 For about a year, I've been fascinated by [Nix and NixOS](https://nixos.org). I don't remember exactly what fascinated me at first, probably the possibility to setup and configure my system using a single file. A few weeks ago, I decided to give it a serious try.
 
 ## Installation
 
 To be honest this is not my first time installing Nix on my machine. I tried the official Nix installer and the "old" way to use Nix which is basically the same as any other package manager. I didn't see the point of having two package managers so I uninstalled Nix quickly after.
 
-Then, a few weeks ago, I came across [this guide](https://nixcademy.com/2024/01/15/nix-on-macos/) and it instantly clicked with me. Having a single file in which I declare my complete system and then have it set up in a few minutes without rebooting is just infinitely cool. In Nix, this feature is called *flake*. The guide uses the [Determinate systems installer](https://github.com/DeterminateSystems/nix-installer) which sets up flakes by default. It also explains how to install Nix Darwin.
+Then, a few weeks ago, I came across [this guide](https://nixcademy.com/2024/01/15/nix-on-macos/) and it instantly clicked with me. Having a single file in which I declare my complete system and then have it set up in a few minutes without rebooting is just infinitely cool. In Nix, this feature is called _flake_. The guide uses the [Determinate systems installer](https://github.com/DeterminateSystems/nix-installer) which sets up flakes by default. It also explains how to install Nix Darwin.
 
 ## Nix Darwin
 
@@ -27,7 +28,7 @@ For everything else, from terminal based programs to their configuration, I use
 
 In the process of writing my Nix configuration, I became unsatisfied with my Neovim setup. I used to use [LazyVim](https://www.lazyvim.org) but it felt more and more bloated and slow on my 9 year old machine. For some time I used [Helix](https://helix-editor.com/) which has great defaults, such as language server protocol (LSP) and fuzzy finder integration. I really think Neovim should go in this direction. Unfortunately it lacks some features to make it my main editor, mostly support for [Typst](https://typst.app/) which is already added to the `master` branch. It also lacks a plugin system, but given such great defaults, there isn't that big of a need for it. Helix also features its own set of motions, and although I think they are not bad, maybe even better than Vim motions, the latter are so ubiquitously implemented that I would essentially use both all the time.
 
-That's when I saw a video by *ThePrimeagen* in which he recommended [Kickstart](https://github.com/nvim-lua/kickstart.nvim/tree/master), a minimal Neovim starter configuration mainly written by *TJ DeVries*. It almost everything you need to get started and has insanely great documentation.
+That's when I saw a video by _ThePrimeagen_ in which he recommended [Kickstart](https://github.com/nvim-lua/kickstart.nvim/tree/master), a minimal Neovim starter configuration mainly written by _TJ DeVries_. It almost everything you need to get started and has insanely great documentation.
 
 The only thing that bothered me was the use of [Mason](https://github.com/williamboman/mason.nvim) as a LSP package manager. For some people this might be the best way to install LSPs, but I don't understand why I would use a second package manager when I can just use Nix for everything. Helix has a list of supported LSPs and all you have to do is make sure they are in your `$PATH`.