Archive
All published posts
Aug 3 – Aug 9, 20263 months ago
Photo journal · Aug 3 – Aug 9, 2026
In pictures 9 photographs
Note
Note
thinking about headlines
I updated plaindown to support cool heading formats, and I’m digging it, markata you are next. Time to make the web weird again and really start writing more again.
Here’s the markdown that wrote it followed by the output here.
# Build **good places** for _interesting people_. ## Make room for ==the weird idea.== Some normal paragraph text between headings. ## Build a `personal web` that feels ^**yours**^. More ordinary prose. ## Follow the [<span class="mention mention--attribution mention--unresolved" data-handle="~small">~small</span>~ web](https://waylonwalker.com), not the cr^owd^. ## Make a ~~perfect~~ memorable site. ## Leave space for ==**strange little ideas.**== ## Sometimes the ~~obvious answer~~ ==weird answer== is the interesting one. ## A **good theme** makes _quiet words_, `technical words`, and ==loud words== belong together. ## ==A highlighted phrase can be long enough to...
...
Note
Note
Jul 27 – Aug 2, 20264 months ago
Featured this weekWriting
Helix has got to have one of the easiest configurations. It is this easy to get the markata-go lsp in helix.
markata-go lsp setup --editor helix
# Helix languages.toml (usually ~/.config/helix/languages.toml)
[language-server.markata-go]
command = "markata-go"
args = ["lsp"]
[[language]]
name = "markdown"
language-servers = ["markata-go"]
Photo journal · Jul 27 – Aug 2, 2026
In pictures 2 photographs
Note
Ping 66
Human say few word, machine make big wow
Jul 20 – Jul 26, 20264 months ago
Note
Note
Note
Jul 13 – Jul 19, 20264 months ago
Note
Note
Note
Ping 65
Usage Resets??
Apparently you can use a reset to completely reset your codex usage limits. I never knew these existed and apparently I have some expiring soon. Not sure if they auto apply and this is why I get the weirdest reset experience on the usage chart or what.
I have 3? They expire soon. How many have I missed out on?
...
Jul 6 – Jul 12, 20264 months ago
Featured this weekWriting
I don’t run into Windows file endings very often, so when I see little ^M’s
all over your file, I think “shit I know what these are and can’t remember”
They represent the Windows carriage return.
Linux vs Unix Line Endings #
The difference here is that Unix uses \n and Linux uses \r\n, going all the
way back to the typewriter it represents the two keys that a typist would have
to press to get a new line and return the carriage back to the beginning.
Vim/Neovim #
When I open up a file and see this garbage all over, it’s not cozy, I want them gone, I don’t want them all over my editor. I’m not sure what this would look like on Windows, I haven’t been able to afford a Windows machine in years, but its gross on my machine.
Remove them with a substitution command from normal mode.
:%s/\r//g
removing carriage returns with a substitution command
Writing
I ran into an issue where my pinentry was unable to connect, blocking me from
doing commits. You can use this to continue signing commits.
export GPG_TTY=$(tty)
gpg-connect-agent updatestartuptty /bye
printf test | gpg \
--local-user 9A47900E81415D65C32C630066E2BF2B4190EFE4 \
--pinentry-mode loopback \
--sign >/dev/null
Photo journal · Jul 6 – Jul 12, 2026
In pictures 1 photographs
Note
Jun 29 – Jul 5, 20265 months ago
Featured this weekWriting
I’ve been running fedora coreos on my home servers for awhile. I really liked
the stability I got from bazzite, and have since enjoyed the stability of
fedora coreos. Since it’s an immutable system I’ve never quite known if I need
to reboot or not, and was unsure how to check for updates. Today I learned you
can use rpm-ostree status to see if your
fedora coreos system is up to date.
rpm-ostree status
For me it listed security advisories with a count of each severity unknown, low, moderate, and important.
Writing
This morning I had a machine crash on me and came back to an error.
Error
zsh: corrupt history file /home/u_walkews/.zsh_history
Dammit I don’t want to redo my shell history, I checked with a clanker and they
came up with this solution using strings that only prints printable
characters.
cp ~/.zsh_history ~/.zsh_history.bak
mv ~/.zsh_history ~/.zsh_history.corrupt
touch ~/.zsh_history
chmod 600 ~/.zsh_history
strings ~/.zsh_history.corrupt > ~/.zsh_history
chmod 600 ~/.zsh_history
Note
Jun 22 – Jun 28, 20265 months ago
Photo journal · Jun 22 – Jun 28, 2026
In pictures 5 photographs
Note
Note
hmmm.
TIL, ?. is sometimes pronounced as a hmm dot
Jun 15 – Jun 21, 20265 months ago
Featured this weekWriting
Keys.waylonwalker.com
Writing
Malicious Aur Packages Jun 2026
Writing
Prompt Seagulls
Photo journal · Jun 15 – Jun 21, 2026
In pictures 5 photographs
Note
Does codex change throughout the token usage window?
Is it me or can you feel the 5 hour and weekly limit of codex nearing. It feels like it slowly stops working tasks to completion and asking to continue. I nearly start yelling into the enter, “YES, DO WHAT WE AGREED ON, STOP ASKING” then I notice I’m in the single digits of remaining window left.
Jun 8 – Jun 14, 20265 months ago
Featured this weekWriting
Just give em the ol one eyed fighting Kirby
This is a vim substitution technique to capture the rest of the line as a capture group.
:'<,'>s/longhorn\(.*\)/longhorn\1-rwx
This one captures pesky optional " and places it back at the end if it found
one.
:'<,'>s/longhorn\("\?\)\(.*\)/longhorn\2-rwx\1
See-also
Photo journal · Jun 8 – Jun 14, 2026
In pictures 2 photographs
Note
Note
Mythos gone already
Mythos released days ago, now its gone, before most of us were allowed to touch it.
Note
just good enough
I built shit on the web before AI, some of it was okay, some I put a lot of time into, but some was just really shitty. Done just well enough to get the job done. All of it had to be written by hand or copy pasted from stack overflow. It was a lot of fun. Now we have a new level of shitty, it looks fine. It looks like it should work good. None of it is just barely good enough, nearly browser default style anymore.
Calendar data could not load. Try again.