ebuku VS grasp

Another option is to use something like ebuku.

i remember looking at that Google style guide a while back, and not being enthused about it. It's true my style across my POSIX scripts isn't yet entirely consistent, as i'm new to writing POSIX shell scripts, and am still working out what's best for me, as the person who's going to be the primary maintainer. Still, i believe my style to be basically consistent within a given script. Having been programming for a few decades now - although i only started coding-for-pay in the late 90s, starting with Perl - i've developed my own preferences regarding code layout (such as in my ELisp packages, e.g. Ebuku), and nowadays take the approach: I'll follow others' style in others' projects, and will generally try to follow common style standards in my own projects, but will modify them as needed when i find they're not conducive to my work.

Well, indeed, i certainly wasn't expecting you to do so! But i already have more than enough volunteer FOSS stuff on my plate as it is (e.g. Ebuku, pulseaudio-control, s6-man-pages, execline-man-pages and guides, amongst various other things), and not using mold with gcc 11 is no problem for me at this point. So i've just noted the issue with the patch on the wiki page, and the patch will have to be updated by someone for whom it's more important.

Fair point. Still, as a FOSS dev myself, i feel that the title might serve as a useful reminder to a number of their readers. Particularly when so many people use FOSS developed by large corporations, and see themselves as 'customers' entitled to 'responsive service'[a] that those of us who aren't a corporation aren't necessarily in a position to provide (even if we do try to provide 'best effort'). The contents of the screencap for one of my FOSS projects is not random. :-)

Based on your post headline, i was going to suggest my Ebuku package, an Emacs frontend to the buku Web bookmark manager - i use it myself, and it has support for both tags and comments on links. But it doesn't meet your requirement of capturing from the browser; i copy-and-paste the URL from the browser into an Emacs prompt.

Me asking for actual data about the the extent to which various arguments to the -O flag is me "trying to argue with you" and "having a bad day"? Er, what? i'm saying your assertions might well be correct, but as a dev myself (here's some of the stuff i've been doing during our exchange), i want some concrete data in support of this, because "premature optimisation is the root of all evil" (cf. "Rob Pike's 5 Rules of Programming").

Not beyond playing around a bit with Squeak. i like Smalltalk's message-passing approach to OO, and i like how thoroughly modifiable the environment is. i haven't spent enough time to know how easily it can interface with the system on which the image is running; one of the things i like about Emacs is that, in addition to being so modifiable itself, it provides lots of support for interacting with software outside of itself. (E.g. i wrote an Emacs package which provides an Emacs UI for the CLI-based buku Web bookmark manager: Ebuku.)

There is an extension called Grasp which acts as a web clipper, you highlight the relevant part & add a tag. It's pretty great. But it only appends to a file. https://github.com/karlicoss/grasp

[1] https://beepb00p.xyz/grasp.html witch is another small example of automation to a certain extent.

I use grasp to capture links from the browser. It also captures any text you have selected on the page and you can add tags and a description.

I'm not using browser bookmarks anymore, instead I am just using plaintext files (org-mode in my case). When I want to make a bookmark I use grasp [0] to simply capture in in the 'links.org' file, possibly with some notes/selected text and tags. Now and then I would skim through this file, refile the most important/interesting things to other files, and put the rest into 'later.org' (things I might never look at again :) ). The upside is that bookmarks become alive this way, you can easily edit them, add more context, interlink, etc.

I also mirror saved items from other services (e.g. reddit/HN/twitter/instapaper) as plaintext org-mode files, via orger [1].

Then, all of this feeds into Promensia [0] [1], a tool I wrote that serves as a web browsing copilot and surfaces my bookmarks (or any relevant links, really) when I'm browsing.

That way I don't need to worry about spending too much time processing bookmarks and that I'd never read them, I can just read the most interesting stuff and the rest is searchable (so I use it as a knowledge base/personal search engine), and surfaces in my browser via Promnesia, so I can find out if I have some relevant information in my knowledge base without actively searching. I don't need to suffer from vendor lock-in (even if the service/tool is open, migration is always painful), I can just add another adapter to my system and feed it into Promnesia/Orger.

[0] https://github.com/karlicoss/grasp#readme

[1] https://beepb00p.xyz/orger.html

[2] https://beepb00p.xyz/promnesia.html

[3] https://news.ycombinator.com/item?id=23668507

In tech terms, behind the scene, yes is complex, but in practical terms just see https://github.com/karlicoss/grasp/ :-)

Grasp (https://addons.mozilla.org/en-US/firefox/addon/grasp and https://beepb00p.xyz/grasp.html for the system/python listener) and Promnesia (https://beepb00p.xyz/promnesia.html) help me "import" quick bookmarks to org-mode (I can't use org-protocol with firejail, at least I have to tweak firejail and I never tried to do so). They demand a small effort (perhaps a quick python venv somewhere in the home to remain self-contained) but they are helpful.

for reading, I'm currently trying to set up elfeed and come sort of capture like grasp. My idea is to use org-mode to also log those things (kinda) effortless.