Loglink
November 30th, 2025
Update: logpoints solves this better than “loglinks”.
I wish there was a program to teach me. I don’t want Clippy-style interrupts for a longer concept like debuggers. Weirdly, you need to market the debugger to me, just as VSCode was marketed to me. When I’m “lean forward”, I don’t want “lean back” lessons.
I log when I should debug. It’s just a habit. However, I find myself swapping back and forth between IDE and a tailing terminal session, copy/pasting log statement prefixes:
- Swapping to terminal and searching for my log statement
- Looking at adjacent statements and swapping back to IDE to find the log statement
Loglink should simplify this:
- Cmd+click a log statement to go to the latest log line
- Cmd+click on a log line to go to the matching code
It feels relatively straightforward:
- Code → Logs: format string → log regex
- Logs → Code: index format strings, attempt to match
- Notify the developer when there are duplicate format strings
I can use language servers to find references or call hierarchies to logging.
log.Printf("hello %s", )
slog.Info("hello", "audience", audience)
// 2022/11/08 15:28:26 INFO hello audience=world
Loglink could look into your code or your Makefile to guess where the logging file is.