mirror of
https://gitlab.com/EternalWanderer/voidcruiser.nl
synced 2024-11-29 04:13:51 +01:00
Compare commits
2 commits
671a8a3dab
...
5dd9c337c7
Author | SHA1 | Date | |
---|---|---|---|
Nox Sluijtman | 5dd9c337c7 | ||
Nox Sluijtman | ee94eadb12 |
37
content/rambles/nixvim.md
Normal file
37
content/rambles/nixvim.md
Normal file
|
@ -0,0 +1,37 @@
|
||||||
|
---
|
||||||
|
title: "NixVim"
|
||||||
|
date: "2024-01-15T02:53:23+01:00"
|
||||||
|
author: "$HUMANOID"
|
||||||
|
tags: ["nix", "linux", "vim"]
|
||||||
|
description: "Some thoughts on Vim, NeoVim and NixVim"
|
||||||
|
draft: true
|
||||||
|
---
|
||||||
|
|
||||||
|
# Vim and Editors in General
|
||||||
|
|
||||||
|
So I've been using Vim for nearly as long as I've been using Linux. I still
|
||||||
|
vaguely remember awkwardly working `vimtutor` for the first time. Before I
|
||||||
|
touched Vim, I didn't really have any strong preference for an editor on Linux.
|
||||||
|
I'd just come from Windows where I'd used Notepad++ to edit small text files and
|
||||||
|
Visual Studio and JetBrains Rider for my college work at the time -- mainly C#
|
||||||
|
in conjunction with Unity. Sure, these editors got the job done, but they
|
||||||
|
weren't... Elegant. Visual Studio and Rider are monstrous pieces of software
|
||||||
|
with several kitchen sinks. And I'm sure Notepad++ has some really cool features
|
||||||
|
that I've never touched, but then it didn't really feel inviting to me and thus
|
||||||
|
I never dug deeper. When moving to Linux, I mainly used Gedit to edit the odd
|
||||||
|
ini file. This got rather tedious when needing root privileges to edit, say an
|
||||||
|
`sshd_config` file. Sure, you can open Gedit using `sudo`, but that makes the
|
||||||
|
terminal window from which you start it useless as long as Gedit is running. On
|
||||||
|
top of that, it being a GTK application means that it spews a lot of output to
|
||||||
|
`STDOUT`. At this point -- not wanting to dig into Vim yet -- I found out Nano
|
||||||
|
is a thing. I never liked it. It's always felt something like a clunky
|
||||||
|
on-graphical Windows Notepad of Linux.
|
||||||
|
|
||||||
|
So after a little while I decided to bite the bullet and start up `vimtutor`.
|
||||||
|
As mentioned before, it was awkward at first. But I could also see the power
|
||||||
|
that the anatomy of Vim allows the user to wield and decided to commit at least
|
||||||
|
the basics to muscle memory.
|
||||||
|
|
||||||
|
# Plugins and NeoVim
|
||||||
|
|
||||||
|
From here it would only be a matter of time.
|
23
flake.nix
23
flake.nix
|
@ -1,15 +1,32 @@
|
||||||
{ description = "Website flake";
|
{ description = "Website flake";
|
||||||
inputs = {
|
inputs = {
|
||||||
nixpkgs.url = github:NixOs/nixpkgs/nixos-23.05;
|
nixpkgs.url = "github:NixOs/nixpkgs/nixos-23.05";
|
||||||
flake-utils.url = github:numtide/flake-utils;
|
flake-utils.url = "github:numtide/flake-utils";
|
||||||
};
|
};
|
||||||
outputs = { self, nixpkgs, flake-utils }:
|
outputs = { self, nixpkgs, flake-utils }:
|
||||||
flake-utils.lib.eachDefaultSystem (system:
|
flake-utils.lib.eachDefaultSystem (system:
|
||||||
let
|
let
|
||||||
pkgs = import nixpkgs { inherit system; };
|
pkgs = import nixpkgs { inherit system; };
|
||||||
in {
|
in {
|
||||||
devShell = pkgs.mkShell {
|
packages = {
|
||||||
|
default = pkgs.stdenvNoCC.mkDerivation rec {
|
||||||
|
|
||||||
|
pname = "voidcruiser";
|
||||||
|
version = "1.3";
|
||||||
|
src = ./.;
|
||||||
|
|
||||||
buildInputs = [ pkgs.hugo ];
|
buildInputs = [ pkgs.hugo ];
|
||||||
|
|
||||||
|
buildPhase = ''
|
||||||
|
hugo
|
||||||
|
'';
|
||||||
|
|
||||||
|
installPhase = ''
|
||||||
|
mkdir -p $out/share/
|
||||||
|
cp -r public $out/share/${pname}
|
||||||
|
'';
|
||||||
|
|
||||||
|
};
|
||||||
};
|
};
|
||||||
});
|
});
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue