notes: move old notes into the 2023 folder without breaking links

Signed-off-by: Xe Iaso <me@xeiaso.net>

5 files changed, 20 insertions, 11 deletions

diff --git a/lume/src/notes/2023/_data.yml b/lume/src/notes/2023/_data.yml
new file mode 100644
index 0000000..a458d74
--- /dev/null
+++ b/lume/src/notes/2023/_data.yml
@@ -0,0 +1,5 @@
+layout: blog.njk
+type: blog
+index: true
+is_note: true
+year: 2023
diff --git a/lume/src/notes/cursorless-alien-magic.mdx b/lume/src/notes/2023/cursorless-alien-magic.mdx
index 8bb80b9..966a438 100644
--- a/lume/src/notes/cursorless-alien-magic.mdx
+++ b/lume/src/notes/2023/cursorless-alien-magic.mdx
@@ -2,6 +2,7 @@
 title: "Cursorless is alien magic from the future"
 date: 2023-11-09
 tags: ["cursorless", "vscode"]
+basename: ../../notes/cursorless-alien-magic
 ---
 
 Just in time for me to start a new job at a new place, my RSI has decided to flare up.
@@ -130,4 +131,4 @@ I'm glad you asked! This is something that I'm experimenting with to try to find
 
 Since I'm taking the opportunity to radically redesign the Talon bindings for Go, I want to try unifying the syntax of pointer values into the idea of raising and lowering to see how it makes it easier to understand Go programs. I don't know if this is a good idea, but you have to fuck around in order to find out.
 
-Maybe some parts of our industry are actually good. I really hope that I get led into the [GitHub copilot voice beta](https://githubnext.com/projects/copilot-voice/) soon, I want to compare how Talon does voice coding versus how copilot voice does it.
\ No newline at end of file
+Maybe some parts of our industry are actually good. I really hope that I get led into the [GitHub copilot voice beta](https://githubnext.com/projects/copilot-voice/) soon, I want to compare how Talon does voice coding versus how copilot voice does it.
diff --git a/lume/src/notes/recover-github-action-secret.mdx b/lume/src/notes/2023/recover-github-action-secret.mdx
index 1c0c825..385ec2f 100644
--- a/lume/src/notes/recover-github-action-secret.mdx
+++ b/lume/src/notes/2023/recover-github-action-secret.mdx
@@ -6,6 +6,7 @@ tags:
   - actions
   - secrets
   - tailscale
+basename: ../../notes/recover-github-action-secret
 ---
 
 Sometimes you fuck up and lose your only copy of a GitHub secret that you can't replace easily, such as a [Cachix](https://www.cachix.org/) signing key. However you lucked out and that key is actually saved in GitHub Actions secrets...which won't let you read the contents of that secret for understandable security reasons. Here's how you work around that.
@@ -16,10 +17,10 @@ First, make sure [Deno](https://deno.land) is installed and copy this program to
 const port = 8080;
 
 const handler = async (req: Request): Promise<Response> => {
-    const body = (await req.text());
-    console.log(body);
-    
-    return new Response()
+  const body = await req.text();
+  console.log(body);
+
+  return new Response();
 };
 
 console.log(`HTTP server running. Access it at: http://localhost:${port}/`);
@@ -58,4 +59,4 @@ jobs:
 
 Replace the contents of `TARGET` as facts and circumstances demand.
 
-Now you can recover your secret by hitting the "Run workflow" button on the Actions tab of your repo. The secret will be in your terminal, and you can copy it to your password manager as a note.
\ No newline at end of file
+Now you can recover your secret by hitting the "Run workflow" button on the Actions tab of your repo. The secret will be in your terminal, and you can copy it to your password manager as a note.
diff --git a/lume/src/notes/talon-lists.mdx b/lume/src/notes/2023/talon-lists.mdx
index f9cebaa..56456d9 100644
--- a/lume/src/notes/talon-lists.mdx
+++ b/lume/src/notes/2023/talon-lists.mdx
@@ -2,6 +2,7 @@
 title: "How to use lists in Talon"
 date: 2023-11-11
 tags: [talon, lists]
+basename: ../../notes/talon-lists
 ---
 
 When you are making commands in Talon, sometimes you need to have a of things that you say which are turned into things that the computer understands.There are a few ways to implement this but it is easy to do it very wrong.
@@ -133,4 +134,4 @@ If you're using Talon more seriously, you should be in the Patreon Beta anyways.
 
 Talon is really cool and a lot of the really cool parts are tragically under-documented I am just barely scratching the surface here, but this is documenting what I am figuring out as I dig more deeply into Talon. I hope this is useful to someone.
 
-If you want to see the Talon bindings I've created for my blog characters, you can look [in my `Xe/invocations` repo](https://github.com/Xe/invocations/tree/main/apps/vscode). I'm still working on them, but they're a good starting point for anyone that wants to do something similar.
\ No newline at end of file
+If you want to see the Talon bindings I've created for my blog characters, you can look [in my `Xe/invocations` repo](https://github.com/Xe/invocations/tree/main/apps/vscode). I'm still working on them, but they're a good starting point for anyone that wants to do something similar.
diff --git a/lume/src/notes/vscode-go-ext.mdx b/lume/src/notes/2023/vscode-go-ext.mdx
index 6735bd8..e12c845 100644
--- a/lume/src/notes/vscode-go-ext.mdx
+++ b/lume/src/notes/2023/vscode-go-ext.mdx
@@ -5,6 +5,7 @@ hero:
   ai: Counterfeit-XL
   file: galaxy-waifu
   prompt: A green-haired anime woman with cyberpunk style clothing drinking coffee in a cyberpunk space station
+basename: ../vscode-go-ext
 ---
 
 When I write these articles, I like having an answer to the question at hand before I start writing. I don't feel like it is fair to readers to have a question without an answer.
@@ -17,10 +18,10 @@ What the fuck am I doing wrong?
 
 Here are all of the steps I've tried:
 
-* Removing settings sync and re-enabling it on all affected machines
-* Looking through system logs around the time of the removal happening
-* Starting from scratch on a new machine (my new work computer) and then syncing settings to find that the Go extension is not being synced
-* Marking the Go extension as "do not sync" and then marking it as "do sync"
+- Removing settings sync and re-enabling it on all affected machines
+- Looking through system logs around the time of the removal happening
+- Starting from scratch on a new machine (my new work computer) and then syncing settings to find that the Go extension is not being synced
+- Marking the Go extension as "do not sync" and then marking it as "do sync"
 
 If anyone is able to figure out what I could have possibly fucked up, I will post the solution here and credit them.