Published

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"]

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

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

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.

This morning I had a machine crash on me and came back to an error.

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