StrangeAstronomer

joined 1 year ago
[–] StrangeAstronomer@lemmy.ml 17 points 1 week ago (1 children)

voidlinux: gave me much better battery life - I assume because it starts as a minimal system and one adds only the essentials to do the job - compared to the soup-to-nuts distros that pile everything in so that newbies are acccomodated. Of course, the voidlinux approach needs more linux skills - but it's not that hard and the doco is great.

Also, I love the back to basics runit init system and runsv service runner (I'm old so I like that stuff) and the ultra fast xbps packaging system.

[–] StrangeAstronomer@lemmy.ml 13 points 1 month ago

Thanks (to all the authors) for your hard work and contributions.

[–] StrangeAstronomer@lemmy.ml 2 points 3 months ago

BTW - thanks for Mistral. Another tool in the box!

[–] StrangeAstronomer@lemmy.ml 2 points 3 months ago (1 children)

Quite right!

You need to take it all (AI or internet searches) with a huge pinch of salt. Even ye olde text books were not infallible and often out of date, so sodium chloride was also required even then.

The code either works or it doesn't - it's all in the testing. If you deploy AI suggestions without thought you deserve the consequences.

[–] StrangeAstronomer@lemmy.ml -4 points 3 months ago (7 children)

so just use chatgpt or gemini - pretty sure they sucked in all of reddit to form their KB

[–] StrangeAstronomer@lemmy.ml 2 points 4 months ago

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.

[–] StrangeAstronomer@lemmy.ml 5 points 4 months ago

So he's a journalist </s> Thanks for the warning, saved me a read.

[–] StrangeAstronomer@lemmy.ml 2 points 4 months ago (2 children)

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 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?

 

Most entries in lemmy's RSS feed have a that points to the relevant lemmy post eg

Title: Any DE or distro without touch support?
Author: https://lemmy.ml/u/tarius
Date: Wed, 15 May 2024 01:24:59 AEST
Feed: Lemmy - linux
Link: https://lemmy.ml/post/15632012

That makes sense - clicking the link takes me to the conversation.

Other entries however, include a link to the subject of the conversation eg

Title: Wayland usage has overtaken X11
Author: https://lemmy.world/u/KISSmyOSFeddit
Date: Tue, 14 May 2024 03:30:46 AEST
Feed: Lemmy - linux
Link: https://lemmy.world/pictrs/image/a71c1b49-fb63-420d-8afc-d40661ffd79c.png

The feed I'm using is https://lemmy.ml/feeds/c/linux.xml

This is unfortunate as clicking the link in my reader (elfeed) does not show the conversation - I rely on the to take me there.

elfeed being built in elisp in emacs, I have been able to concoct a fix especially for lemmy - but it really feels like a bug in lemmy as no other feed needs it. Where can I report it or discuss it?

[–] StrangeAstronomer@lemmy.ml 4 points 4 months ago

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!

[–] StrangeAstronomer@lemmy.ml 1 points 4 months ago

Wow! Just wow!

[–] StrangeAstronomer@lemmy.ml 1 points 4 months ago

Another approach entirely is to use pam_mount(8) which can automatically mount a disc on login. I use it to mount /home/$USER (obviously this couldn't be used to mount the root fs !!)

 

... more an annoyance really, and not elfeed's fault at all but ...

[first posted on reddit/r/emacs but probably more interesting here]

lemmy RSS feeds (such as "https://lemmy.ml/feeds/c/emacs.xml") often (but not always) have mis-guided "Link:" elements which target an external link, an image file or other material instead of the lemmy post itself. Consequently, hitting 'b' elfeed-search-browse-url may send one on a surprising if not always useful journey.

eg

Title: Keymacs, a program to generate Emacs keybindings | Plain DrOps
Author: https://feddit.de/u/DrOps
Date: Tue, 23 Apr 2024 23:35:25 AEST
Feed: Lemmy - emacs
Tags: emacs, lemmy
Link: https://plaindrops.de/blog/2024/keymacs/

submitted by DrOps to emacs
8 points | 2 comments
https://plaindrops.de/blog/2024/keymacs/

In this case, the link to lemmy itself is in the "2 comments" => https://lemmy.ml/post/14798221

Here's a little hook to fix it up - it also marks the entry with the tag 'lemmy-fixed' ...

(defun elfeed-fix-lemmy-link (entry)
  "Fix lemmy.ml RSS feed links in elfeed."
  (when-let ((url-base-regexp "https://lemmy\\.ml/")
             (feed (elfeed-entry-feed entry))
             (feed-url (elfeed-feed-url feed))
             ((string-match-p (concat url-base-regexp "feeds/c/") feed-url))
             (entry-link (elfeed-entry-link entry))
             (link-url-regexp (concat url-base-regexp "post/[0-9]+"))
             ((not (string-match-p link-url-regexp entry-link))))
    (when-let ((content (elfeed-deref (elfeed-entry-content entry))))
      (let ((lines (split-string content "\n")))
        (dolist (line lines)
          (when (string-match link-url-regexp line)
            (let ((post-link (substring line (match-beginning 0) (match-end 0))))
              (setf (elfeed-entry-link entry) post-link)
              (elfeed-tag entry 'lemmy-fixed)
              (message "Fixed lemmy link in elfeed: %s" post-link)
              (cl-return))))))))
(add-hook 'elfeed-new-entry-hook #'elfeed-fix-lemmy-link)

Thanks to u/karthik for getting me started with this. The crappy elisp is mine not his (roast me!)

view more: next ›