The code and data behind xeiaso.net
notes: move old notes into the 2023 folder without breaking links
Signed-off-by: Xe Iaso <me@xeiaso.net>
+24
-11
+3
.vscode/settings.json
+3
.vscode/settings.json
+5
lume/src/notes/2023/_data.yml
+5
lume/src/notes/2023/_data.yml
+2
-1
lume/src/notes/cursorless-alien-magic.mdx
lume/src/notes/2023/cursorless-alien-magic.mdx
+2
-1
lume/src/notes/cursorless-alien-magic.mdx
lume/src/notes/2023/cursorless-alien-magic.mdx
···
2
2
title: "Cursorless is alien magic from the future"
3
3
date: 2023-11-09
4
4
tags: ["cursorless", "vscode"]
5
+
basename: ../../notes/cursorless-alien-magic
5
6
---
6
7
7
8
Just in time for me to start a new job at a new place, my RSI has decided to flare up.
···
130
131
131
132
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.
132
133
133
-
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.
134
+
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.
+6
-5
lume/src/notes/recover-github-action-secret.mdx
lume/src/notes/2023/recover-github-action-secret.mdx
+6
-5
lume/src/notes/recover-github-action-secret.mdx
lume/src/notes/2023/recover-github-action-secret.mdx
···
6
6
- actions
7
7
- secrets
8
8
- tailscale
9
+
basename: ../../notes/recover-github-action-secret
9
10
---
10
11
11
12
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
17
const port = 8080;
17
18
18
19
const handler = async (req: Request): Promise<Response> => {
19
-
const body = (await req.text());
20
-
console.log(body);
21
-
22
-
return new Response()
20
+
const body = await req.text();
21
+
console.log(body);
22
+
23
+
return new Response();
23
24
};
24
25
25
26
console.log(`HTTP server running. Access it at: http://localhost:${port}/`);
···
58
59
59
60
Replace the contents of `TARGET` as facts and circumstances demand.
60
61
61
-
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.
62
+
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.
+2
-1
lume/src/notes/talon-lists.mdx
lume/src/notes/2023/talon-lists.mdx
+2
-1
lume/src/notes/talon-lists.mdx
lume/src/notes/2023/talon-lists.mdx
···
2
2
title: "How to use lists in Talon"
3
3
date: 2023-11-11
4
4
tags: [talon, lists]
5
+
basename: ../../notes/talon-lists
5
6
---
6
7
7
8
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
134
134
135
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.
135
136
136
-
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.
137
+
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.
+5
-4
lume/src/notes/vscode-go-ext.mdx
lume/src/notes/2023/vscode-go-ext.mdx
+5
-4
lume/src/notes/vscode-go-ext.mdx
lume/src/notes/2023/vscode-go-ext.mdx
···
5
5
ai: Counterfeit-XL
6
6
file: galaxy-waifu
7
7
prompt: A green-haired anime woman with cyberpunk style clothing drinking coffee in a cyberpunk space station
8
+
basename: ../vscode-go-ext
8
9
---
9
10
10
11
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
18
18
19
Here are all of the steps I've tried:
19
20
20
-
* Removing settings sync and re-enabling it on all affected machines
21
-
* Looking through system logs around the time of the removal happening
22
-
* 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
23
-
* Marking the Go extension as "do not sync" and then marking it as "do sync"
21
+
- Removing settings sync and re-enabling it on all affected machines
22
+
- Looking through system logs around the time of the removal happening
23
+
- 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
24
+
- Marking the Go extension as "do not sync" and then marking it as "do sync"
24
25
25
26
If anyone is able to figure out what I could have possibly fucked up, I will post the solution here and credit them.
26
27