From: Max Nikulin <email@example.com> To: firstname.lastname@example.org Subject: LinkRemark Firefox extension approved for addons.mozilla.org Date: Fri, 19 Nov 2021 00:01:17 +0700 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <87sg7spthm.fsf@localhost> A year ago I announced LinkRemark browser extension to save metadata of web pages as notes in Org Mode. New version is available in Firefox catalog (It is not published to Chrome store, the only option is still to load unpacked extension.): https://addons.mozilla.org/firefox/addon/linkremark/ Capture is not ideal and notes require edits. Some subset of schema.org microdata embedded into HTML markup is extracted now. I addressed some issues from comments to first release. Example: #+begin_src org ,* Link: Karl Voit: UOMF: Managing web bookmarks with Org Mode :PROPERTIES: :DATE_ADDED: [2021-09-28 Tue 12:15] :END: - Link URL :: [[https://karl-voit.at/2014/08/10/bookmarks-with-orgmode/]] - Link text :: Karl Voit: UOMF: Managing web bookmarks with Org Mode ,#+begin_quote author: Karl Voit published: [2014-08-10 Sun] ,#+end_quote On the page ,** Adam Porter — org-almanac :PROPERTIES: :DATE_ADDED: [2021-09-28 Tue 12:15] :LAST_MODIFIED: [2021-09-18 Tue 01:23] 09/18/2021 01:23:46 :END: - URL :: [[https://alphapapa.github.io/org-almanac/]] - title :: org-almanac - author :: Adam Porter - referrer :: [[https://www.google.com/]] #+end_src On 26/12/2020 20:49, Ihor Radchenko wrote: > > Another idea would be providing a callback from elisp to browser (I am > not sure if it is possible). org-capture-ref has a mechanism to check if > the link was captured in the past. If the link is already captured, the > information about the link location and todo-state can be messaged back > to the browser. I looked into org-capture-ref code and stole the idea to use an external tool to search in Org files. LinkRemark now can ask native messaging application helper whether URLs are already known. Proof of concept: https://github.com/maxnikulin/burl > For the scientific publications, the key point is usually getting > DOI/ISBN. At least apparent DOI and links should be recognized now, however with no additional actions. > Also, do you pass any of the parsed metadata to org-protocol? If you do, > it would be trivial to get it into capture templates on Elisp (and > org-capture-ref) side. Actually it was possible even a year ago to specify "object" format instead of "org" and to get extracted metadata in JSON format wrapped into org-protocol URI. I can not say that structure of data has been stabilized and I would not change it again. > For example, I tweaked title of captured > github issues to include "issue#", which helps to distinguish such pages > from individual repo bookmarks. In particular case of GitHub it is better to fetch raw data curl -H 'Accept: application/vnd.github.v3+json' 'https://api.github.com/repos/yantar92/org-capture-ref/issues/2' On 26/12/2020 05:11, Samuel Wales wrote: > for > example, you could have sets of tabs, selected by right click in > firefox, to save to a bunch of org entries. then you could load that > particular set of entries into firefox whenever you want. and you > could keep notes on each page and move the entries wherever you want. > this would be useful for such things as "i am researching rice > cookers; these are my tabs, but i don't want them cluttering firefox > and i want them with my org notes and to make notes on them and will > re-load them into firefox when i want to revisit" I implemented capture of highlighted tab group for Firefox. No ready to use solution is provided to restore it. It is just a tree of Org headings. > now if i can only debug the extra-blank-lines-in-capture problem. I hope, a kind of hack to avoid excessive newlines in selected text would not be a source of problems. Clipboard managers might be a trouble though.
next prev parent reply other threads:[~2021-11-18 17:08 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-25 12:44 Yet another browser extension for capturing notes - LinkRemark Maxim Nikulin 2020-12-25 14:19 ` Ihor Radchenko 2020-12-26 11:49 ` Maxim Nikulin 2020-12-26 13:49 ` Ihor Radchenko 2020-12-27 12:18 ` Maxim Nikulin 2021-11-18 17:01 ` Max Nikulin [this message] 2020-12-25 14:26 ` Russell Adams 2020-12-25 22:11 ` Samuel Wales 2020-12-26 9:16 ` Maxim Nikulin 2022-01-17 2:29 ` Samuel Wales 2022-01-18 1:03 ` Samuel Wales 2022-01-18 5:43 ` Samuel Banya 2022-01-18 10:57 ` Max Nikulin 2022-01-18 10:34 ` Max Nikulin 2022-01-19 3:28 ` Ihor Radchenko 2022-01-19 8:45 ` András Simonyi 2022-01-19 10:00 ` Ihor Radchenko 2022-01-19 10:58 ` András Simonyi 2022-01-19 11:42 ` Ihor Radchenko 2022-01-20 0:23 ` Samuel Wales 2022-01-20 12:16 ` Org mode and firefox tabs (feature request) Max Nikulin
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org' \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: LinkRemark Firefox extension approved for addons.mozilla.org' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).