tec
/
this-month-in-org
1
0
Fork 0
Code Issues Pull Requests Releases Activity

Publish update based on 3928c66

This commit is contained in:
TEC 2024-01-12 13:08:14 +08:00
parent 59bca70525
commit 596af0ec31
Signed by: tec
SSH Key Fingerprint: SHA256:eobz41Mnm0/iYWBvWThftS0ElEs1ftBr6jamutnXc/A
35 changed files with 232 additions and 232 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
2021-04-26-Welcome.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 11:13 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Welcome</title>
@ -114,7 +114,7 @@ This should help ensure nothing slips through the cracks of the <span class='acr
</p>
<figure id="org6cb1380">
<figure id="orgdd6cf1f">
<img src="figures/screenshot-of-updates-orgmode-org.png" alt="screenshot-of-updates-orgmode-org.png" class="invertible">
<figcaption><span class="figure-number">Figure 1: </span>A screenshot of <a href="https://updates.orgmode.org/">updates.orgmode.org</a></figcaption>
@ -148,7 +148,7 @@ their glory!
</p>
<figure id="org649b591">
<figure id="org8192379">
<img src="https://github.com/larsmagne/meme/raw/master/images/Grandma-Finds-The-Internet.jpg" alt="Grandma-Finds-The-Internet.jpg" style="height:16em">
<figcaption><span class="figure-number">Figure 2: </span>Org mode discovers the internet</figcaption>
@ -169,7 +169,7 @@ environments, but why leave inline LaTeX fragments out? We'll, they're now in.
</p>
<figure id="orge03698e">
<figure id="org2f642e3">
<img src="figures/org-edit-special-latex-fragment.png" alt="org-edit-special-latex-fragment.png" class="invertible">
<figcaption><span class="figure-number">Figure 3: </span>Running <code>org-edit-special</code> on an inline LaTeX fragment</figcaption>
@ -187,7 +187,7 @@ at last.
</p>
<figure id="org66618e4">
<figure id="org947274b">
<img src="figures/org-startup-num-and-levels.png" alt="org-startup-num-and-levels.png" class="invertible">
<figcaption><span class="figure-number">Figure 4: </span>Opening a buffer with the new <kbd>num</kbd> and <kbd>show2levels</kbd> startup options</figcaption>

2
2021-04-26-Welcome.org
View File

@ -1,4 +1,4 @@
# Created 2024-01-11 Thu 11:13
# Created 2024-01-12 Fri 13:05
#+title: Welcome
#+date: 2021-04-26
#+author: TEC

4
2021-04-30-export-plot.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 11:13 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>April 2021</title>
@ -71,7 +71,7 @@ If you've been thinking about <a href="https://orgmode.org/contribute.html">gett
give it a shot!
</p>
<div class="info" id="org53f40b0">
<div class="info" id="org315f273">
<p>
<b>Ways you can contribute to the project</b>
</p>

2
2021-04-30-export-plot.org
View File

@ -1,4 +1,4 @@
# Created 2024-01-11 Thu 11:13
# Created 2024-01-12 Fri 13:05
#+title: April 2021
#+date: 2021-04-30
#+author: TEC

6
2021-05-31-async.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 11:13 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>May 2021</title>
@ -254,7 +254,7 @@ But a dream within a dream?
</details>
<figure id="org53cc3ef">
<figure id="org9f879d9">
<img src="figures/org-verses-example-poem-dream-within-dream.png" alt="org-verses-example-poem-dream-within-dream.png" class="invertible">
<figcaption><span class="figure-number">Figure 1: </span>A short Poe-em</figcaption>
@ -266,7 +266,7 @@ But a dream within a dream?
<div class="outline-text-2" id="text-easy-zero-width">
<p>
Occasionally you may run into annoyances when you wish to have two different Org
elements right next to each other (no space) &#x2014; for example, <b>emph</b>​asising part of
elements right next to each other (no space) &#x2014; for example, <b>emph</b>asising part of
a word or putting a currency symbol immediately before an inline source block.
</p>

4
2021-05-31-async.org
View File

@ -1,4 +1,4 @@
# Created 2024-01-11 Thu 11:13
# Created 2024-01-12 Fri 13:05
#+title: May 2021
#+date: 2021-05-31
#+author: TEC
@ -130,7 +130,7 @@ blocks now support four new attributes:
* Easy zero-width spaces with Org
Occasionally you may run into annoyances when you wish to have two different Org
elements right next to each other (no space) --- for example, *emph*​asising part of
elements right next to each other (no space) --- for example, *emph*asising part of
a word or putting a currency symbol immediately before an inline source block.
The best solution to this in Org is zero-width spaces. As such, I've found it

2
2021-05-31-async.txt
View File

@ -165,7 +165,7 @@ Easy zero-width spaces with Org
Occasionally you may run into annoyances when you wish to have two
different Org elements right next to each other (no space) — for
example, *emph*​asising part of a word or putting a currency symbol
example, *emph*asising part of a word or putting a currency symbol
immediately before an inline source block.
The best solution to this in Org is zero-width spaces. As such, I've

14
2021-06-34-relaxed.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 11:13 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>June 2021</title>
@ -51,7 +51,7 @@ You'll just have to stick around to hear about those in a future edition of <spa
</p>
<figure id="org557fa99">
<figure id="org4093549">
<img src="figures/dilbert-zenos-paradox.jpg" alt="dilbert-zenos-paradox.jpg" class="invertible">
<figcaption><span class="figure-number">Figure 1: </span>It's right around the corner, I swear!</figcaption>
@ -66,7 +66,7 @@ without giving it a name) &#x2014; for example with <kbd>[[Profound section]]</k
</p>
<figure id="org74fa200">
<figure id="org4e948be">
<img src="figures/org-latex-default-reference-to-sec.png" alt="org-latex-default-reference-to-sec.png" class="invertible">
<figcaption><span class="figure-number">Figure 2: </span>A LaTeX export of a simple document with a reference to both the first and second section. "2" what? Section 2, Table 2, Figure 2, &#x2026;</figcaption>
@ -79,7 +79,7 @@ I can set this to <kbd>\\cref{%s}</kbd> and then add <code class="src src-elisp"
</p>
<figure id="org3f0fbad">
<figure id="org92e84d8">
<img src="figures/org-latex-cref-reference-to-sec.png" alt="org-latex-cref-reference-to-sec.png" class="invertible">
<figcaption><span class="figure-number">Figure 3: </span>A LaTeX export of the same document, but now using <code>cleveref</code>. Note the change from "1" and "2" to "Section 1" and "Section 2".</figcaption>
@ -182,7 +182,7 @@ As you may have guessed from the fact this works without a LaTeX-specific
keyword, this works nicely in <span class='acr'>HTML</span> too 🙂.
</p>
<figure id="org0da3d6f">
<figure id="org87315cd">
<img src="figures/salvador-dali-persistence-of-memory.jpg" alt="salvador-dali-persistence-of-memory.jpg">
<figcaption><span class="figure-number">Figure 4: </span>A famous surrealist painting</figcaption>
@ -259,7 +259,7 @@ Year &amp; Painting<span class="org-warning">\\</span>
Org is nice and does the right thing<sup><span class='acr'>TM</span></sup> by including the caption at the top.
</p>
<figure id="org93d637a">
<figure id="orgb734b46">
<img src="figures/org-table-to-latex-example.png" alt="org-table-to-latex-example.png" class="invertible">
<figcaption><span class="figure-number">Figure 5: </span>Look ma, I put the caption in the right place.</figcaption>
@ -433,7 +433,7 @@ templates. Each template simply takes three components:
<p>
For example, I'm quite a fan of the <a href="https://ctan.org/pkg/koma-script"><span class='acr'>KOMA</span>-script</a> family. Should I want to add a
<kbd>kart</kbd> class (for: <b>k</b>​oma <b>art</b>​icle), I simply need to do something like the
<kbd>kart</kbd> class (for: <b>k</b>oma <b>art</b>icle), I simply need to do something like the
following:
</p>
<details id='preamble-content,code--2' class='code' open><summary><span class="lang">Emacs Lisp</span></summary>

4
2021-06-34-relaxed.org
View File

@ -1,4 +1,4 @@
# Created 2024-01-11 Thu 11:13
# Created 2024-01-12 Fri 13:05
#+title: June 2021
#+date: 2021-06-34
#+author: TEC
@ -221,7 +221,7 @@ templates. Each template simply takes three components:
3. A series of format strings to translate headings to LaTeX, with and without numbering
For example, I'm quite a fan of the [[https://ctan.org/pkg/koma-script][KOMA-script]] family. Should I want to add a
=kart= class (for: *k*​oma *art*​icle), I simply need to do something like the
=kart= class (for: *k*oma *art*icle), I simply need to do something like the
following:
#+begin_src emacs-lisp
(add-to-list 'org-latex-classes

2
2021-06-34-relaxed.txt
View File

@ -283,7 +283,7 @@ Preamble content
without numbering
For example, I'm quite a fan of the [KOMA-script] family. Should I
want to add a `kart' class (for: *k*​oma *art*​icle), I simply need to
want to add a `kart' class (for: *k*oma *art*icle), I simply need to
do something like the following:
┌────
│ (add-to-list 'org-latex-classes

64
2021-07-31-citations.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 11:13 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>July 2021</title>
@ -48,7 +48,7 @@ this post.
</p>
<figure id="orgcca163b">
<figure id="org6898ad8">
<img src="figures/celebrate-citations.svg" alt="celebrate-citations.svg" class="org-svg">
</figure>
@ -157,11 +157,11 @@ First we need to let Org know about this bibliography file (which must have a
<kbd>.bib</kbd>, <kbd>.bibtex</kbd>, or <kbd>.json</kbd> extension), which we do either via the <kbd>#+bibliography</kbd>
keyword, or the variable <code>org-cite-global-bibliography</code>.
</p>
<details id='org0ecc492' class='code' open>
<details id='org7282dd6' class='code' open>
<summary></summary>
<div class='gutter'><a href='#org0ecc492'>#</a>
<div class='gutter'><a href='#org7282dd6'>#</a>
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
<pre class="example" id="org0ecc492">
<pre class="example" id="org7282dd6">
#+bibliography: orgcite.bib
</pre>
@ -173,7 +173,7 @@ content! The basic citation syntax is as follows:
</p>
<figure id="orgca65a3c">
<figure id="orge96e856">
<img src="figures/citation-structure-basic.svg" alt="citation-structure-basic.svg" class="org-svg">
<figcaption><span class="figure-number">Figure 1: </span>The new citation syntax, for simple citations</figcaption>
@ -189,17 +189,17 @@ Finally, to insert a bibliography somewhere, we just need to insert the
<kbd>#+print_bibliography</kbd> keyword, like so:
</p>
<details id='org0dbc7b0' class='code' open>
<details id='org9348862' class='code' open>
<summary></summary>
<div class='gutter'><a href='#org0dbc7b0'>#</a>
<div class='gutter'><a href='#org9348862'>#</a>
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
<pre class="example" id="org0dbc7b0">
<pre class="example" id="org9348862">
#+print_bibliography:
</pre>
</details>
<div class="info" id="orgfd33b20">
<div class="info" id="orgf35d8be">
<style>.csl-entry{text-indent: -1.5em; margin-left: 1.5em;}</style><div class="csl-bib-body">
<div class="csl-entry"><a id="citeproc_bib_item_1"></a>org, mode, Citation Syntax, Mailing List, and Time Effort. 2021. “Elegant Citations with Org-Mode.” <i>Journal of Plain Text Formats</i> 42 (1): 2–3.</div>
</div>
@ -209,11 +209,11 @@ Finally, to insert a bibliography somewhere, we just need to insert the
<p>
So, to summarise, all one needs to get started is:
</p>
<details id='orgb188c35' class='code' open>
<details id='org13233ab' class='code' open>
<summary></summary>
<div class='gutter'><a href='#orgb188c35'>#</a>
<div class='gutter'><a href='#org13233ab'>#</a>
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
<pre class="example" id="orgb188c35">
<pre class="example" id="org13233ab">
#+bibliography: references.bib
[cite:@key]
#+print_bibliography:
@ -235,7 +235,7 @@ cite syntax:
</p>
<figure id="org9d1b0a1">
<figure id="org9f717cf">
<img src="figures/citation-structure-full.svg" alt="citation-structure-full.svg" class="org-svg">
<figcaption><span class="figure-number">Figure 2: </span>The new citations syntax, in full</figcaption>
@ -549,11 +549,11 @@ The citation processor is automatically selected based on
on a per-document basis via the <kbd>#+cite_export</kbd> keyword. Here, I shall use the <kbd>csl</kbd>
processor,
</p>
<details id='orgef702e6' class='code' open>
<details id='orgc3254e9' class='code' open>
<summary></summary>
<div class='gutter'><a href='#orgef702e6'>#</a>
<div class='gutter'><a href='#orgc3254e9'>#</a>
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
<pre class="example" id="orgef702e6">
<pre class="example" id="orgc3254e9">
#+cite_export: csl
</pre>
@ -564,11 +564,11 @@ With <code>org-cite-export-processors</code>, you can also set the bibliography
style by giving a triplet of parameters <code class="src src-elisp">(PROCESSOR BIBLIOGRAPHY-STYLE CITATION-STYLE)</code> instead of just the processor. You can also use this triplet of
values with the <kbd>#+cite_export</kbd> keyword
</p>
<details id='org27d1686' class='code' open>
<details id='orgcdfba21' class='code' open>
<summary></summary>
<div class='gutter'><a href='#org27d1686'>#</a>
<div class='gutter'><a href='#orgcdfba21'>#</a>
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
<pre class="example" id="org27d1686">
<pre class="example" id="orgcdfba21">
#+cite_export: processor bibliography-style citation-style
</pre>
@ -581,11 +581,11 @@ processor does not currently support any options, the BibLaTeX processor passes
options to a <code class="src src-LaTeX"><span class="org-keyword">\printbibliography</span></code> command, allowing for the
following:
</p>
<details id='orgfcd1a36' class='code' open>
<details id='org8e8611d' class='code' open>
<summary></summary>
<div class='gutter'><a href='#orgfcd1a36'>#</a>
<div class='gutter'><a href='#org8e8611d'>#</a>
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
<pre class="example" id="orgfcd1a36">
<pre class="example" id="org8e8611d">
#+print_bibliography: :section 2 :heading subbibliography
#+print_bibliography: :keyword abc,xyz :title "Primary Sources"
</pre>
@ -637,11 +637,11 @@ When exporting, you can set the style by providing a path to <span class='acr'>C
either absolute or relative to <code>org-cite-csl-styles-dir</code>. For example, if I
download <kbd>apa.csl</kbd> I can use it like so:
</p>
<details id='orgf358fb8' class='code' open>
<details id='orgb8c48a4' class='code' open>
<summary></summary>
<div class='gutter'><a href='#orgf358fb8'>#</a>
<div class='gutter'><a href='#orgb8c48a4'>#</a>
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
<pre class="example" id="orgf358fb8">
<pre class="example" id="orgb8c48a4">
#+cite_export: csl ~/Downloads/apa.csl
</pre>
@ -674,14 +674,14 @@ to a <kbd>.bib</kbd> file and automatically keep it in sync. I'd recommend insta
</p>
<figure id="org921e9a3">
<figure id="orge6b34f3">
<img src="figures/zotero-export-library.png" alt="zotero-export-library.png" class="invertible">
<figcaption><span class="figure-number">Figure 3: </span>Zotero library right click context menu, showing the export option</figcaption>
</figure>
<figure id="orgb2b8a82">
<figure id="org13fe646">
<img src="figures/zotero-export-options-prompt.png" alt="zotero-export-options-prompt.png" class="invertible">
<figcaption><span class="figure-number">Figure 4: </span>Zotero collection export dialog</figcaption>
@ -693,7 +693,7 @@ Zotero also features an easy way to install <span class='acr'>CSL</span> styles
</p>
<figure id="org8b26b0e">
<figure id="orgaff19e1">
<img src="figures/zotero-cite-styles-menu.png" alt="zotero-cite-styles-menu.png" class="invertible">
<figcaption><span class="figure-number">Figure 5: </span>Zotero <span class='acr'>CSL</span> style management within preferences</figcaption>
@ -718,11 +718,11 @@ directory.
To then use the citation style defined by <kbd>~/Zotero/styles/apa.csl</kbd> one can then
simply refer to <kbd>apa.csl</kbd> when using the <kbd>#+cite_export</kbd> keyword.
</p>
<details id='orgcf0ffb4' class='code' open>
<details id='org7322f9e' class='code' open>
<summary></summary>
<div class='gutter'><a href='#orgcf0ffb4'>#</a>
<div class='gutter'><a href='#org7322f9e'>#</a>
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
<pre class="example" id="orgcf0ffb4">
<pre class="example" id="org7322f9e">
#+cite_export: csl apa.csl
</pre>

2
2021-07-31-citations.org
View File

@ -1,4 +1,4 @@
# Created 2024-01-11 Thu 11:13
# Created 2024-01-12 Fri 13:05
#+title: July 2021
#+date: 2021-07-31
#+author: TEC

6
2021-08-38-roaming.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 11:13 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>August 2021</title>
@ -97,7 +97,7 @@ release of <a href="https://github.com/org-roam/org-roam-server">org-roam-server
</p>
<figure id="org0f2ebc7">
<figure id="orgccbd2c5">
<img src="figures/org-roam-graph-2d-overview.png" alt="org-roam-graph-2d-overview.png" class="doom-one" width="50%">
<figcaption><span class="figure-number">Figure 1: </span>org-roam-ui's 2D overview.</figcaption>
@ -128,7 +128,7 @@ graph view and the currently open roam file in Emacs. Furthermore, with
</p>
<figure id="org598637d">
<figure id="org6ade445">
<img src="figures/org-roam-ui-in-emacs.png" alt="org-roam-ui-in-emacs.png" class="invertible">
<figcaption><span class="figure-number">Figure 2: </span>Embed org-roam-ui in Emacs using xwidget-webkit.</figcaption>

2
2021-08-38-roaming.org
View File

@ -1,4 +1,4 @@
# Created 2024-01-11 Thu 11:13
# Created 2024-01-12 Fri 13:05
#+title: August 2021
#+date: 2021-08-38
#+author: TEC

8
2021-10-31-release.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 11:13 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>October 2021</title>
@ -68,7 +68,7 @@ document publishing needs, whatever they may be.
</p>
<figure id="org3a7bfcd">
<figure id="org3d5d213">
<img src="figures/citation-structure-full.svg" alt="citation-structure-full.svg" class="org-svg">
<figcaption><span class="figure-number">Figure 1: </span>The full citation syntax</figcaption>
@ -82,7 +82,7 @@ insertion experience.
</p>
<figure id="org58ff9c3">
<figure id="orgbc1feea">
<img src="figures/org-citar-insertion.png" alt="org-citar-insertion.png" class="doom-one">
<figcaption><span class="figure-number">Figure 2: </span>Inserting a citation with the <i>citar</i> package</figcaption>
@ -124,7 +124,7 @@ and more.
</p>
<figure id="org133ed9c">
<figure id="org25cb2f8">
<img src="figures/ob-julia-latexify-rendered.png" alt="ob-julia-latexify-rendered.png" class="doom-one">
<figcaption><span class="figure-number">Figure 3: </span>Rendered LaTeX representations of some Julia values</figcaption>

2
2021-10-31-release.org
View File

@ -1,4 +1,4 @@
# Created 2024-01-11 Thu 11:13
# Created 2024-01-12 Fri 13:05
#+title: October 2021
#+date: 2021-10-31
#+author: TEC

26
2021-11-30-element.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 11:13 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>November 2021</title>
@ -123,11 +123,11 @@ recently before say using the <kbd>csl</kbd> backend, one needed to
<p>
Now, if you have a line like:
</p>
<details id='orgc4e3731' class='code' open>
<details id='orgc8750fb' class='code' open>
<summary></summary>
<div class='gutter'><a href='#orgc4e3731'>#</a>
<div class='gutter'><a href='#orgc8750fb'>#</a>
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
<pre class="example" id="orgc4e3731">
<pre class="example" id="orgc8750fb">
#+cite_export: FORMAT ...
</pre>
@ -165,11 +165,11 @@ the base/default mode set by <code>org-babel-tangle-default-file-mode</code>.</d
<p>
This means the following forms are now all equivalent:
</p>
<details id='org8b61fea' class='code' open>
<details id='orgfa29bb3' class='code' open>
<summary></summary>
<div class='gutter'><a href='#org8b61fea'>#</a>
<div class='gutter'><a href='#orgfa29bb3'>#</a>
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
<pre class="example" id="org8b61fea">
<pre class="example" id="orgfa29bb3">
:tangle-mode (identity #o755)
:tangle-mode o755
:tangle-mode a=rx,u+w
@ -190,9 +190,9 @@ made yet though.
</p>
</div>
</div>
<div id="outline-container-149714207" class="outline-2">
<h2 id="149714207">Org element parser cache<a aria-hidden="true" href="#149714207">#</a> </h2>
<div class="outline-text-2" id="text-149714207">
<div id="outline-container-90227103" class="outline-2">
<h2 id="90227103">Org element parser cache<a aria-hidden="true" href="#90227103">#</a> </h2>
<div class="outline-text-2" id="text-90227103">
<p>
Ihor Radchenko has done some fantastic work over the past few months by
overhauling parts of <kbd>org-element.el</kbd> to introduce extensive caching. <kbd>org-element</kbd>
@ -231,7 +231,7 @@ differently from plain text. Now though, they have a new dedicated face
</p>
<figure id="orgcb55fd0">
<figure id="org2816665">
<img src="figures/inline-src-block-fontified-vs-code.png" alt="inline-src-block-fontified-vs-code.png" class="doom-one">
<figcaption><span class="figure-number">Figure 1: </span>Side-by-side comparison of a identical paragraphs using code (<code>~</code>) markup and inline source blocks (<code>src_</code>).</figcaption>
@ -246,7 +246,7 @@ show the code that produces them.
</p>
<figure id="org230c8c6">
<figure id="orgcb0073f">
<img src="figures/inline-src-block-julia-demo.png" alt="inline-src-block-julia-demo.png" class="doom-one">
<figcaption><span class="figure-number">Figure 2: </span>A paragraph making use of <i>evaluated</i> inline source blocks. Note that the <kbd>⟨11⟩</kbd> is a prettified results macro (using a potential future org-mode patch).</figcaption>
@ -381,7 +381,7 @@ accessible text width in the buffer.
</p>
<figure id="org5c0804c">
<figure id="orgbd6df71">
<img src="figures/proportional-image-width.png" alt="proportional-image-width.png" class="doom-one">
<figcaption><span class="figure-number">Figure 3: </span>A containing with an image set to half of the accesible text width</figcaption>

2
2021-11-30-element.org
View File

@ -1,4 +1,4 @@
# Created 2024-01-11 Thu 11:13
# Created 2024-01-12 Fri 13:05
#+title: November 2021
#+date: 2021-11-30
#+author: TEC

2
2021-12-31-retrospection.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 11:13 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>December 2021</title>

2
2021-12-31-retrospection.org
View File

@ -1,4 +1,4 @@
# Created 2024-01-11 Thu 11:13
# Created 2024-01-12 Fri 13:05
#+title: December 2021
#+date: 2021-12-31
#+author: TEC

16
2022-01-31-caching.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 15:58 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>January 2022</title>
@ -56,7 +56,7 @@ existed for a while now, but it used to be too buggy to be useful.
<p>
This is no longer the case! We're finally confident enough to flip
<code>org-element-use-cache</code>'s default from <code>nil</code> to <code>t</code>. I mentioned some of the
improvements in <a href="2021-11-30-element.html#org5a97798">November</a>, however Ihor has continued to make strides with the
improvements in <a href="2021-11-30-element.html#org6c447c2">November</a>, however Ihor has continued to make strides with the
cache.
</p>
@ -66,7 +66,7 @@ improved there are still lingering bugs which need to be chased down. If you
only take one thing away from the post, I'd like it to be this:
</p>
<div class="info" id="org9639369">
<div class="info" id="orgfc1b754">
<div style="text-align: left; margin-left: 1rem;">
<p>
The cache is actively being developed now, for the first time in years, so:
@ -83,11 +83,11 @@ The cache is actively being developed now, for the first time in years, so:
<p>
Cache warnings look something like this:
</p>
<details id='org54cdfd9' class='code' open>
<details id='org70e1330' class='code' open>
<summary></summary>
<div class='gutter'><a href='#org54cdfd9'>#</a>
<div class='gutter'><a href='#org70e1330'>#</a>
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
<pre class="example" id="org54cdfd9">
<pre class="example" id="org70e1330">
Warning (org-element-cache): org-element--cache: Unregistered buffer modifications detected. Resetting.
If this warning appears regularly, please report the warning text to Org mode mailing list (M-x org-submit-bug-report).
The buffer is: config.org
@ -161,7 +161,7 @@ to provide support for not just <span class='acr'>HTTPS</span> links but also tr
</p>
<figure id="org82a2995">
<figure id="org288b81f">
<img src="figures/ox-latex-image-link-localisation-demo.png" alt="ox-latex-image-link-localisation-demo.png" class="invertible">
<figcaption><span class="figure-number">Figure 1: </span>A screenshot of a (compiled to <span class='acr'>PDF</span>) LaTeX export, with an <span class='acr'>HTTPS</span> and tramp images.</figcaption>
@ -187,7 +187,7 @@ custom link types).
<li>Produce less native-comp warnings <span class="underline">Ihor Radchenko</span></li>
<li>Add a header to the clock report table <span class="underline">Samim Pezeshki</span></li>
<li>More verbose test failure summary <span class="underline">Max Nikulin</span></li>
<li>Parallelise <kbd>make</kbd>​ing the docs <span class="underline">Marco Wahl</span></li>
<li>Parallelise <kbd>make</kbd>ing the docs <span class="underline">Marco Wahl</span></li>
<li>More org-element tests <span class="underline">Ihor Radchenko</span></li>
</ul>
</div>

4
2022-01-31-caching.org
View File

@ -1,4 +1,4 @@
# Created 2024-01-11 Thu 15:58
# Created 2024-01-12 Fri 13:05
#+title: January 2022
#+date: 2022-01-31
#+author: TEC
@ -94,7 +94,7 @@ custom link types).
- Produce less native-comp warnings _Ihor Radchenko_
- Add a header to the clock report table _Samim Pezeshki_
- More verbose test failure summary _Max Nikulin_
- Parallelise =make=​ing the docs _Marco Wahl_
- Parallelise =make=ing the docs _Marco Wahl_
- More org-element tests _Ihor Radchenko_
* Bugfixes
- Fix formatting in elisp-link prompt _TEC_

2
2022-01-31-caching.txt
View File

@ -124,7 +124,7 @@ Other improvements
⁃ Produce less native-comp warnings _Ihor Radchenko_
⁃ Add a header to the clock report table _Samim Pezeshki_
⁃ More verbose test failure summary _Max Nikulin_
⁃ Parallelise `make'​ing the docs _Marco Wahl_
⁃ Parallelise `make'ing the docs _Marco Wahl_
⁃ More org-element tests _Ihor Radchenko_

4
2022-02-30-orgnvim.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 11:13 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>February 2022</title>
@ -49,7 +49,7 @@ experience outside Emacs.
</p>
<p>
<div class="link-preview"><a href="https://github.com/nvim-orgmode/orgmode"><img src="https://opengraph.githubassets.com/f86a7a47f5ae42199e2e39fb24fc82118fa106c93369a4272f8a5af6b6b37f11/nvim-orgmode/orgmode"/><small>github.com</small><p><b>GitHub - nvim-orgmode/orgmode: Orgmode clone written in Lua for Neovim 0.9+.</b></br>Orgmode clone written in Lua for Neovim 0.9+. Contribute to nvim-orgmode/orgmode development by creating an account on GitHub.</p></a></div>
<div class="link-preview"><a href="https://github.com/nvim-orgmode/orgmode"><img src="https://opengraph.githubassets.com/77915b5f9981ebc87709ee51d02ed39c60c1359e31ca75449c487c099f2456f6/nvim-orgmode/orgmode"/><small>github.com</small><p><b>GitHub - nvim-orgmode/orgmode: Orgmode clone written in Lua for Neovim 0.9+.</b></br>Orgmode clone written in Lua for Neovim 0.9+. Contribute to nvim-orgmode/orgmode development by creating an account on GitHub.</p></a></div>
</p>
<p>

2
2022-02-30-orgnvim.org
View File

@ -1,4 +1,4 @@
# Created 2024-01-11 Thu 11:13
# Created 2024-01-12 Fri 13:05
#+title: February 2022
#+date: 2022-02-30
#+author: Kristijan Husak

30
2022-04-01-confluence.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 11:13 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Special Announcement</title>
@ -42,26 +42,26 @@
<h1 class="title">Special Announcement</h1>
<p class="subtitle" role="doc-subtitle">Throwing in the towel and jumping on the bandwagon</p>
</header><p>
It <b>h</b>​as become apparent to the Org Mode developers that Org is suffering from a
severe lack of enterprise adoption. To r​<b>e</b>​ctify this, we will be leveraging our
collective decades working on holistic human-markup interaction tools to rapid​<b>l</b>​y
It <b>h</b>as become apparent to the Org Mode developers that Org is suffering from a
severe lack of enterprise adoption. To r<b>e</b>ctify this, we will be leveraging our
collective decades working on holistic human-markup interaction tools to rapid<b>l</b>y
pivot to what we believe to be the <i>true</i> markup format of the future &#x2014;
<a href="https://confluence.atlassian.com/doc/confluence-wiki-markup-251003035.html">Confluence Wiki Markup</a>.
</p>
<p>
With this <b>p</b>​aradigm shift, you can look forward to a much more intuitive syntax,
With this <b>p</b>aradigm shift, you can look forward to a much more intuitive syntax,
empowering you to create next-generation agile documents.
</p>
<p>
To assist you in this <b>t</b>​ransition, we'll give you a brief overview of the changes
To assist you in this <b>t</b>ransition, we'll give you a brief overview of the changes
you can expect. Text formatting is almost unaffected, with a few sensible
changes made to the surrounding c​<b>h</b>​aracters.
changes made to the surrounding c<b>h</b>aracters.
</p>
<figure id="orgd0a53d0">
<figure id="org24d0a1f">
<img src="figures/org-markup-to-confluence.svg" alt="org-markup-to-confluence.svg" class="invertible">
<figcaption><span class="figure-number">Figure 1: </span>Translation between Org's syntax and our new Confluence overlords's equivalents</figcaption>
@ -69,25 +69,25 @@ changes made to the surrounding c​<b>h</b>​aracters.
<p>
We'd like to thank the <span class='acr'>FSF</span> for giving the Org project the space and support to
grow to become a world-class proj​<b>e</b>​ct. In our new venture, cop​<b>y</b>​right assignment
to t​<b>h</b>​e <span class='acr'>FSF</span> is no longer required. Inste​<b>a</b>​d, copyright must be assigned to
grow to become a world-class proj<b>e</b>ct. In our new venture, cop<b>y</b>right assignment
to t<b>h</b>e <span class='acr'>FSF</span> is no longer required. Inste<b>a</b>d, copyright must be assigned to
Atlassian prior to contributing.
</p>
<p>
This new partnership enables new and exciting integrations with Atlassian's
proprietary technologies. O​<b>v</b>​er the next f​<b>e</b>​w months we will <b>b</b>​e transforming Org
to a cloud-n​<b>a</b>​tive serverless profes​<b>s</b>​ional markup offering. Unlike Confluence, we
will allow you to bo​<b>t</b>​h write <i>and edit</i> documents using pla​<b>i</b>​ntext markup. We
proprietary technologies. O<b>v</b>er the next f<b>e</b>w months we will <b>b</b>e transforming Org
to a cloud-n<b>a</b>tive serverless profes<b>s</b>ional markup offering. Unlike Confluence, we
will allow you to bo<b>t</b>h write <i>and edit</i> documents using pla<b>i</b>ntext markup. We
believe that by unlocking the synergy between plaintext and Confluence the Org
project will become a thought leader in hyp​<b>e</b>​r-scale markup solutions.
project will become a thought leader in hyp<b>e</b>r-scale markup solutions.
</p>
<p>
The shift to Confluence wiki markup will come as a surprise to many of you, but
after doing a deep dive into the scalability of Org we realised that there were
no low-hanging fruit available &#x2014; only out of the box thinking will allow for the
in​<b>n</b>​ovation so many of our users crave.
in<b>n</b>ovation so many of our users crave.
</p>
<p>

28
2022-04-01-confluence.org
View File

@ -1,40 +1,40 @@
# Created 2024-01-11 Thu 11:13
# Created 2024-01-12 Fri 13:05
#+title: Special Announcement
#+date: 2022-04-01
#+author: TEC
#+subtitle: Throwing in the towel and jumping on the bandwagon
It *h*​as become apparent to the Org Mode developers that Org is suffering from a
severe lack of enterprise adoption. To r​*e*​ctify this, we will be leveraging our
collective decades working on holistic human-markup interaction tools to rapid​*l*​y
It *h*as become apparent to the Org Mode developers that Org is suffering from a
severe lack of enterprise adoption. To r*e*ctify this, we will be leveraging our
collective decades working on holistic human-markup interaction tools to rapid*l*y
pivot to what we believe to be the /true/ markup format of the future ---
[[https://confluence.atlassian.com/doc/confluence-wiki-markup-251003035.html][Confluence Wiki Markup]].
With this *p*​aradigm shift, you can look forward to a much more intuitive syntax,
With this *p*aradigm shift, you can look forward to a much more intuitive syntax,
empowering you to create next-generation agile documents.
To assist you in this *t*​ransition, we'll give you a brief overview of the changes
To assist you in this *t*ransition, we'll give you a brief overview of the changes
you can expect. Text formatting is almost unaffected, with a few sensible
changes made to the surrounding c​*h*​aracters.
changes made to the surrounding c*h*aracters.
#+caption: Translation between Org's syntax and our new Confluence overlords's equivalents
[[file:figures/org-markup-to-confluence.svg]]
We'd like to thank the FSF for giving the Org project the space and support to
grow to become a world-class proj​*e*​ct. In our new venture, cop​*y*​right assignment
to t​*h*​e FSF is no longer required. Inste​*a*​d, copyright must be assigned to
grow to become a world-class proj*e*ct. In our new venture, cop*y*right assignment
to t*h*e FSF is no longer required. Inste*a*d, copyright must be assigned to
Atlassian prior to contributing.
This new partnership enables new and exciting integrations with Atlassian's
proprietary technologies. O​*v*​er the next f​*e*​w months we will *b*​e transforming Org
to a cloud-n​*a*​tive serverless profes​*s*​ional markup offering. Unlike Confluence, we
will allow you to bo​*t*​h write /and edit/ documents using pla​*i*​ntext markup. We
proprietary technologies. O*v*er the next f*e*w months we will *b*e transforming Org
to a cloud-n*a*tive serverless profes*s*ional markup offering. Unlike Confluence, we
will allow you to bo*t*h write /and edit/ documents using pla*i*ntext markup. We
believe that by unlocking the synergy between plaintext and Confluence the Org
project will become a thought leader in hyp​*e*​r-scale markup solutions.
project will become a thought leader in hyp*e*r-scale markup solutions.
The shift to Confluence wiki markup will come as a surprise to many of you, but
after doing a deep dive into the scalability of Org we realised that there were
no low-hanging fruit available --- only out of the box thinking will allow for the
in​*n*​ovation so many of our users crave.
in*n*ovation so many of our users crave.
We hope this change will not just disrupt your documents, but the entire markup
industry.

28
2022-04-01-confluence.txt
View File

@ -10,39 +10,39 @@
2022-04-01
It *h*​as become apparent to the Org Mode developers that Org is
suffering from a severe lack of enterprise adoption. To r​*e*​ctify this,
It *h*as become apparent to the Org Mode developers that Org is
suffering from a severe lack of enterprise adoption. To r*e*ctify this,
we will be leveraging our collective decades working on holistic
human-markup interaction tools to rapid​*l*​y pivot to what we believe to
human-markup interaction tools to rapid*l*y pivot to what we believe to
be the /true/ markup format of the future — [Confluence Wiki Markup].
With this *p*​aradigm shift, you can look forward to a much more
With this *p*aradigm shift, you can look forward to a much more
intuitive syntax, empowering you to create next-generation agile
documents.
To assist you in this *t*​ransition, we'll give you a brief overview of
To assist you in this *t*ransition, we'll give you a brief overview of
the changes you can expect. Text formatting is almost unaffected, with a
few sensible changes made to the surrounding c​*h*​aracters.
few sensible changes made to the surrounding c*h*aracters.
<file:figures/org-markup-to-confluence.svg>
We'd like to thank the FSF for giving the Org project the space and
support to grow to become a world-class proj​*e*​ct. In our new venture,
cop​*y*​right assignment to t​*h*​e FSF is no longer required. Inste​*a*​d,
support to grow to become a world-class proj*e*ct. In our new venture,
cop*y*right assignment to t*h*e FSF is no longer required. Inste*a*d,
copyright must be assigned to Atlassian prior to contributing.
This new partnership enables new and exciting integrations with
Atlassian's proprietary technologies. O​*v*​er the next f​*e*​w months we
will *b*​e transforming Org to a cloud-n​*a*​tive serverless profes​*s*​ional
markup offering. Unlike Confluence, we will allow you to bo​*t*​h write
/and edit/ documents using pla​*i*​ntext markup. We believe that by
Atlassian's proprietary technologies. O*v*er the next f*e*w months we
will *b*e transforming Org to a cloud-n*a*tive serverless profes*s*ional
markup offering. Unlike Confluence, we will allow you to bo*t*h write
/and edit/ documents using pla*i*ntext markup. We believe that by
unlocking the synergy between plaintext and Confluence the Org project
will become a thought leader in hyp​*e*​r-scale markup solutions.
will become a thought leader in hyp*e*r-scale markup solutions.
The shift to Confluence wiki markup will come as a surprise to many of
you, but after doing a deep dive into the scalability of Org we realised
that there were no low-hanging fruit available — only out of the box
thinking will allow for the in​*n*​ovation so many of our users crave.
thinking will allow for the in*n*ovation so many of our users crave.
We hope this change will not just disrupt your documents, but the entire
markup industry.

14
2022-05-31-folding.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<!-- 2024-01-11 Thu 11:13 -->
<!-- 2024-01-12 Fri 13:05 -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>May 2022</title>
@ -94,14 +94,14 @@ kind enough to whip up some benchmarks.
</p>
<figure id="orga8902d1">
<figure id="org02e48a4">
<img src="figures/org-fold-perf-shifttab-contents.svg" alt="org-fold-perf-shifttab-contents.svg" class="invertible">
<figcaption><span class="figure-number">Figure 1: </span>The scaling of <code>org-shifttab</code> showing file contents, as file size increases, with and without org-fold.</figcaption>
</figure>
<figure id="org13985e7">
<figure id="org6c3910b">
<img src="figures/org-fold-perf-shifttab-showall.svg" alt="org-fold-perf-shifttab-showall.svg" class="invertible">
<figcaption><span class="figure-number">Figure 2: </span>The scaling of <code>org-shifttab</code> showing the entire file, as file size increases, with and without org-fold.</figcaption>
@ -188,7 +188,7 @@ difference with small&#x2013;medium files, but if you a few large+ files this sh
be a <i>fantastic</i> improvement. Once again, thanks Ihor!
</p>
<div class="warning" id="org4c99280">
<div class="warning" id="org1c64527">
<p>
The change to text properties instead of overlays breaks a number of third party
packages like <kbd>evil-search</kbd> and <kbd>consult</kbd>'s <code>consult-line</code>.
@ -225,7 +225,7 @@ exports in LaTeX.
</p>
<figure id="orga0edd31">
<figure id="orgf39b777">
<img src="figures/engraved-faces-sample.png" alt="engraved-faces-sample.png" class="invertible">
<figcaption><span class="figure-number">Figure 3: </span>A screenshot of an Org code block, exported to a <span class='acr'>PDF</span>, using <kbd>engrave-faces</kbd> and the <kbd>doom-one-light</kbd> theme.</figcaption>
@ -250,7 +250,7 @@ The theme can also be set on a per-block level using the LaTeX attribute
</p>
<figure id="orgbefe8d3">
<figure id="org3ce23a5">
<img src="figures/engraved-faces-multitheme.png" alt="engraved-faces-multitheme.png">
<figcaption><span class="figure-number">Figure 4: </span>Seven code blocks exported to LaTeX, each with a different engrave-faces theme.</figcaption>
@ -358,7 +358,7 @@ giving it a shot.
</p>
<figure id="org1fc8d88">
<figure id="org701b21b">
<img src="figures/org-modern-readme-demo.gif" alt="org-modern-readme-demo.gif" class="invertible">
<figcaption><span class="figure-number">Figure 5: </span>A demonstration of org-modern taken from the project <span class='acr'>README</span>.</figcaption>

2
2022-05-31-folding.org
View File

@ -1,4 +1,4 @@
# Created 2024-01-11 Thu 11:13
# Created 2024-01-12 Fri 13:05
#+title: May 2022
#+date: 2022-05-31
#+author: TEC

10
archive.html
View File

@ -13,14 +13,14 @@
<meta property="og:image:width" content="464" />
<meta property="og:image:height" content="512" />
<meta property="og:image:alt" content="Org unicorn logo" />
<meta property="og:article:published_time" content="2024-01-11T16:04:23+0800" />
<meta property="og:article:modified_time" content="2024-01-11T16:04:23+0800" />
<meta property="og:article:published_time" content="2024-01-11T17:58:27+0800" />
<meta property="og:article:modified_time" content="2024-01-11T17:58:27+0800" />
<link rel="alternate" type="application/atom+xml" title="This Month in Org" href="rss.xml" />
<link rel="icon" type="image/ico" href="favicon.ico?v=3">
<link rel="stylesheet" type="text/css" href="org-style.css">
<link rel="stylesheet" type="text/css" href="blog.css">
<script src="org-style.js"></script>
<style> a { background-size: 0 !important; } </style>
<style> a { background-size: 0 !important; } li a { text-decoration: none; } </style>
</head>
<body>
<input type='checkbox' id='theme-switch'><div id='page'><label id='switch-label' for='theme-switch'></label><div id="preamble" class="status">
@ -38,7 +38,7 @@
<h1 class="title">Archive</h1>
</header><ul class="org-ul">
<li><a href='2022-05-31-folding.html'> <b>2022-05-31</b> Folding more improvement into Org <span class="underline">1090 words</span> </a></li>
<li><a href='2022-04-01-confluence.html'> <b>2022-04-01</b> Throwing in the towel and jumping on the bandwagon <span class="underline">350 words</span> </a></li>
<li><a href='2022-04-01-confluence.html'> <b>2022-04-01</b> Throwing in the towel and jumping on the bandwagon <span class="underline">320 words</span> </a></li>
<li><a href='2022-02-30-orgnvim.html'> <b>2022-02-30</b> An orgmode clone for neovim <span class="underline">2070 words</span> </a></li>
<li><a href='2022-01-31-caching.html'> <b>2022-01-31</b> Caching <span class="underline">770 words</span> </a></li>
<li><a href='2021-12-31-retrospection.html'> <b>2021-12-31</b> Looking back on my first year of blogging <span class="underline">540 words</span> </a></li>
@ -46,7 +46,7 @@
<li><a href='2021-10-31-release.html'> <b>2021-10-31</b> Release 9.5 <span class="underline">640 words</span> </a></li>
<li><a href='2021-08-38-roaming.html'> <b>2021-08-38</b> Roaming around <span class="underline">620 words</span> </a></li>
<li><a href='2021-07-31-citations.html'> <b>2021-07-31</b> Introducing citations! <span class="underline">1710 words</span> </a></li>
<li><a href='2021-06-34-relaxed.html'> <b>2021-06-34</b> A relaxed month <span class="underline">1260 words</span> </a></li>
<li><a href='2021-06-34-relaxed.html'> <b>2021-06-34</b> A relaxed month <span class="underline">1250 words</span> </a></li>
<li><a href='2021-05-31-async.html'> <b>2021-05-31</b> Asynchronous code execution <span class="underline">1090 words</span> </a></li>
<li><a href='2021-04-30-export-plot.html'> <b>2021-04-30</b> Export <i>&amp;</i> plot in style <span class="underline">860 words</span> </a></li>
<li><a href='2021-04-26-Welcome.html'> <b>2021-04-26</b> Welcome <span class="underline">930 words</span> </a></li>

2
archive.org
View File

@ -1,6 +1,6 @@
#+title: Archive
#+options: author:nil date:nil
#+html_head: <style> a { background-size: 0 !important; } </style>
#+html_head: <style> a { background-size: 0 !important; } li a { text-decoration: none; } </style>
* Post processing :noexport:
First we need to get all the posts

2
blog.css
View File

@ -1 +1 @@
header{position:relative;margin:0 auto -2rem}header>h4>a{text-decoration:none;color:inherit}header>h4>a.orgicorn img{height:1.5em;top:0.25em;opacity:0.85;position:relative}header>h4>a.rss{float:right}header>h4>a.rss img{position:relative;top:-0.2em;filter:invert(0.6)}header>h4>a.rss img:hover{opacity:1;filter:invert(38%) sepia(98%) saturate(1640%) hue-rotate(11deg) contrast(98%)}@media (min-width: 1000px){#content{margin:auto}header>h4>a.orgicorn img{position:absolute;top:-0.3em;transform:translateX(-100%) translateX(-0.8rem)}}#postamble{display:block}footer{display:block;text-align:center;font-size:0.8rem;padding:1rem 0;font-family:sans;color:#666}footer a{color:#777;font-weight:bold;background-image:none !important;opacity:0.65}#content{min-height:calc(100vh - 10rem - 48px)}.doom-one{filter:invert(5%) sepia(3%)}#theme-switch:checked~#page .doom-one{filter:invert(91.5%) hue-rotate(180deg) sepia(1%)}.underline{color:var(--text-medium);border-radius:.8em;padding:.5em .4em .2em;height:0;font-size:.9em;font-family:"Open Sans",sans}.underline:last-child{float:right;white-space:break-spaces;line-height:1}figure{transition-property:left width;left:0;width:90%;transition-duration:0ms}figure:active{position:relative;left:min(0px, 720px - 60vw);width:80vw;transition-duration:150ms}
header{position:relative}header>h4>a{text-decoration:none;color:inherit}header>h4>a.orgicorn img{height:1.5em;top:0.25em;opacity:0.85;position:relative}header>h4>a.rss{float:right}header>h4>a.rss img{position:relative;top:-0.2em;filter:invert(0.6)}header>h4>a.rss img:hover{opacity:1;filter:invert(38%) sepia(98%) saturate(1640%) hue-rotate(11deg) contrast(98%)}@media (min-width: 1000px){#content{margin:auto}header{margin:0 auto -2rem}header h4>a.orgicorn{display:inherit}header h4>a.orgicorn img{position:absolute;top:-0.3em;transform:translateX(-100%) translateX(-0.8rem)}}#postamble{display:block}footer{display:block;text-align:center;font-size:0.8rem;padding:1rem 0;font-family:sans;color:#666}footer a{color:#777;font-weight:bold;background-image:none !important;opacity:0.65}#content{min-height:calc(100vh - 10rem - 48px)}.doom-one{filter:invert(5%) sepia(3%)}#theme-switch:checked~#page .doom-one{filter:invert(91.5%) hue-rotate(180deg) sepia(1%)}.underline{color:var(--text-medium);border-radius:.8em;padding:.5em .4em .2em;height:0;font-size:.9em;font-family:"Open Sans",sans}.underline:last-child{float:right;white-space:break-spaces;line-height:1}figure{transition-property:left width;left:0;width:90%;transition-duration:0ms}figure:active{position:relative;left:min(0px, 720px - 60vw);width:80vw;transition-duration:150ms}

30
index.html
View File

@ -122,14 +122,14 @@ kind enough to whip up some benchmarks.
</p>
<figure id="org816610c">
<figure id="org0dd184c">
<img src="figures/org-fold-perf-shifttab-contents.svg" alt="org-fold-perf-shifttab-contents.svg" class="invertible">
<figcaption><span class="figure-number">Figure 1: </span>The scaling of <code>org-shifttab</code> showing file contents, as file size increases, with and without org-fold.</figcaption>
</figure>
<figure id="org6503ca0">
<figure id="org0fcffbe">
<img src="figures/org-fold-perf-shifttab-showall.svg" alt="org-fold-perf-shifttab-showall.svg" class="invertible">
<figcaption><span class="figure-number">Figure 2: </span>The scaling of <code>org-shifttab</code> showing the entire file, as file size increases, with and without org-fold.</figcaption>
@ -216,7 +216,7 @@ difference with small&#x2013;medium files, but if you a few large+ files this sh
be a <i>fantastic</i> improvement. Once again, thanks Ihor!
</p>
<div class="warning" id="orga3f7c65">
<div class="warning" id="org6e3b1ea">
<p>
The change to text properties instead of overlays breaks a number of third party
packages like <kbd>evil-search</kbd> and <kbd>consult</kbd>'s <code>consult-line</code>.
@ -253,7 +253,7 @@ exports in LaTeX.
</p>
<figure id="org862b4a5">
<figure id="org0d80784">
<img src="figures/engraved-faces-sample.png" alt="engraved-faces-sample.png" class="invertible">
<figcaption><span class="figure-number">Figure 3: </span>A screenshot of an Org code block, exported to a <span class='acr'>PDF</span>, using <kbd>engrave-faces</kbd> and the <kbd>doom-one-light</kbd> theme.</figcaption>
@ -278,7 +278,7 @@ The theme can also be set on a per-block level using the LaTeX attribute
</p>
<figure id="org096dd1d">
<figure id="org26c0201">
<img src="figures/engraved-faces-multitheme.png" alt="engraved-faces-multitheme.png">
<figcaption><span class="figure-number">Figure 4: </span>Seven code blocks exported to LaTeX, each with a different engrave-faces theme.</figcaption>
@ -386,7 +386,7 @@ giving it a shot.
</p>
<figure id="org10a2c69">
<figure id="orga39661b">
<img src="figures/org-modern-readme-demo.gif" alt="org-modern-readme-demo.gif" class="invertible">
<figcaption><span class="figure-number">Figure 5: </span>A demonstration of org-modern taken from the project <span class='acr'>README</span>.</figcaption>
@ -434,22 +434,22 @@ Fogel, Cody Harris</span></li>
<h2 id="htmla-href2022-04"><a href='2022-04-01-confluence.html' style='text-decoration:none;color:inherit'> Special Announcement <span class='tag'><span>2022-04-01</span></span></a><a aria-hidden="true" href="#htmla-href2022-04">#</a> </h2>
<div class="outline-text-2" id="text-htmla-href2022-04">
<p>
It <b>h</b>​as become apparent to the Org Mode developers that Org is suffering from a
severe lack of enterprise adoption. To r​<b>e</b>​ctify this, we will be leveraging our
collective decades working on holistic human-markup interaction tools to rapid​<b>l</b>​y
It <b>h</b>as become apparent to the Org Mode developers that Org is suffering from a
severe lack of enterprise adoption. To r<b>e</b>ctify this, we will be leveraging our
collective decades working on holistic human-markup interaction tools to rapid<b>l</b>y
pivot to what we believe to be the <i>true</i> markup format of the future &#x2014;
<a href="https://confluence.atlassian.com/doc/confluence-wiki-markup-251003035.html">Confluence Wiki Markup</a>.
</p>
<p>
With this <b>p</b>​aradigm shift, you can look forward to a much more intuitive syntax,
With this <b>p</b>aradigm shift, you can look forward to a much more intuitive syntax,
empowering you to create next-generation agile documents.
</p>
<p>
To assist you in this <b>t</b>​ransition, we'll give you a brief overview of the changes
To assist you in this <b>t</b>ransition, we'll give you a brief overview of the changes
you can expect. Text formatting is almost unaffected, with a few sensible
changes made to the surrounding c​<b>h</b>​aracters.
changes made to the surrounding c<b>h</b>aracters.
</p>
<p>
@ -467,7 +467,7 @@ experience outside Emacs.
</p>
<p>
<div class="link-preview"><a href="https://github.com/nvim-orgmode/orgmode"><img src="https://opengraph.githubassets.com/f86a7a47f5ae42199e2e39fb24fc82118fa106c93369a4272f8a5af6b6b37f11/nvim-orgmode/orgmode"/><small>github.com</small><p><b>GitHub - nvim-orgmode/orgmode: Orgmode clone written in Lua for Neovim 0.9+.</b></br>Orgmode clone written in Lua for Neovim 0.9+. Contribute to nvim-orgmode/orgmode development by creating an account on GitHub.</p></a></div>
<div class="link-preview"><a href="https://github.com/nvim-orgmode/orgmode"><img src="https://opengraph.githubassets.com/77915b5f9981ebc87709ee51d02ed39c60c1359e31ca75449c487c099f2456f6/nvim-orgmode/orgmode"/><small>github.com</small><p><b>GitHub - nvim-orgmode/orgmode: Orgmode clone written in Lua for Neovim 0.9+.</b></br>Orgmode clone written in Lua for Neovim 0.9+. Contribute to nvim-orgmode/orgmode development by creating an account on GitHub.</p></a></div>
</p>
<p>
@ -641,7 +641,7 @@ this post.
</p>
<figure id="org0fd095a">
<figure id="org372a347">
<img src="figures/celebrate-citations.svg" alt="celebrate-citations.svg" class="org-svg">
</figure>
@ -668,7 +668,7 @@ You'll just have to stick around to hear about those in a future edition of <spa
</p>
<figure id="org107d0a0">
<figure id="orgbb06346">
<img src="figures/dilbert-zenos-paradox.jpg" alt="dilbert-zenos-paradox.jpg" class="invertible">
<figcaption><span class="figure-number">Figure 6: </span>It's right around the corner, I swear!</figcaption>

124
rss.xml
View File

@ -14,8 +14,8 @@
<link>https://blog.tecosaur.net/tmio/</link>
<description><![CDATA[]]></description>
<language>en</language>
<pubDate>Thu, 11 Jan 2024 16:07:37 +0800</pubDate>
<lastBuildDate>Thu, 11 Jan 2024 16:07:37 +0800</lastBuildDate>
<pubDate>Fri, 12 Jan 2024 13:07:35 +0800</pubDate>
<lastBuildDate>Fri, 12 Jan 2024 13:07:35 +0800</lastBuildDate>
<generator>Emacs 29.1 Org-mode 9.6</generator>
<webMaster>contact.tmio@tecosaur.net (TEC)</webMaster>
<image>
@ -48,7 +48,7 @@
<p>
This is no longer the case! We're finally confident enough to flip
<code>org-element-use-cache</code>'s default from <code>nil</code> to <code>t</code>. I mentioned some of the
improvements in <a href="https://blog.tecosaur.net/tmio/2021-11-30-element.html#org8271516">November</a>, however Ihor has continued to make strides with the
improvements in <a href="https://blog.tecosaur.net/tmio/2021-11-30-element.html#orgf4b49e3">November</a>, however Ihor has continued to make strides with the
cache.
</p>
@ -58,7 +58,7 @@
only take one thing away from the post, I'd like it to be this:
</p>
<div class="info" id="orgc939446">
<div class="info" id="orgcc126eb">
<div style="text-align: left; margin-left: 1rem;">
<p>
The cache is actively being developed now, for the first time in years, so:
@ -71,7 +71,7 @@
<p>
Cache warnings look something like this:
</p>
<pre class="example" id="org46291dd">
<pre class="example" id="org75bef27">
Warning (org-element-cache): org-element--cache: Unregistered buffer modifications detected. Resetting.
If this warning appears regularly, please report the warning text to Org mode mailing list (M-x org-submit-bug-report).
The buffer is: config.org
@ -143,7 +143,7 @@
</p>
<figure id="org9159abe">
<figure id="org9423af2">
<img src="https://blog.tecosaur.net/tmio/figures/ox-latex-image-link-localisation-demo.png" alt="ox-latex-image-link-localisation-demo.png">
<figcaption><span class="figure-number">Figure 1: </span>A screenshot of a (compiled to PDF) LaTeX export, with an HTTPS and tramp images.</figcaption>
@ -166,7 +166,7 @@
Produce less native-comp warnings <span class="underline">Ihor Radchenko</span>
Add a header to the clock report table <span class="underline">Samim Pezeshki</span>
More verbose test failure summary <span class="underline">Max Nikulin</span>
Parallelise <kbd>make</kbd>​ing the docs <span class="underline">Marco Wahl</span>
Parallelise <kbd>make</kbd>ing the docs <span class="underline">Marco Wahl</span>
More org-element tests <span class="underline">Ihor Radchenko</span>
Bugfixes
Fix formatting in elisp-link prompt <span class="underline">TEC</span>
@ -218,14 +218,14 @@
</p>
<figure id="org08a2dd4">
<figure id="org9f7a5bb">
<img src="https://blog.tecosaur.net/tmio/figures/org-fold-perf-shifttab-contents.svg" alt="org-fold-perf-shifttab-contents.svg" class="org-svg">
<figcaption><span class="figure-number">Figure 2: </span>The scaling of <code>org-shifttab</code> showing file contents, as file size increases, with and without org-fold.</figcaption>
</figure>
<figure id="org1157409">
<figure id="org6f6ed94">
<img src="https://blog.tecosaur.net/tmio/figures/org-fold-perf-shifttab-showall.svg" alt="org-fold-perf-shifttab-showall.svg" class="org-svg">
<figcaption><span class="figure-number">Figure 3: </span>The scaling of <code>org-shifttab</code> showing the entire file, as file size increases, with and without org-fold.</figcaption>
@ -310,7 +310,7 @@
be a <i>fantastic</i> improvement. Once again, thanks Ihor!
</p>
<div class="warning" id="org0a0af58">
<div class="warning" id="orge7922ee">
<p>
The change to text properties instead of overlays breaks a number of third party
packages like <kbd>evil-search</kbd> and <kbd>consult</kbd>'s <code>consult-line</code>.
@ -335,26 +335,26 @@
<pubDate>Sat, 02 Apr 2022 00:00:00 +0800</pubDate>
<description><![CDATA[<p>
It <b>h</b>​as become apparent to the Org Mode developers that Org is suffering from a
severe lack of enterprise adoption. To r​<b>e</b>​ctify this, we will be leveraging our
collective decades working on holistic human-markup interaction tools to rapid​<b>l</b>​y
It <b>h</b>as become apparent to the Org Mode developers that Org is suffering from a
severe lack of enterprise adoption. To r<b>e</b>ctify this, we will be leveraging our
collective decades working on holistic human-markup interaction tools to rapid<b>l</b>y
pivot to what we believe to be the <i>true</i> markup format of the future ---
<a href="https://confluence.atlassian.com/doc/confluence-wiki-markup-251003035.html">Confluence Wiki Markup</a>.
</p>
<p>
With this <b>p</b>​aradigm shift, you can look forward to a much more intuitive syntax,
With this <b>p</b>aradigm shift, you can look forward to a much more intuitive syntax,
empowering you to create next-generation agile documents.
</p>
<p>
To assist you in this <b>t</b>​ransition, we'll give you a brief overview of the changes
To assist you in this <b>t</b>ransition, we'll give you a brief overview of the changes
you can expect. Text formatting is almost unaffected, with a few sensible
changes made to the surrounding c​<b>h</b>​aracters.
changes made to the surrounding c<b>h</b>aracters.
</p>
<figure id="orga5ac6c2">
<figure id="orgbe36c8a">
<img src="https://blog.tecosaur.net/tmio/figures/org-markup-to-confluence.svg" alt="org-markup-to-confluence.svg" class="org-svg">
<figcaption><span class="figure-number">Figure 4: </span>Translation between Org's syntax and our new Confluence overlords's equivalents</figcaption>
@ -362,25 +362,25 @@
<p>
We'd like to thank the FSF for giving the Org project the space and support to
grow to become a world-class proj​<b>e</b>​ct. In our new venture, cop​<b>y</b>​right assignment
to t​<b>h</b>​e FSF is no longer required. Inste​<b>a</b>​d, copyright must be assigned to
grow to become a world-class proj<b>e</b>ct. In our new venture, cop<b>y</b>right assignment
to t<b>h</b>e FSF is no longer required. Inste<b>a</b>d, copyright must be assigned to
Atlassian prior to contributing.
</p>
<p>
This new partnership enables new and exciting integrations with Atlassian's
proprietary technologies. O​<b>v</b>​er the next f​<b>e</b>​w months we will <b>b</b>​e transforming Org
to a cloud-n​<b>a</b>​tive serverless profes​<b>s</b>​ional markup offering. Unlike Confluence, we
will allow you to bo​<b>t</b>​h write <i>and edit</i> documents using pla​<b>i</b>​ntext markup. We
proprietary technologies. O<b>v</b>er the next f<b>e</b>w months we will <b>b</b>e transforming Org
to a cloud-n<b>a</b>tive serverless profes<b>s</b>ional markup offering. Unlike Confluence, we
will allow you to bo<b>t</b>h write <i>and edit</i> documents using pla<b>i</b>ntext markup. We
believe that by unlocking the synergy between plaintext and Confluence the Org
project will become a thought leader in hyp​<b>e</b>​r-scale markup solutions.
project will become a thought leader in hyp<b>e</b>r-scale markup solutions.
</p>
<p>
The shift to Confluence wiki markup will come as a surprise to many of you, but
after doing a deep dive into the scalability of Org we realised that there were
no low-hanging fruit available --- only out of the box thinking will allow for the
in​<b>n</b>​ovation so many of our users crave.
in<b>n</b>ovation so many of our users crave.
</p>
<p>
@ -980,7 +980,7 @@
<p>
Now, if you have a line like:
</p>
<pre class="example" id="orga669c32">
<pre class="example" id="orgb5adb53">
#+cite_export: FORMAT ...
</pre>
<p>
@ -1014,7 +1014,7 @@
<p>
This means the following forms are now all equivalent:
</p>
<pre class="example" id="org600178b">
<pre class="example" id="org63e5501">
:tangle-mode (identity #o755)
:tangle-mode o755
:tangle-mode a=rx,u+w
@ -1074,7 +1074,7 @@
</p>
<figure id="org5049549">
<figure id="org163b65b">
<img src="https://blog.tecosaur.net/tmio/figures/inline-src-block-fontified-vs-code.png" alt="inline-src-block-fontified-vs-code.png">
<figcaption><span class="figure-number">Figure 5: </span>Side-by-side comparison of a identical paragraphs using code (<code>~</code>) markup and inline source blocks (<code>src_</code>).</figcaption>
@ -1089,7 +1089,7 @@
</p>
<figure id="orge9925a6">
<figure id="orgee7a6c4">
<img src="https://blog.tecosaur.net/tmio/figures/inline-src-block-julia-demo.png" alt="inline-src-block-julia-demo.png">
<figcaption><span class="figure-number">Figure 6: </span>A paragraph making use of <i>evaluated</i> inline source blocks. Note that the <kbd>⟨11⟩</kbd> is a prettified results macro (using a potential future org-mode patch).</figcaption>
@ -1199,7 +1199,7 @@
</p>
<figure id="org8d7fac1">
<figure id="orgc75d165">
<img src="https://blog.tecosaur.net/tmio/figures/proportional-image-width.png" alt="proportional-image-width.png">
<figcaption><span class="figure-number">Figure 7: </span>A containing with an image set to half of the accesible text width</figcaption>
@ -1459,7 +1459,7 @@
</div>
<figure id="org3e171f1">
<figure id="org9d6cbb9">
<img src="https://blog.tecosaur.net/tmio/figures/org-verses-example-poem-dream-within-dream.png" alt="org-verses-example-poem-dream-within-dream.png">
<figcaption><span class="figure-number">Figure 8: </span>A short Poe-em</figcaption>
@ -1471,7 +1471,7 @@
<p>
Occasionally you may run into annoyances when you wish to have two different Org
elements right next to each other (no space) --- for example, <b>emph</b>​asising part of
elements right next to each other (no space) --- for example, <b>emph</b>asising part of
a word or putting a currency symbol immediately before an inline source block.
</p>
@ -1615,7 +1615,7 @@
</p>
<figure id="org152a478">
<figure id="orgf27c9bd">
<img src="https://blog.tecosaur.net/tmio/figures/citation-structure-full.svg" alt="citation-structure-full.svg" class="org-svg">
<figcaption><span class="figure-number">Figure 9: </span>The full citation syntax</figcaption>
@ -1629,7 +1629,7 @@
</p>
<figure id="orgfd9fb0e">
<figure id="org8628c32">
<img src="https://blog.tecosaur.net/tmio/figures/org-citar-insertion.png" alt="org-citar-insertion.png">
<figcaption><span class="figure-number">Figure 10: </span>Inserting a citation with the <i>citar</i> package</figcaption>
@ -1671,7 +1671,7 @@
</p>
<figure id="orga2159df">
<figure id="orgef00c46">
<img src="https://blog.tecosaur.net/tmio/figures/ob-julia-latexify-rendered.png" alt="ob-julia-latexify-rendered.png">
<figcaption><span class="figure-number">Figure 11: </span>Rendered LaTeX representations of some Julia values</figcaption>
@ -1777,7 +1777,7 @@
give it a shot!
</p>
<div class="info" id="orgd6909fa">
<div class="info" id="org1d62981">
<p>
<b>Ways you can contribute to the project</b>
</p>
@ -1958,7 +1958,7 @@
</p>
<figure id="org4ce13f0">
<figure id="org835ce20">
<img src="https://blog.tecosaur.net/tmio/figures/celebrate-citations.svg" alt="celebrate-citations.svg" class="org-svg">
</figure>
@ -2057,7 +2057,7 @@
<kbd>.bib</kbd>, <kbd>.bibtex</kbd>, or <kbd>.json</kbd> extension), which we do either via the <kbd>#+bibliography</kbd>
keyword, or the variable <code>org-cite-global-bibliography</code>.
</p>
<pre class="example" id="org1289f44">
<pre class="example" id="orgc4635b9">
#+bibliography: orgcite.bib
</pre>
@ -2067,7 +2067,7 @@
</p>
<figure id="orgf519e84">
<figure id="org8b523f5">
<img src="https://blog.tecosaur.net/tmio/figures/citation-structure-basic.svg" alt="citation-structure-basic.svg" class="org-svg">
<figcaption><span class="figure-number">Figure 12: </span>The new citation syntax, for simple citations</figcaption>
@ -2083,11 +2083,11 @@
<kbd>#+print_bibliography</kbd> keyword, like so:
</p>
<pre class="example" id="org43ff7db">
<pre class="example" id="org96f8ada">
#+print_bibliography:
</pre>
<div class="info" id="org9243a4d">
<div class="info" id="org6fb2faa">
<style>.csl-entry{text-indent: -1.5em; margin-left: 1.5em;}</style><div class="csl-bib-body">
</div>
@ -2096,7 +2096,7 @@
<p>
So, to summarise, all one needs to get started is:
</p>
<pre class="example" id="org665d03d">
<pre class="example" id="org7a46bad">
#+bibliography: references.bib
[cite:@key]
#+print_bibliography:
@ -2116,7 +2116,7 @@
</p>
<figure id="org00b1508">
<figure id="org9462168">
<img src="https://blog.tecosaur.net/tmio/figures/citation-structure-full.svg" alt="citation-structure-full.svg" class="org-svg">
<figcaption><span class="figure-number">Figure 13: </span>The new citations syntax, in full</figcaption>
@ -2420,7 +2420,7 @@
on a per-document basis via the <kbd>#+cite_export</kbd> keyword. Here, I shall use the <kbd>csl</kbd>
processor,
</p>
<pre class="example" id="orgccb1e6c">
<pre class="example" id="org0d415b1">
#+cite_export: csl
</pre>
@ -2429,7 +2429,7 @@
style by giving a triplet of parameters <code class="src src-elisp">(PROCESSOR BIBLIOGRAPHY-STYLE CITATION-STYLE)</code> instead of just the processor. You can also use this triplet of
values with the <kbd>#+cite_export</kbd> keyword
</p>
<pre class="example" id="org2049ddf">
<pre class="example" id="org725e95e">
#+cite_export: processor bibliography-style citation-style
</pre>
@ -2440,7 +2440,7 @@
options to a <code class="src src-LaTeX"><span class="org-keyword">\printbibliography</span></code> command, allowing for the
following:
</p>
<pre class="example" id="org6e290eb">
<pre class="example" id="orgd359f15">
#+print_bibliography: :section 2 :heading subbibliography
#+print_bibliography: :keyword abc,xyz :title "Primary Sources"
</pre>
@ -2486,7 +2486,7 @@
either absolute or relative to <code>org-cite-csl-styles-dir</code>. For example, if I
download <kbd>apa.csl</kbd> I can use it like so:
</p>
<pre class="example" id="org2bd0f17">
<pre class="example" id="org734efba">
#+cite_export: csl ~/Downloads/apa.csl
</pre>
@ -2515,14 +2515,14 @@
</p>
<figure id="org921c8a4">
<figure id="orgc22f107">
<img src="https://blog.tecosaur.net/tmio/figures/zotero-export-library.png" alt="zotero-export-library.png">
<figcaption><span class="figure-number">Figure 14: </span>Zotero library right click context menu, showing the export option</figcaption>
</figure>
<figure id="org62c57d5">
<figure id="org3ce83fb">
<img src="https://blog.tecosaur.net/tmio/figures/zotero-export-options-prompt.png" alt="zotero-export-options-prompt.png">
<figcaption><span class="figure-number">Figure 15: </span>Zotero collection export dialog</figcaption>
@ -2534,7 +2534,7 @@
</p>
<figure id="orgd080ff4">
<figure id="orgf35b296">
<img src="https://blog.tecosaur.net/tmio/figures/zotero-cite-styles-menu.png" alt="zotero-cite-styles-menu.png">
<figcaption><span class="figure-number">Figure 16: </span>Zotero CSL style management within preferences</figcaption>
@ -2554,7 +2554,7 @@
To then use the citation style defined by <kbd>~/Zotero/styles/apa.csl</kbd> one can then
simply refer to <kbd>apa.csl</kbd> when using the <kbd>#+cite_export</kbd> keyword.
</p>
<pre class="example" id="org7cc7ea2">
<pre class="example" id="orgb94c0c3">
#+cite_export: csl apa.csl
</pre>
</div>
@ -2643,7 +2643,7 @@
</p>
<figure id="orgbfed9c3">
<figure id="org07dce1d">
<img src="https://blog.tecosaur.net/tmio/figures/org-roam-graph-2d-overview.png" alt="org-roam-graph-2d-overview.png">
<figcaption><span class="figure-number">Figure 17: </span>org-roam-ui's 2D overview.</figcaption>
@ -2664,7 +2664,7 @@
</p>
<figure id="org57709a6">
<figure id="org62b4001">
<img src="https://blog.tecosaur.net/tmio/figures/org-roam-ui-in-emacs.png" alt="org-roam-ui-in-emacs.png">
<figcaption><span class="figure-number">Figure 18: </span>Embed org-roam-ui in Emacs using xwidget-webkit.</figcaption>
@ -2749,7 +2749,7 @@
</p>
<figure id="org9b040a2">
<figure id="org584a1d2">
<img src="https://blog.tecosaur.net/tmio/figures/dilbert-zenos-paradox.jpg" alt="dilbert-zenos-paradox.jpg">
<figcaption><span class="figure-number">Figure 19: </span>It's right around the corner, I swear!</figcaption>
@ -2766,7 +2766,7 @@
</p>
<figure id="orgca40214">
<figure id="org683a6fd">
<img src="https://blog.tecosaur.net/tmio/figures/org-latex-default-reference-to-sec.png" alt="org-latex-default-reference-to-sec.png">
<figcaption><span class="figure-number">Figure 20: </span>A LaTeX export of a simple document with a reference to both the first and second section. "2" what? Section 2, Table 2, Figure 2, ...</figcaption>
@ -2779,7 +2779,7 @@
</p>
<figure id="org3c92465">
<figure id="org1df8331">
<img src="https://blog.tecosaur.net/tmio/figures/org-latex-cref-reference-to-sec.png" alt="org-latex-cref-reference-to-sec.png">
<figcaption><span class="figure-number">Figure 21: </span>A LaTeX export of the same document, but now using <code>cleveref</code>. Note the change from "1" and "2" to "Section 1" and "Section 2".</figcaption>
@ -2861,7 +2861,7 @@
keyword, this works nicely in HTML too 🙂.
</p>
<figure id="orgaea6235">
<figure id="orgbb09719">
<img src="https://blog.tecosaur.net/tmio/figures/salvador-dali-persistence-of-memory.jpg" alt="salvador-dali-persistence-of-memory.jpg">
<figcaption><span class="figure-number">Figure 22: </span>A famous surrealist painting</figcaption>
@ -2923,7 +2923,7 @@
Org is nice and does the right thing<sup>TM</sup> by including the caption at the top.
</p>
<figure id="org9d2e956">
<figure id="org3aa9563">
<img src="https://blog.tecosaur.net/tmio/figures/org-table-to-latex-example.png" alt="org-table-to-latex-example.png">
<figcaption><span class="figure-number">Figure 23: </span>Look ma, I put the caption in the right place.</figcaption>
@ -3066,7 +3066,7 @@
<p>
For example, I'm quite a fan of the <a href="https://ctan.org/pkg/koma-script">KOMA-script</a> family. Should I want to add a
<kbd>kart</kbd> class (for: <b>k</b>​oma <b>art</b>​icle), I simply need to do something like the
<kbd>kart</kbd> class (for: <b>k</b>oma <b>art</b>icle), I simply need to do something like the
following:
</p>
<div class="org-src-container">
@ -3206,7 +3206,7 @@
</p>
<figure id="org72a991a">
<figure id="org7a2e29c">
<img src="https://blog.tecosaur.net/tmio/figures/screenshot-of-updates-orgmode-org.png" alt="screenshot-of-updates-orgmode-org.png">
<figcaption><span class="figure-number">Figure 24: </span>A screenshot of <a href="https://updates.orgmode.org/">updates.orgmode.org</a></figcaption>
@ -3240,7 +3240,7 @@
</p>
<figure id="org2eb911f">
<figure id="org00406c4">
<img src="https://github.com/larsmagne/meme/raw/master/images/Grandma-Finds-The-Internet.jpg" alt="Grandma-Finds-The-Internet.jpg">
<figcaption><span class="figure-number">Figure 25: </span>Org mode discovers the internet</figcaption>
@ -3261,7 +3261,7 @@
</p>
<figure id="org2870424">
<figure id="orgd11dfa5">
<img src="https://blog.tecosaur.net/tmio/figures/org-edit-special-latex-fragment.png" alt="org-edit-special-latex-fragment.png">
<figcaption><span class="figure-number">Figure 26: </span>Running <code>org-edit-special</code> on an inline LaTeX fragment</figcaption>
@ -3279,7 +3279,7 @@
</p>
<figure id="orga201c9b">
<figure id="org60c1d2a">
<img src="https://blog.tecosaur.net/tmio/figures/org-startup-num-and-levels.png" alt="org-startup-num-and-levels.png">
<figcaption><span class="figure-number">Figure 27: </span>Opening a buffer with the new <kbd>num</kbd> and <kbd>show2levels</kbd> startup options</figcaption>