Dave Marquardt

@FritzAdalis @RuntimeArguments @jammcq @YesJustWolf

Thanks. I did look this up after I wrote the post. I should have looked it up before. But still, without knowing that history, it appeared the speaker was either confused about #OpenSSH and #OpenBSD or equating them or something. It wasn't obvious to me that the OpenBSD team *wrote* OpenSSH. That's the way I heard it, might have misinterpreted what was said.

@RuntimeArguments @jammcq @YesJustWolf

You touched on the -R flag briefly. I've used it, but I don't recall it for the purpose you mentioned.

I need to check out using certificates.

I didn't know about password managers being ssh key agents. Another thing to check out, as I use a few 😀

I also didn't know about ssh-import-id-gh, which doesn't appear to be part of any package in the Fedora repos.

A better episode than I expected given my long use of #SSH.

2/2

@RuntimeArguments @jammcq @YesJustWolf

I've been a #UNIX user since 1984, and spent my working life developing flavors of Unix and now #Linux. I listened to this episode over the past couple of days. I'm a long time user of #SSH One point of confusion and a few points that I learned.

When talking about the origins of #OpenSSH you talked about #OpenBSD but didn't explain how it related to OpenSSH . Was OpenBSD involved in the creation of OpenSSH ? It could have used explanation.

1/2

#ssh

@paniash

IIRC @publicvoit published something about following feeds using Gnus. I used to do that. The sticking point is that Emacs will hang while Gnus waits for a feed that may or may not connect or provide its data. elfeed was better about that, but I missed Gnus' adaptive scoring. I'd written an elfeed adaptive scoring package, but was never thrilled about using a separate package for feeds. So I'm giving Gnus and nnrss and nnatom another try.

#emacs #gnus

Browsing URLs from Gnus Summary buffer https://davemq.github.io/emacs/gnus/url/2026/04/29/visiting-urls-from-gnus-summary.html

#emacs #gnus

@me What version of #Emacs? What version of #Gnus? Maybe nnatom isn't included in your version.

New blog: Using Org mode table for calculating RAGBRAI training actual vs. planned mileage https://davemq.github.io/2026/02/24/ragbrai-training-actuals-vs-plan.html

#ragbrai #emacs #org #orgmode

New blog post: A Rofi workspace switcher for Sway https://davemq.github.io/2026/02/24/rofi-workspace-switcher-sway.html

#sway #rofi

@cidra I've only ever used #Toolbox to get older versions of #Fedora running because they still have #Python2 .But I see your point!

I'm writing an #Emacs package. It's complete enough for a first release, but I should really include an Info file. I'm far more familiar with writing Org documents than TeXinfo documents, so I think I'll be writing the Info as an Org document, then exporting it as TeXinfo or Info.

#TeXinfo #emacs #org #orgmode

I finished day 6 part 2 of #aoc2025. While I initially tried parsing forward through the lines of input, I eventually moved to parsing right to left. And again used reduce() to get the results of the problems.

#AdventOfCode2025 #AdventofCode

I had fun applying reduce() to lists to solve day 6 part 1 of #aoc2025. I learned about reduce() while porting machine learning code to Linux on IBM Power many years back, but I've seldom used it.

#AdventofCode #AdventOfCode2025

I finished day 5 part 2 of #aoc2025. My first approach left me with overlapping ranges, so I had to revamp it. The working solution was much more elegant in addition to working!

#AdventofCode #AdventOfCode2025

I finished day 5 part 1 of #aoc2025 in #Python. I wanted to use a big set of integers for the fresh ingredients and check for membership, but the range was too large for the #Python interpreter to handle. I also explored expanding and coalescing ranges, but in the end didn't need to implement it.

#AdventofCode2025 #AdventOfCode

I implemented day 4 part 2 of #aoc2025. I refactored the day 4 part 1 code to use directly in the part 2 solution. I learned how to replace characters within #Python strings, i.e. create a new string with slices of the original and the character you want in the particular position.

#AdventOfCode2025 #AdventOfCode

I solved day 4 part 1 of #aoc2025. My algorithm to find neighbors was good, and my counting was good, but my result was too high. Eventually I figured it out

#AdventOfCode2025

I finished day 3 part 2 of #AdventOfCode2025. I came up with a nice recursive solution with a little optimization.

#aoc2025

#b4 #linux Having gotten through using "b4" once now, I generally like it. It pulls together all the things needed for sending a patch to one of the Linux development groups, making it much more difficult to forget something!

#b4 #emacs #magit #python

I installed "b4" using "pipx", which sets up a virtual environment for the "b4" code and its dependencies. I looked for a way to set TMPDIR to the current working directory when running "b4".

After some research, I found I could create a "foo.pth" file in the pipx virtual environment's site-pakages directory, which a 1 liner:

import os; os.environ['TMPDIR'] = os.getenv('PWD')

This did the trick! b4 prep --edit-cover now works with emacsclient and Magit!

5/5

#b4 #emacs #magit #linux

I'm not sure why Magit really cares. I tried using advice to get around this, but didn't quite get it to work.

Looking at the "b4", I found the Python code for editing the cover letter. It creates a temporary directory and then "COMMIT_EDITMSG" in that directory. Looking at the documentation for tempfile.TemporaryDirectory suggested using an environment variable like TMPDIR. Okay, this is another idea, set TMPDIR to the current working directory.

4/5

#b4 #emacs #magit

The file is showing in Emacs. I tried to exit the emacsclient session with C-x #, and it asked if I wanted to create the directory where the file lived. Sure, I say. But at this point its useless. So I looked for ways to work around or fix this problem. With Emacs, I suspect Magit was involved. Looking at the source code, I found the places where this error was triggered. There was no easy way to get around this, other than put the file in the repository directory tree.

3/5

#b4 #emacs #magit #linux

"b4 prep --edit-cover" uses the EDITOR environment variable to figure out which editor to use. Apparently the default for bash on Fedora 42 is to set EDITOR to /usr/bin/vim. While I'm quite versed in vi (the predecessor to vim), I prefer to use Emacs. So I set EDITOR to emacsclient and tried again. But this time I got an error about the file not being in a Git repository, and b4 said the file hadn't changed.

2/5

#b4 #emacs #magit #linux

I recently found a small typo in some Linux kernel documentation, and posted a patch to get it fixed. There were some problems with the patch, and it was suggested I use a tool called "b4" https://b4.docs.kernel.org/en/latest/index.html. I started using it for my next patch revision, but ran into a snag when editing the patch cover file.

1/5