Kangaroo Flat, Australia
Peter Prevos: Water engineer, social scientist and reality-disruptor
From Peter Prevos to ~protesilaos/denote
Hi Saša, > ... I'm interested if > some tips how to provide a "framework" to assist in general > search > feature. Namely, besides in looking for specific notes based on > its > signature and the context it provides, we would like to be able > to > filter our notes on keywords (aka tags) as well as the note's > content, > resembling full-text search (fts) which is provided by
From Peter Prevos to ~protesilaos/denote
Hi Prot et al., I noted that a search for backlinks yields results that are not technically links. As I am experimenting with saving the complete Denote archive as a JSON file for visualisation, I noted that the backlinks search also returns hits on my notes with embedded JSON snippets, e.g.: {"id":"20190402T054953","name":"Adams (1994): The Knot Book"}. Denote now suggests a link from the note holding this JSON to the referenced note. I brute-force corrected the denote--retrieve-location-in-xrefs
From Peter Prevos to ~protesilaos/denote
Hi Stephen, I also used the :missing-only option a bit in pretty much the same way you did. Prot, you previously mentioned that you got false positives. Not sure what method you used previously. I wrote a function that lists all static links in an Org file. I am unsure how dynamic blocks work, but surely this function can be plumbed into the denote-org-dblock--files function to exclude these matches from consideration. (defun denote-org-dblock--extract-static-links () "List all Denote links outside a dynamic block." (let ((link-ids '()))
From Peter Prevos to ~protesilaos/ef-themes
Dear fellow Denoters, I am working on the denote-explore package, which includes visualisation tools for Denote I am writing some functions to save the structure of the Denote files as two JSON files. One with metadata about each note and one with all links. The function below gives me grief. I am using the denote-id-only-link-in-context-regexp variable to find all links in files matching regex. However, using this variable gives me a parse error. Also the denote-org-link-in-context-regexp variable
From Peter Prevos to ~protesilaos/ef-themes
Hi Prot, Glad you like my little folly. Theme-buffet is proper food compared to my fast-food version. Happy for you to add a link to the Ef Themes manual. I am not releasing this formally and will leave it on GitHub as is. Regards P:)
From Peter Prevos to ~protesilaos/ef-themes
Hi folks, I just created a frivolous minor mode to randomly change between Ef Themes. https://github.com/pprevos/disco-ef-themes P:) -- Dr Peter Prevos
From Peter Prevos to ~protesilaos/denote
Hi Prot, I have not yet written release notes for anything I develop. Perhaps it is a habit I should start. P:)
From Peter Prevos to ~protesilaos/denote
Hi folks, I have just updated the denote-explore package: https://github.com/pprevos/denote-explore It does three things: 1. Summary statistics: Count and visualise keywords and note types 2. Random walks: Generate new ideas using serendipity 3. Network visualisation: Visualise your Denote network of links It contains a rudimentary network visualisation function, relying on the R language. I will need some D3.js expertise to improve the
From Peter Prevos to ~protesilaos/denote
Hi Prot, Perhaps a section in the Denote manual covering exporting Org and Markdown files would be useful. You can use this as you see fit: Exporting Denote notes ────────────────────── When exporting Denote notes to, for example, a website or PDF, there is a risk that the same file name is used with a new extension. This can be problematic because it creates files with
From Peter Prevos to ~protesilaos/denote
Hi Nobiot and relict007, I am using the Melpa version and just checked the GitHub version. Apparent I wasted my time worrying ... :) Please ignore my email. Perhaps the text and code I wrote about exporting would be good to add to the manual to prevent the duplicate ID issue in the first place. Apologies to waste your time.