summaryrefslogtreecommitdiffstats
path: root/2022/talks/eev.md
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2022-09-30 15:59:56 -0400
committerSacha Chua <sacha@sachachua.com>2022-09-30 15:59:56 -0400
commit67f0f1c500091db27a69cb3a05fffd20c137d6e4 (patch)
tree22f66de124999dca2f6d965795c8135d747aa6eb /2022/talks/eev.md
parent0e44a3f1f7dbc27c92aa51aa50e898b163d56ac3 (diff)
downloademacsconf-wiki-67f0f1c500091db27a69cb3a05fffd20c137d6e4.tar.xz
emacsconf-wiki-67f0f1c500091db27a69cb3a05fffd20c137d6e4.zip
Add 2022 talks
Diffstat (limited to '2022/talks/eev.md')
-rw-r--r--2022/talks/eev.md57
1 files changed, 57 insertions, 0 deletions
diff --git a/2022/talks/eev.md b/2022/talks/eev.md
new file mode 100644
index 00000000..b11e7b2c
--- /dev/null
+++ b/2022/talks/eev.md
@@ -0,0 +1,57 @@
+[[!meta title="Bidirectional links with eev"]]
+[[!meta copyright="Copyright &copy; 2022 Eduardo Ochs"]]
+[[!inline pages="internal(2022/info/eev-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-generate-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Bidirectional links with eev
+Eduardo Ochs
+
+[[!inline pages="internal(2022/info/eev-before)" raw="yes"]]
+
+Consider the two sexps below:
+
+ (code-c-d "foobar" "/tmp/foo/bar/" :anchor)
+ (code-c-d "fb" "/tmp/foo/bar/" :anchor)
+
+Each one of them defines several "short hyperlink" functions. After
+running them the three sexps below are roughly equivalent:
+
+ (find-file "/tmp/foo/bar/plic.txt")
+ (find-foobarfile "plic.txt")
+ (find-fbfile "plic.txt")
+
+The "`code-c-d`"s above also define functions with even shorter names
+&#x2013; `find-foobar` and `find-fb` - that point to "anchors" in files in
+the directory `/tmp/foo/bar/`. The three sexps below are roughly
+equivalent -
+
+ (find-fline "/tmp/foo/bar/plic.txt" "«bletch»")
+ (find-foobar "plic.txt" "bletch")
+ (find-fb "plic.txt" "bletch")
+
+Until feb/2022 the only way that I had to produce these hyperlinks to
+anchors quickly required a LOT of muscle memory&#x2026; I had to type this,
+
+ M-1 M-h M-w M-h M-h 9*<down> M-h M-2 M-h M-y M-h M-- M-h M-w M-k
+
+where the number of "`<down>`"s depended on whether I preferred
+`find-foobar` of `find-fb` - i.e., of on what is my preferred "code"
+for the "directory" `/tmp/foo/bar/`; either "`foobar`" or "`fb`".
+
+In this presentation I will show a much better way to generate short
+hyperlinks to anchors and push these short hyperlinks to the kill
+ring, and how I use that to create bidirectional hyperlinks between my
+notes on a language $LANGUAGE and programs written in that language.
+
+For more info see [this page](http://angg.twu.net/emacsconf2022-kla.html).
+
+
+
+[[!inline pages="internal(2022/info/eev-after)" raw="yes"]]
+
+[[!inline pages="internal(2022/info/eev-nav)" raw="yes"]]
+
+[[!taglink CategoryEEV]]