aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorYann Herklotz <git@yannherklotz.com>2022-07-09 20:08:26 +0100
committerYann Herklotz <git@yannherklotz.com>2022-07-09 20:08:26 +0100
commitaa9811f46fe2912113007cd8486617808a89d5c9 (patch)
tree1994b0f09af4b7ed54f6405f7427c0554ad3bc53
parent20e11bdcb97bfa956d2855c8f161a1a8846fde74 (diff)
downloadyannherklotz.com-aa9811f46fe2912113007cd8486617808a89d5c9.tar.gz
yannherklotz.com-aa9811f46fe2912113007cd8486617808a89d5c9.zip
Add links
-rw-r--r--content.org13
1 files changed, 9 insertions, 4 deletions
diff --git a/content.org b/content.org
index f05ada0..959163c 100644
--- a/content.org
+++ b/content.org
@@ -86,10 +86,10 @@ associated with that bib entry into the right folder and named it after the key
bib file. I used to do this manually, but it took quite a bit of work and seemed like something I
should automate.
-The first step is therefore just figuring out how to get the ID of the current entry when in the
-ebib index buffer (the one that lists all the bib entries). I know of a function which can already
-copy the key when hovering over the entry, which is bound to ~C k~, so we can have a look at what
-function is executed when pressing these keys, using the lovely builtin src_emacs-lisp[:exports
+The first step is just figuring out how to get the ID of the current entry when in the ebib index
+buffer (the one that lists all the bib entries). I know of a function which can already copy the
+key when hovering over the entry, which is bound to ~C k~, so we can have a look at what function is
+executed when pressing these keys, using the lovely builtin src_emacs-lisp[:exports
code]{describe-key} function, and then at how this function is implemented by using
src_emacs-lisp[:exports code]{describe-function}, which also gives you the source code for the
function (which you can obviously modify as you want and reevaluate to change the behaviour at
@@ -232,6 +232,11 @@ ls *.pdf | xargs -n1 rmapi put
which will try to upload all my files every time I call it, but nicely enough it fails quickly
whenever the file already exists on the Remarkable.
+
+*** Links
+
+- [[https://news.ycombinator.com/item?id=32038264][Hacker News]]
+- [[https://old.reddit.com/r/emacs/comments/vv8ndl/ebib_downloading_academic_papers_automatically/?][Reddit]]
** TODO About the Promise of Performance from Formal Verification
When one thinks about formal verification, one normally associates this with sacrificing performance