It might be more expected for you but I’m going to differ.
for an article (or a link to a image), it takes you there instead.
… and then you can’t get to the discussion.
The RSS-2.0 definition of <link> is
The URL to the HTML website corresponding to the channel.
so clearly, it should point to the lemmy post. No other RSS feed that I know of has this problem.
Fortunately, emacs can flex around this, but duh! Where can I raise a bug report?
OK, more than wow! Probably the most helpful, in-depth and up to date coverage of this topic I’ve seen in 40 years of barely scratching the surface of emacs. Thank you!
Wow! Just wow!
I find the various linters and checkers a bit too intrusive while I’m trying to code - I prefer to just have a check when I stop fiddling with the code and save it. So I have these checks run in after-save-hook - if there are errors, I get a popup otherwise nothing and all is good:
;; ** syntax checking on file save:
(defun bh/check-syntax ()
"Check syntax for various languages."
(when (eq major-mode 'emacs-lisp-mode)
(ignore-errors (kill-buffer byte-compile-log-buffer))
(let ((byte-compile-warnings '(not free-vars obsolete unresolved)))
(unless (byte-compile-file buffer-file-name)
(pop-to-buffer byte-compile-log-buffer))))
(when (eq major-mode 'sh-mode)
(compile (format "bash -n %s && shellcheck -f gcc %s" buffer-file-name buffer-file-name) t))
(when (eq major-mode 'ruby-mode)
(compile (format "ruby -c %s" buffer-file-name) t))
(when (eq major-mode 'python-mode)
(compile (format "python -B -m py_compile %s" buffer-file-name) t))
(when (eq major-mode 'awk-mode)
(compile (format "AWKPATH=$PATH gawk --lint --source 'BEGIN { exit(0) } END { exit(0) }' --file %s" buffer-file-name) t)))
(add-hook 'after-save-hook #'bh/check-syntax)
I don’t work much with json files but I daresay the idea could be extended to them. Sorry about the crappy elisp.
I followed up on github as you suggested and a very nice young man took a look at it and said that the code already does work the right way (at least the way I and their little poll think it should work). But, it turns out that the fix (from 2021) has not been deployed - it’s to be in the next release.
So I don’t know what will happen now - I’ll continue to use my workaround, so I’m happy enough.