Publish update based on 6e8419e
This commit is contained in:
parent
596af0ec31
commit
1bf5423940
SSH Key Fingerprint:
SHA256:eobz41Mnm0/iYWBvWThftS0ElEs1ftBr6jamutnXc/A
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>Welcome</title>
|
||||
|
|
@ -44,8 +44,8 @@
|
|||
<div class="outline-text-2" id="text-introduction">
|
||||
<p>
|
||||
Org is an absolutely marvellous project. However, a quick glance at
|
||||
<a href="https://orgmode.org">https://orgmode.org</a> can lead one to think "so… it's an Emacs version of
|
||||
Markdown? What's the big deal?". While it's easy to understand how someone might
|
||||
<a href="https://orgmode.org">https://orgmode.org</a> can lead one to think “so… it’s an Emacs version of
|
||||
Markdown? What’s the big deal?”. While it’s easy to understand how someone might
|
||||
think that at first, that impression misses two crucial points:
|
||||
</p>
|
||||
<ul class="org-ul">
|
||||
|
|
@ -65,21 +65,21 @@ number of things you can do with Org is only increasing.
|
|||
</p>
|
||||
|
||||
<p>
|
||||
However, if one doesn't want to receive tens to hundreds of emails a week, it
|
||||
However, if one doesn’t want to receive tens to hundreds of emails a week, it
|
||||
can be all too easy to miss out on exciting developments<sup><a id="fnr.2" class="footref" href="#fn.2" role="doc-backlink">2</a></sup> 😢. So, to help keep
|
||||
you abreast of the latest in Org, I'm starting a blog ✨. Like all good things,
|
||||
you abreast of the latest in Org, I’m starting a blog ✨. Like all good things,
|
||||
it is <a href="https://github.com/tecosaur/this-month-in-org/">written entirely in Org</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Inspired by <a href="https://pointieststick.com/category/this-week-in-kde/">This Week in <span class='acr'>KDE</span></a> I'm thrilled to announce <i>This Month in Org</i> (we have
|
||||
Inspired by <a href="https://pointieststick.com/category/this-week-in-kde/">This Week in <span class='acr'>KDE</span></a> I’m thrilled to announce <i>This Month in Org</i> (we have
|
||||
slightly less going on than a Desktop Environment<sup><a id="fnr.3" class="footref" href="#fn.3" role="doc-backlink">3</a></sup>). Each month I shall
|
||||
endeavour to present the highlights of Org development.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Who knows, perhaps you might see something you'd like to help out with or
|
||||
suggest improvements too. We'd love you to <a href="https://orgmode.org/community.html">get in touch</a>.
|
||||
Who knows, perhaps you might see something you’d like to help out with or
|
||||
suggest improvements too. We’d love you to <a href="https://orgmode.org/community.html">get in touch</a>.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -87,13 +87,13 @@ suggest improvements too. We'd love you to <a href="https://orgmode.org/communit
|
|||
<h2 id="catching-up-lost">Catching up on lost time — a year in review<a aria-hidden="true" href="#catching-up-lost">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-catching-up-lost">
|
||||
<p>
|
||||
I joined the Org mailing list in May last year, it's almost been a year since
|
||||
then and we've seen the release of Org 9.4, and its inclusion in Emacs 27.
|
||||
I joined the Org mailing list in May last year, it’s almost been a year since
|
||||
then and we’ve seen the release of Org 9.4, and its inclusion in Emacs 27.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
I'm not going to do 12 months of work for just this one post, but I'd like to
|
||||
give you a sample of what's changed over the last year.
|
||||
I’m not going to do 12 months of work for just this one post, but I’d like to
|
||||
give you a sample of what’s changed over the last year.
|
||||
</p>
|
||||
</div>
|
||||
<div id="outline-container-new-discussion-tracker" class="outline-3">
|
||||
|
|
@ -114,14 +114,14 @@ This should help ensure nothing slips through the cracks of the <span class='acr
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="orgdd6cf1f">
|
||||
<figure id="org03d28e5">
|
||||
<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>
|
||||
</figure>
|
||||
|
||||
<p>
|
||||
It's very slick, and Bastien built a <a href="https://github.com/bzg/woof">mailbox monitor</a> just for it — so be sure
|
||||
It’s very slick, and Bastien built a <a href="https://github.com/bzg/woof">mailbox monitor</a> just for it — so be sure
|
||||
to check it out. This should make it easier to see what needs doing. If you feel
|
||||
inclined to help out with Org check out the <i>Help requests</i> section in particular.
|
||||
</p>
|
||||
|
|
@ -148,7 +148,7 @@ their glory!
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org8192379">
|
||||
<figure id="org97973a6">
|
||||
<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>
|
||||
|
|
@ -164,12 +164,12 @@ To get this working, simply set <code class="src src-elisp">org-display-remote-i
|
|||
<h3 id="use-org-edit">Use <code>org-edit-special</code> (<kbd>C-c '</kbd>) with LaTeX fragments<a aria-hidden="true" href="#use-org-edit">#</a> </h3>
|
||||
<div class="outline-text-3" id="text-use-org-edit">
|
||||
<p>
|
||||
It's great how in Org you can jump into a LaTeX-mode minibuffer for LaTeX
|
||||
environments, but why leave inline LaTeX fragments out? We'll, they're now in.
|
||||
It’s great how in Org you can jump into a LaTeX-mode minibuffer for LaTeX
|
||||
environments, but why leave inline LaTeX fragments out? We’ll, they’re now in.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org2f642e3">
|
||||
<figure id="org056ad3d">
|
||||
<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>
|
||||
|
|
@ -180,21 +180,21 @@ environments, but why leave inline LaTeX fragments out? We'll, they're now in.
|
|||
<h3 id="control-heading-display">Control heading display on startup<a aria-hidden="true" href="#control-heading-display">#</a> </h3>
|
||||
<div class="outline-text-3" id="text-control-heading-display">
|
||||
<p>
|
||||
<kbd>org-num-mode</kbd> is great for when you're keeping an eye on section numbers, but
|
||||
it's not fun to find yourself enabling it every time you open a file where you
|
||||
<kbd>org-num-mode</kbd> is great for when you’re keeping an eye on section numbers, but
|
||||
it’s not fun to find yourself enabling it every time you open a file where you
|
||||
want it. With the new option <kbd>#+startup: num</kbd> by Bastien, you can set and forget
|
||||
at last.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org947274b">
|
||||
<figure id="orgcb68ae3">
|
||||
<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>
|
||||
</figure>
|
||||
|
||||
<p>
|
||||
Should you want to set the number of levels you see on opening a file, there's
|
||||
Should you want to set the number of levels you see on opening a file, there’s
|
||||
now an option for that too. Gustav Wikström has added <i>another</i> new option
|
||||
<kbd>#+startup: show<n>levels</kbd> (where <kbd><n></kbd> is between 2 and 5, inclusive).
|
||||
<i><span class='acr'>NB</span>: This is part of the upcoming 9.5 release</i>
|
||||
|
|
@ -205,8 +205,8 @@ now an option for that too. Gustav Wikström has added <i>another</i> new option
|
|||
<h3 id="set-permissions-tangled">Set permissions of tangled files<a aria-hidden="true" href="#set-permissions-tangled">#</a> </h3>
|
||||
<div class="outline-text-3" id="text-set-permissions-tangled">
|
||||
<p>
|
||||
Are you particular about your file permissions? If so you'll likely like John
|
||||
Herrlin's new source block header argument <kbd>:file-mode</kbd> pertinent. The easiest way
|
||||
Are you particular about your file permissions? If so you’ll likely like John
|
||||
Herrlin’s new source block header argument <kbd>:file-mode</kbd> pertinent. The easiest way
|
||||
to set a permission is with an <a href="https://docs.nersc.gov/filesystems/unix-file-permissions/">octal value</a>, like so:
|
||||
</p>
|
||||
<details id='set-permissions-tangled,code--1' class='code' open><summary><span class="lang">Org mode</span></summary>
|
||||
|
|
@ -227,17 +227,17 @@ to set a permission is with an <a href="https://docs.nersc.gov/filesystems/unix-
|
|||
<h3 id="collection-improvements-source">A collection of improvements to source block header arguments<a aria-hidden="true" href="#collection-improvements-source">#</a> </h3>
|
||||
<div class="outline-text-3" id="text-collection-improvements-source">
|
||||
<p>
|
||||
These's been a whole set of these, so I'll just list them off.
|
||||
These’s been a whole set of these, so I’ll just list them off.
|
||||
</p>
|
||||
<dl class="org-dl">
|
||||
<dt>python, improved <kbd>:return</kbd></dt><dd>Now works with sessions and the <kbd>:epilogue</kbd>
|
||||
argument (Jack Kamm)</dd>
|
||||
<dt>Java, new argument <kbd>:cmdargs</kbd></dt><dd>Add some command line arguments to be passed to
|
||||
<code>java</code> (Jarmo Hurri)</dd>
|
||||
<dt>C/C++, non-system headers with <kbd>:includes</kbd></dt><dd>values that don't start with <kbd><</kbd>
|
||||
<dt>C/C++, non-system headers with <kbd>:includes</kbd></dt><dd>values that don’t start with <kbd><</kbd>
|
||||
will now be formatted as double-quoted <code class="src src-C"><span class="org-preprocessor">#include</span></code> statements (Brandon
|
||||
Guttersohn)</dd>
|
||||
<dt>Screen, new argument <kbd>:screenrc</kbd></dt><dd>For those of you who still haven't moved to
|
||||
<dt>Screen, new argument <kbd>:screenrc</kbd></dt><dd>For those of you who still haven’t moved to
|
||||
<kbd>tmux</kbd> (Kenneth D. Mankoff)</dd>
|
||||
</dl>
|
||||
</div>
|
||||
|
|
@ -261,12 +261,12 @@ Aside from somewhat more <a href="https://orgmode.org/quickstart.html">intuitive
|
|||
structures, Org also has the advantage of not having <a href="https://github.com/commonmark/commonmark-spec/wiki/markdown-flavors">40 functionally distinct
|
||||
specifications</a>. There is only one Org. <br>
|
||||
<span class='acr'>NB</span>: If you attempt to be pedantic you may say that there are multiple Orgs
|
||||
because, for example, GitHub uses <a href="https://github.com/wallyqs/org-ruby">org-ruby</a>. However, that's just an incomplete
|
||||
because, for example, GitHub uses <a href="https://github.com/wallyqs/org-ruby">org-ruby</a>. However, that’s just an incomplete
|
||||
implementation — not a <a href="https://orgmode.org/worg/dev/org-syntax.html">specification</a>.
|
||||
</p></div></div>
|
||||
|
||||
<div class="footdef"><sup><a id="fn.2" class="footnum" href="#fnr.2" role="doc-backlink">2</a></sup> <div class="footpara" role="doc-footnote"><p class="footpara">
|
||||
There is <a href="https://code.orgmode.org/bzg/org-mode/src/master/etc/ORG-NEWS"><span class='acr'>ORG</span>-<span class='acr'>NEWS</span></a>, but do you <i>really</i> check that? Besides, it doesn't even
|
||||
There is <a href="https://code.orgmode.org/bzg/org-mode/src/master/etc/ORG-NEWS"><span class='acr'>ORG</span>-<span class='acr'>NEWS</span></a>, but do you <i>really</i> check that? Besides, it doesn’t even
|
||||
have pictures.
|
||||
</p></div></div>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: Welcome
|
||||
#+date: 2021-04-26
|
||||
#+author: TEC
|
||||
|
|
|
|||
|
|
@ -12,8 +12,8 @@ Introduction
|
|||
════════════
|
||||
|
||||
Org is an absolutely marvellous project. However, a quick glance at
|
||||
<https://orgmode.org> can lead one to think "so… it's an Emacs version
|
||||
of Markdown? What's the big deal?". While it's easy to understand how
|
||||
<https://orgmode.org> can lead one to think “so… it’s an Emacs version
|
||||
of Markdown? What’s the big deal?”. While it’s easy to understand how
|
||||
someone might think that at first, that impression misses two crucial
|
||||
points:
|
||||
⁃ While for simple constructs (*bold*, /italic/, headlines, etc.) the
|
||||
|
|
@ -29,18 +29,18 @@ Introduction
|
|||
is active, as is development, and the number of things you can do with
|
||||
Org is only increasing.
|
||||
|
||||
However, if one doesn't want to receive tens to hundreds of emails a
|
||||
However, if one doesn’t want to receive tens to hundreds of emails a
|
||||
week, it can be all too easy to miss out on exciting developments[2]
|
||||
😢. So, to help keep you abreast of the latest in Org, I'm starting a
|
||||
😢. So, to help keep you abreast of the latest in Org, I’m starting a
|
||||
blog ✨. Like all good things, it is [written entirely in Org].
|
||||
|
||||
Inspired by [This Week in KDE] I'm thrilled to announce /This Month in
|
||||
Inspired by [This Week in KDE] I’m thrilled to announce /This Month in
|
||||
Org/ (we have slightly less going on than a Desktop
|
||||
Environment[3]). Each month I shall endeavour to present the
|
||||
highlights of Org development.
|
||||
|
||||
Who knows, perhaps you might see something you'd like to help out with
|
||||
or suggest improvements too. We'd love you to [get in touch].
|
||||
Who knows, perhaps you might see something you’d like to help out with
|
||||
or suggest improvements too. We’d love you to [get in touch].
|
||||
|
||||
|
||||
[popping] <https://github.com/marktext/marktext>
|
||||
|
|
@ -69,12 +69,12 @@ Introduction
|
|||
Catching up on lost time — a year in review
|
||||
═══════════════════════════════════════════
|
||||
|
||||
I joined the Org mailing list in May last year, it's almost been a
|
||||
year since then and we've seen the release of Org 9.4, and its
|
||||
I joined the Org mailing list in May last year, it’s almost been a
|
||||
year since then and we’ve seen the release of Org 9.4, and its
|
||||
inclusion in Emacs 27.
|
||||
|
||||
I'm not going to do 12 months of work for just this one post, but I'd
|
||||
like to give you a sample of what's changed over the last year.
|
||||
I’m not going to do 12 months of work for just this one post, but I’d
|
||||
like to give you a sample of what’s changed over the last year.
|
||||
|
||||
|
||||
A new discussion tracker — [updates.orgmode.org]
|
||||
|
|
@ -90,7 +90,7 @@ A new discussion tracker — [updates.orgmode.org]
|
|||
|
||||
<file:figures/screenshot-of-updates-orgmode-org.png>
|
||||
|
||||
It's very slick, and Bastien built a [mailbox monitor] just for it —
|
||||
It’s very slick, and Bastien built a [mailbox monitor] just for it —
|
||||
so be sure to check it out. This should make it easier to see what
|
||||
needs doing. If you feel inclined to help out with Org check out the
|
||||
/Help requests/ section in particular.
|
||||
|
|
@ -127,9 +127,9 @@ Inline display of remote images
|
|||
Use `org-edit-special' (`C-c '') with LaTeX fragments
|
||||
─────────────────────────────────────────────────────
|
||||
|
||||
It's great how in Org you can jump into a LaTeX-mode minibuffer for
|
||||
LaTeX environments, but why leave inline LaTeX fragments out? We'll,
|
||||
they're now in.
|
||||
It’s great how in Org you can jump into a LaTeX-mode minibuffer for
|
||||
LaTeX environments, but why leave inline LaTeX fragments out? We’ll,
|
||||
they’re now in.
|
||||
|
||||
<file:figures/org-edit-special-latex-fragment.png>
|
||||
|
||||
|
|
@ -137,15 +137,15 @@ Use `org-edit-special' (`C-c '') with LaTeX fragments
|
|||
Control heading display on startup
|
||||
──────────────────────────────────
|
||||
|
||||
`org-num-mode' is great for when you're keeping an eye on section
|
||||
numbers, but it's not fun to find yourself enabling it every time you
|
||||
`org-num-mode' is great for when you’re keeping an eye on section
|
||||
numbers, but it’s not fun to find yourself enabling it every time you
|
||||
open a file where you want it. With the new option `#+startup: num' by
|
||||
Bastien, you can set and forget at last.
|
||||
|
||||
<file:figures/org-startup-num-and-levels.png>
|
||||
|
||||
Should you want to set the number of levels you see on opening a file,
|
||||
there's now an option for that too. Gustav Wikström has added
|
||||
there’s now an option for that too. Gustav Wikström has added
|
||||
/another/ new option `#+startup: show<n>levels' (where `<n>' is
|
||||
between 2 and 5, inclusive). /NB: This is part of the upcoming 9.5
|
||||
release/
|
||||
|
|
@ -154,8 +154,8 @@ Control heading display on startup
|
|||
Set permissions of tangled files
|
||||
────────────────────────────────
|
||||
|
||||
Are you particular about your file permissions? If so you'll likely
|
||||
like John Herrlin's new source block header argument `:file-mode'
|
||||
Are you particular about your file permissions? If so you’ll likely
|
||||
like John Herrlin’s new source block header argument `:file-mode'
|
||||
pertinent. The easiest way to set a permission is with an [octal
|
||||
value], like so:
|
||||
┌────
|
||||
|
|
@ -173,17 +173,17 @@ Set permissions of tangled files
|
|||
A collection of improvements to source block header arguments
|
||||
─────────────────────────────────────────────────────────────
|
||||
|
||||
These's been a whole set of these, so I'll just list them off.
|
||||
These’s been a whole set of these, so I’ll just list them off.
|
||||
python, improved `:return'
|
||||
Now works with sessions and the `:epilogue' argument (Jack Kamm)
|
||||
Java, new argument `:cmdargs'
|
||||
Add some command line arguments to be passed to `java' (Jarmo
|
||||
Hurri)
|
||||
C/C++, non-system headers with `:includes'
|
||||
values that don't start with `<' will now be formatted as
|
||||
values that don’t start with `<' will now be formatted as
|
||||
double-quoted `#include' statements (Brandon Guttersohn)
|
||||
Screen, new argument `:screenrc'
|
||||
For those of you who still haven't moved to `tmux' (Kenneth
|
||||
For those of you who still haven’t moved to `tmux' (Kenneth
|
||||
D. Mankoff)
|
||||
|
||||
|
||||
|
|
@ -211,13 +211,13 @@ distinct specifications]
|
|||
is only one Org.
|
||||
NB: If you attempt to be pedantic you may say that there are multiple
|
||||
Orgs because, for example, GitHub uses [org-ruby]
|
||||
(<https://github.com/wallyqs/org-ruby>). However, that's just an
|
||||
(<https://github.com/wallyqs/org-ruby>). However, that’s just an
|
||||
incomplete implementation — not a [specification]
|
||||
(<https://orgmode.org/worg/dev/org-syntax.html>).
|
||||
|
||||
[2] There is [ORG-NEWS]
|
||||
(<https://code.orgmode.org/bzg/org-mode/src/master/etc/ORG-NEWS>), but
|
||||
do you /really/ check that? Besides, it doesn't even have pictures.
|
||||
do you /really/ check that? Besides, it doesn’t even have pictures.
|
||||
|
||||
[3] That said, with /interesting/ projects like the [Emacs Application
|
||||
Framework]
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>April 2021</title>
|
||||
|
|
@ -46,7 +46,7 @@
|
|||
<h2 id="discussion-contributor-support">A discussion on contributor support<a aria-hidden="true" href="#discussion-contributor-support">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-discussion-contributor-support">
|
||||
<p>
|
||||
Concerns <a href="https://lists.gnu.org/archive/html/emacs-orgmode/2021-04/msg00291.html">were raised</a><sup><a id="fnr.1" class="footref" href="#fn.1" role="doc-backlink">1</a></sup> about some contributors' patches languishing, and it not
|
||||
Concerns <a href="https://lists.gnu.org/archive/html/emacs-orgmode/2021-04/msg00291.html">were raised</a><sup><a id="fnr.1" class="footref" href="#fn.1" role="doc-backlink">1</a></sup> about some contributors’ patches languishing, and it not
|
||||
being made clear how long it might take to get a response from someone.
|
||||
</p>
|
||||
|
||||
|
|
@ -67,11 +67,11 @@ and core maintainers:
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
If you've been thinking about <a href="https://orgmode.org/contribute.html">getting involved with Org</a>, now is a great time to
|
||||
If you’ve been thinking about <a href="https://orgmode.org/contribute.html">getting involved with Org</a>, now is a great time to
|
||||
give it a shot!
|
||||
</p>
|
||||
|
||||
<div class="info" id="org315f273">
|
||||
<div class="info" id="org437f980">
|
||||
<p>
|
||||
<b>Ways you can contribute to the project</b>
|
||||
</p>
|
||||
|
|
@ -88,7 +88,7 @@ Test patches, improve documentation, translate pages, confirm bugs, feedback on
|
|||
<div class="outline-text-2" id="text-doi-link-exporting">
|
||||
<p>
|
||||
<a href="https://www.doi.org/">Digital Document Identifiers</a> (<span class='acr'>DOI</span><small>s</small>) are an <span class='acr'>ISO</span>-standardised way of robustly
|
||||
linking to a particular online resource. You'll see these a lot with academic
|
||||
linking to a particular online resource. You’ll see these a lot with academic
|
||||
papers, for example.
|
||||
</p>
|
||||
|
||||
|
|
@ -135,7 +135,7 @@ Thanks to Nicolas Goaziou, when exporting to <span class='acr'>HTML</span>, LaTe
|
|||
</details>
|
||||
|
||||
<p>
|
||||
This is a minor change, but I think <span class='acr'>DOI</span><small>s</small> are great, so I'm highlighting it.
|
||||
This is a minor change, but I think <span class='acr'>DOI</span><small>s</small> are great, so I’m highlighting it.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -164,9 +164,9 @@ refreshed <span class="underline"><span class='acr'>TEC</span></span></li>
|
|||
</figure>
|
||||
|
||||
<p>
|
||||
Other than a few minor tweaks and bug fixes, that's it for April. However, over
|
||||
the last year there have been some rather nice improvements that I didn't
|
||||
mention in the initial blog post, so let's go over them now.
|
||||
Other than a few minor tweaks and bug fixes, that’s it for April. However, over
|
||||
the last year there have been some rather nice improvements that I didn’t
|
||||
mention in the initial blog post, so let’s go over them now.
|
||||
</p>
|
||||
|
||||
<ul class="org-ul">
|
||||
|
|
@ -192,7 +192,7 @@ my current Emacs theme.</li>
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
If you haven't used Org plot before, I think it's a great way to quickly
|
||||
If you haven’t used Org plot before, I think it’s a great way to quickly
|
||||
visualise data in a table. To get started, all you need is a <kbd>#+plot</kbd> line above
|
||||
the table, with a certain <kbd>type</kbd> specified (e.g. <kbd>type:2d</kbd> for a 2d line plot).
|
||||
Then, if you can specify a certain columns as the independent variable
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: April 2021
|
||||
#+date: 2021-04-30
|
||||
#+author: TEC
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@
|
|||
A discussion on contributor support
|
||||
═══════════════════════════════════
|
||||
|
||||
Concerns [were raised][1] about some contributors' patches
|
||||
Concerns [were raised][1] about some contributors’ patches
|
||||
languishing, and it not being made clear how long it might take to get
|
||||
a response from someone.
|
||||
|
||||
|
|
@ -27,7 +27,7 @@ A discussion on contributor support
|
|||
⁃ Tim Cross
|
||||
⁃ John Corless
|
||||
|
||||
If you've been thinking about [getting involved with Org], now is a
|
||||
If you’ve been thinking about [getting involved with Org], now is a
|
||||
great time to give it a shot!
|
||||
|
||||
*Ways you can contribute to the project*
|
||||
|
|
@ -51,7 +51,7 @@ DOI link exporting
|
|||
══════════════════
|
||||
|
||||
[Digital Document Identifiers] (DOIs) are an ISO-standardised way of
|
||||
robustly linking to a particular online resource. You'll see these a
|
||||
robustly linking to a particular online resource. You’ll see these a
|
||||
lot with academic papers, for example.
|
||||
|
||||
Thanks to Nicolas Goaziou, when exporting to HTML, LaTeX, Ascii, and
|
||||
|
|
@ -71,7 +71,7 @@ DOI link exporting
|
|||
│ @uref{https://doi.org/10.18637/jss.v046.i03}
|
||||
└────
|
||||
|
||||
This is a minor change, but I think DOIs are great, so I'm
|
||||
This is a minor change, but I think DOIs are great, so I’m
|
||||
highlighting it.
|
||||
|
||||
|
||||
|
|
@ -88,9 +88,9 @@ Org plot improvements
|
|||
⁃ When an image is regenerated, all instances of the image in the
|
||||
buffer are refreshed _TEC_
|
||||
|
||||
Other than a few minor tweaks and bug fixes, that's it for
|
||||
Other than a few minor tweaks and bug fixes, that’s it for
|
||||
April. However, over the last year there have been some rather nice
|
||||
improvements that I didn't mention in the initial blog post, so let's
|
||||
improvements that I didn’t mention in the initial blog post, so let’s
|
||||
go over them now.
|
||||
|
||||
⁃ The inbuilt plot types have been abstracted out into a new
|
||||
|
|
@ -114,7 +114,7 @@ Org plot improvements
|
|||
plots to your liking. For example, [I use this] to set line and
|
||||
background colours based on my current Emacs theme.
|
||||
|
||||
If you haven't used Org plot before, I think it's a great way to
|
||||
If you haven’t used Org plot before, I think it’s a great way to
|
||||
quickly visualise data in a table. To get started, all you need is a
|
||||
`#+plot' line above the table, with a certain `type' specified
|
||||
(e.g. `type:2d' for a 2d line plot). Then, if you can specify a
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>May 2021</title>
|
||||
|
|
@ -50,7 +50,7 @@ asynchronous output from source blocks <i>with full support for sessions</i>
|
|||
</p>
|
||||
|
||||
<p>
|
||||
If you haven't used sessions before, you're in for a treat! By simply assigning
|
||||
If you haven’t used sessions before, you’re in for a treat! By simply assigning
|
||||
a named session to a source code block, e.g. <kbd>:session foo</kbd>, the same process will
|
||||
be reused for any other code blocks that specify the <kbd>foo</kbd> session. To do this for
|
||||
a certain language across the entire document, you can set the header argument
|
||||
|
|
@ -74,7 +74,7 @@ not-too-distant future 😍.
|
|||
|
||||
<p>
|
||||
To use this, just add the <kbd>:async</kbd> parameter to a python block. Instead of Emacs
|
||||
freezing until it completes execution, you'll see a placeholder inserted which is
|
||||
freezing until it completes execution, you’ll see a placeholder inserted which is
|
||||
replaced by the result when it is ready.
|
||||
</p>
|
||||
|
||||
|
|
@ -89,8 +89,8 @@ replaced by the result when it is ready.
|
|||
</figure>
|
||||
|
||||
<p>
|
||||
<a href="https://github.com/nnicandro/emacs-jupyter">emacs-jupyter</a> allowed for asynchronous code execution (with sessions), but it's
|
||||
great to have a solution that doesn't require Jupyter kernels, and is part of
|
||||
<a href="https://github.com/nnicandro/emacs-jupyter">emacs-jupyter</a> allowed for asynchronous code execution (with sessions), but it’s
|
||||
great to have a solution that doesn’t require Jupyter kernels, and is part of
|
||||
Org.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -99,14 +99,14 @@ Org.
|
|||
<h2 id="font-lock-inline">Font lock for inline export snippets<a aria-hidden="true" href="#font-lock-inline">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-font-lock-inline">
|
||||
<p>
|
||||
Now, this isn't necessarily a significant change, but I don't think many people
|
||||
know about this feature so I'll take the opportunity to go over it 🙂.
|
||||
Now, this isn’t necessarily a significant change, but I don’t think many people
|
||||
know about this feature so I’ll take the opportunity to go over it 🙂.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
If you want to include a snippet of <span class='acr'>HTML</span>/LaTeX etc. when exporting to that
|
||||
format, you can use a <kbd>#+begin_export html</kbd> block which simply includes the
|
||||
enclosed content verbatim. This doesn't really work for small inline snippets
|
||||
enclosed content verbatim. This doesn’t really work for small inline snippets
|
||||
though — but never fear, Org has <i>inline</i> export snippets which simply follow the
|
||||
form <code class="src src-org"><span class="org-comment">@@</span><span class="org-org-tag">format:</span>content<span class="org-comment">@@</span></code>. For example:
|
||||
</p>
|
||||
|
|
@ -145,12 +145,12 @@ and then in LaTeX will be,
|
|||
</div>
|
||||
</details>
|
||||
<p>
|
||||
isn't that neat!
|
||||
isn’t that neat!
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Now you'll find the <kbd>@@</kbd> parts using the comment face and the <kbd>format:</kbd> bit using the
|
||||
Org tag's face. It's a small change, but it makes it easier to see what's going on.
|
||||
Now you’ll find the <kbd>@@</kbd> parts using the comment face and the <kbd>format:</kbd> bit using the
|
||||
Org tag’s face. It’s a small change, but it makes it easier to see what’s going on.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -162,8 +162,8 @@ No mode-specific syntax highlighting yet, but that may come in the future 😉.
|
|||
<h2 id="plot-your-results"><kbd>#+plot</kbd> your <kbd>#+results</kbd><a aria-hidden="true" href="#plot-your-results">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-plot-your-results">
|
||||
<p>
|
||||
Org-plot has been getting some more love as of late (see <a href="2021-04-30-export-plot.html">last month's post</a>), and
|
||||
that hasn't stopped yet. This month there's been a fairly minor change that I'm
|
||||
Org-plot has been getting some more love as of late (see <a href="2021-04-30-export-plot.html">last month’s post</a>), and
|
||||
that hasn’t stopped yet. This month there’s been a fairly minor change that I’m
|
||||
quite a fan of. If you have a source block that produces a table of <kbd>#+results</kbd>, you
|
||||
can now put a <kbd>#+plot</kbd> statement immediately above to get a visualisation of those
|
||||
results!
|
||||
|
|
@ -254,7 +254,7 @@ But a dream within a dream?
|
|||
</details>
|
||||
|
||||
|
||||
<figure id="org9f879d9">
|
||||
<figure id="org4ac285e">
|
||||
<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>
|
||||
|
|
@ -271,7 +271,7 @@ a word or putting a currency symbol immediately before an inline source block.
|
|||
</p>
|
||||
|
||||
<p>
|
||||
The best solution to this in Org is zero-width spaces. As such, I've found it
|
||||
The best solution to this in Org is zero-width spaces. As such, I’ve found it
|
||||
rather nice adding insertion of a zero-width space to the <code>org-mode-map</code> in my
|
||||
config. Perhaps some of you might find this solution useful too 🙂.
|
||||
</p>
|
||||
|
|
@ -288,7 +288,7 @@ config. Perhaps some of you might find this solution useful too 🙂.
|
|||
</details>
|
||||
|
||||
<p>
|
||||
Should you want to keep zero-width spaces out of exports, that's easy enough to
|
||||
Should you want to keep zero-width spaces out of exports, that’s easy enough to
|
||||
accomplish with an <a href="https://orgmode.org/manual/Advanced-Export-Configuration.html">export filter</a>.
|
||||
</p>
|
||||
|
||||
|
|
@ -309,7 +309,7 @@ accomplish with an <a href="https://orgmode.org/manual/Advanced-Export-Configura
|
|||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgs-repos-have" class="outline-2">
|
||||
<h2 id="orgs-repos-have">Org's repos have moved<a aria-hidden="true" href="#orgs-repos-have">#</a> </h2>
|
||||
<h2 id="orgs-repos-have">Org’s repos have moved<a aria-hidden="true" href="#orgs-repos-have">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-orgs-repos-have">
|
||||
<ul class="org-ul">
|
||||
<li><kbd>contrib/</kbd> is now at <a href="https://git.sr.ht/~bzg/org-contrib">https://git.sr.ht/~bzg/org-contrib</a> for Org 9.5, and it will
|
||||
|
|
@ -325,7 +325,7 @@ be available on Non-<span class='acr'>GNU</span> <span class='acr'>ELPA</span>.<
|
|||
<ul class="org-ul">
|
||||
<li>Add support for <kbd>HHhMM</kbd> date formats (e.g. <kbd>13h20</kbd>) <span class="underline">Gustavo Barros</span></li>
|
||||
<li>Make tangling faster <i>and</i> more robust <span class="underline">Sébastien Miquel</span></li>
|
||||
<li>Allow importing tables from files that <i>don't</i> end in <kbd>.txt</kbd>, <kbd>.tsv</kbd>, or <kbd>.csv</kbd>
|
||||
<li>Allow importing tables from files that <i>don’t</i> end in <kbd>.txt</kbd>, <kbd>.tsv</kbd>, or <kbd>.csv</kbd>
|
||||
<span class="underline">Utkarsh Singh</span></li>
|
||||
<li>Add an <span class='acr'>SVG</span>-specific post-export <kbd>ob-plantuml</kbd> step:
|
||||
<code>org-babel-plantuml-svg-text-to-path</code> for running Inkscape text-to-path
|
||||
|
|
@ -375,7 +375,7 @@ Nicolar Goaziou</span></li>
|
|||
<li>Inserting a heading before a headline <span class="underline">Bastien Guerry</span></li>
|
||||
<li>Perform <code>org-entry-put</code> in a read-only buffer <span class="underline">Ihor Radchenko</span></li>
|
||||
<li>Emacs 24 compatibility for <kbd>ob-C</kbd> and <code>org-agenda-show-new-time</code> <span class="underline">Kyle Meyer</span></li>
|
||||
<li>Maintain Org's keybindings when <code>visual-line-mode</code> active <span class="underline">Bastien Guerry</span></li>
|
||||
<li>Maintain Org’s keybindings when <code>visual-line-mode</code> active <span class="underline">Bastien Guerry</span></li>
|
||||
<li>Keep track of start of region beginning in <code>org-table-wrap-region</code> <span class="underline">Bastien Guerry</span></li>
|
||||
<li>Ensure correct visibility when unfolding subtree <span class="underline">Bastien Guerry</span></li>
|
||||
<li>Corner case in <code>org--backwards-paragaph-once</code> <span class="underline">Bastien Guerry</span></li>
|
||||
|
|
@ -387,7 +387,7 @@ instead of column <span class="underline"><span class='acr'>TEC</span></span></l
|
|||
<li>Prevent <kbd>ob-sql</kbd> from getting stuck on an error <span class="underline">Ivan Sokolov</span></li>
|
||||
<li>Make <kbd>org-columns</kbd> respect <code>global-visual-line-mode</code>, and simplify tag scanning
|
||||
<span class="underline">Nick Savage</span></li>
|
||||
<li>Don't fontify <kbd>::</kbd> in headlines as description item <span class="underline">Ihor Radchenko</span></li>
|
||||
<li>Don’t fontify <kbd>::</kbd> in headlines as description item <span class="underline">Ihor Radchenko</span></li>
|
||||
<li>Handle a few corner-cases in <kbd>ob-R</kbd> <span class="underline">Jeremie Juste</span></li>
|
||||
<li>Many fixes to <code>org-indent-line</code> <span class="underline">Bastien Guerry</span></li>
|
||||
<li>Make headline numbering consistent with <span class='acr'>TOC</span> <span class="underline">Mingkai Dong</span></li>
|
||||
|
|
@ -395,8 +395,8 @@ instead of column <span class="underline"><span class='acr'>TEC</span></span></l
|
|||
<li>Fix edge case when converting durations to minutes <span class="underline">Nicolas Goaziou</span></li>
|
||||
<li>Make org-refile work in non-file-visiting buffers <span class="underline">Bastien Guerry</span></li>
|
||||
<li>Be more rigorous in <code>org-sort-remove-invisible</code> <span class="underline">Nicolas Goaziou</span></li>
|
||||
<li>Don't update checkbox stats when heading has <kbd>todo</kbd> <kbd>COOKIE_DATA</kbd> <span class="underline">Bastien Guerry</span></li>
|
||||
<li>Don't recognise a lone <kbd>:END:</kbd> to be forming a drawer <span class="underline">Nicolas Goaziou</span></li>
|
||||
<li>Don’t update checkbox stats when heading has <kbd>todo</kbd> <kbd>COOKIE_DATA</kbd> <span class="underline">Bastien Guerry</span></li>
|
||||
<li>Don’t recognise a lone <kbd>:END:</kbd> to be forming a drawer <span class="underline">Nicolas Goaziou</span></li>
|
||||
<li>Allow new footnotes in empty table cells <span class="underline">Nicolas Goaziou</span></li>
|
||||
</ul>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: May 2021
|
||||
#+date: 2021-05-31
|
||||
#+author: TEC
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ Async Babel sessions have landed
|
|||
supports asynchronous output from source blocks /with full support for
|
||||
sessions/ 🎉.
|
||||
|
||||
If you haven't used sessions before, you're in for a treat! By simply
|
||||
If you haven’t used sessions before, you’re in for a treat! By simply
|
||||
assigning a named session to a source code block, e.g. `:session foo',
|
||||
the same process will be reused for any other code blocks that specify
|
||||
the `foo' session. To do this for a certain language across the entire
|
||||
|
|
@ -30,12 +30,12 @@ Async Babel sessions have landed
|
|||
*R* and *Ruby* in the not-too-distant future 😍.
|
||||
|
||||
To use this, just add the `:async' parameter to a python
|
||||
block. Instead of Emacs freezing until it completes execution, you'll
|
||||
block. Instead of Emacs freezing until it completes execution, you’ll
|
||||
see a placeholder inserted which is replaced by the result when it is
|
||||
ready.
|
||||
|
||||
[emacs-jupyter] allowed for asynchronous code execution (with
|
||||
sessions), but it's great to have a solution that doesn't require
|
||||
sessions), but it’s great to have a solution that doesn’t require
|
||||
Jupyter kernels, and is part of Org.
|
||||
|
||||
|
||||
|
|
@ -45,13 +45,13 @@ Async Babel sessions have landed
|
|||
Font lock for inline export snippets
|
||||
════════════════════════════════════
|
||||
|
||||
Now, this isn't necessarily a significant change, but I don't think
|
||||
many people know about this feature so I'll take the opportunity to go
|
||||
Now, this isn’t necessarily a significant change, but I don’t think
|
||||
many people know about this feature so I’ll take the opportunity to go
|
||||
over it 🙂.
|
||||
|
||||
If you want to include a snippet of HTML/LaTeX etc. when exporting to
|
||||
that format, you can use a `#+begin_export html' block which simply
|
||||
includes the enclosed content verbatim. This doesn't really work for
|
||||
includes the enclosed content verbatim. This doesn’t really work for
|
||||
small inline snippets though — but never fear, Org has /inline/ export
|
||||
snippets which simply follow the form `@@format:content@@'. For
|
||||
example:
|
||||
|
|
@ -67,11 +67,11 @@ Font lock for inline export snippets
|
|||
┌────
|
||||
│ I love using Org to export to \LaTeX{} documents.
|
||||
└────
|
||||
isn't that neat!
|
||||
isn’t that neat!
|
||||
|
||||
Now you'll find the `@@' parts using the comment face and the
|
||||
`format:' bit using the Org tag's face. It's a small change, but it
|
||||
makes it easier to see what's going on.
|
||||
Now you’ll find the `@@' parts using the comment face and the
|
||||
`format:' bit using the Org tag’s face. It’s a small change, but it
|
||||
makes it easier to see what’s going on.
|
||||
|
||||
No mode-specific syntax highlighting yet, but that may come in the
|
||||
future 😉.
|
||||
|
|
@ -80,9 +80,9 @@ Font lock for inline export snippets
|
|||
`#+plot' your `#+results'
|
||||
═════════════════════════
|
||||
|
||||
Org-plot has been getting some more love as of late (see [last month's
|
||||
post]), and that hasn't stopped yet. This month there's been a fairly
|
||||
minor change that I'm quite a fan of. If you have a source block that
|
||||
Org-plot has been getting some more love as of late (see [last month’s
|
||||
post]), and that hasn’t stopped yet. This month there’s been a fairly
|
||||
minor change that I’m quite a fan of. If you have a source block that
|
||||
produces a table of `#+results', you can now put a `#+plot' statement
|
||||
immediately above to get a visualisation of those results!
|
||||
|
||||
|
|
@ -105,7 +105,7 @@ Font lock for inline export snippets
|
|||
about it in the [manual].
|
||||
|
||||
|
||||
[last month's post] <file:2021-04-30-export-plot.org>
|
||||
[last month’s post] <file:2021-04-30-export-plot.org>
|
||||
|
||||
[manual] <https://orgmode.org/manual/Org-Plot.html>
|
||||
|
||||
|
|
@ -168,7 +168,7 @@ Easy zero-width spaces with Org
|
|||
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
|
||||
The best solution to this in Org is zero-width spaces. As such, I’ve
|
||||
found it rather nice adding insertion of a zero-width space to the
|
||||
`org-mode-map' in my config. Perhaps some of you might find this
|
||||
solution useful too 🙂.
|
||||
|
|
@ -178,7 +178,7 @@ Easy zero-width spaces with Org
|
|||
│ (lambda () (interactive) (insert "\u200b")))
|
||||
└────
|
||||
|
||||
Should you want to keep zero-width spaces out of exports, that's easy
|
||||
Should you want to keep zero-width spaces out of exports, that’s easy
|
||||
enough to accomplish with an [export filter].
|
||||
|
||||
┌────
|
||||
|
|
@ -195,7 +195,7 @@ Easy zero-width spaces with Org
|
|||
<https://orgmode.org/manual/Advanced-Export-Configuration.html>
|
||||
|
||||
|
||||
Org's repos have moved
|
||||
Org’s repos have moved
|
||||
══════════════════════
|
||||
|
||||
⁃ `contrib/' is now at <https://git.sr.ht/~bzg/org-contrib> for Org
|
||||
|
|
@ -209,7 +209,7 @@ Other improvements
|
|||
|
||||
⁃ Add support for `HHhMM' date formats (e.g. `13h20') _Gustavo Barros_
|
||||
⁃ Make tangling faster /and/ more robust _Sébastien Miquel_
|
||||
⁃ Allow importing tables from files that /don't/ end in `.txt',
|
||||
⁃ Allow importing tables from files that /don’t/ end in `.txt',
|
||||
`.tsv', or `.csv' _Utkarsh Singh_
|
||||
⁃ Add an SVG-specific post-export `ob-plantuml' step:
|
||||
`org-babel-plantuml-svg-text-to-path' for running Inkscape
|
||||
|
|
@ -260,7 +260,7 @@ Bugfixes
|
|||
⁃ Perform `org-entry-put' in a read-only buffer _Ihor Radchenko_
|
||||
⁃ Emacs 24 compatibility for `ob-C' and `org-agenda-show-new-time'
|
||||
_Kyle Meyer_
|
||||
⁃ Maintain Org's keybindings when `visual-line-mode' active _Bastien
|
||||
⁃ Maintain Org’s keybindings when `visual-line-mode' active _Bastien
|
||||
Guerry_
|
||||
⁃ Keep track of start of region beginning in `org-table-wrap-region'
|
||||
_Bastien Guerry_
|
||||
|
|
@ -275,7 +275,7 @@ Bugfixes
|
|||
⁃ Prevent `ob-sql' from getting stuck on an error _Ivan Sokolov_
|
||||
⁃ Make `org-columns' respect `global-visual-line-mode', and simplify
|
||||
tag scanning _Nick Savage_
|
||||
⁃ Don't fontify `::' in headlines as description item _Ihor Radchenko_
|
||||
⁃ Don’t fontify `::' in headlines as description item _Ihor Radchenko_
|
||||
⁃ Handle a few corner-cases in `ob-R' _Jeremie Juste_
|
||||
⁃ Many fixes to `org-indent-line' _Bastien Guerry_
|
||||
⁃ Make headline numbering consistent with TOC _Mingkai Dong_
|
||||
|
|
@ -284,8 +284,8 @@ Bugfixes
|
|||
⁃ Fix edge case when converting durations to minutes _Nicolas Goaziou_
|
||||
⁃ Make org-refile work in non-file-visiting buffers _Bastien Guerry_
|
||||
⁃ Be more rigorous in `org-sort-remove-invisible' _Nicolas Goaziou_
|
||||
⁃ Don't update checkbox stats when heading has `todo' `COOKIE_DATA'
|
||||
⁃ Don’t update checkbox stats when heading has `todo' `COOKIE_DATA'
|
||||
_Bastien Guerry_
|
||||
⁃ Don't recognise a lone `:END:' to be forming a drawer _Nicolas
|
||||
⁃ Don’t recognise a lone `:END:' to be forming a drawer _Nicolas
|
||||
Goaziou_
|
||||
⁃ Allow new footnotes in empty table cells _Nicolas Goaziou_
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>June 2021</title>
|
||||
|
|
@ -44,17 +44,17 @@
|
|||
</header><p>
|
||||
The previous two months have been pretty good for Org development — with many
|
||||
bug fixes and feature improvements. This month has been substantially slower
|
||||
than the last<sup><a id="fnr.1" class="footref" href="#fn.1" role="doc-backlink">1</a></sup>, but that's not to say not much is happening: in fact, there are
|
||||
than the last<sup><a id="fnr.1" class="footref" href="#fn.1" role="doc-backlink">1</a></sup>, but that’s not to say not much is happening: in fact, there are
|
||||
some rather nifty contributions lined up for the not-too-distant future and a
|
||||
certain long-awaited feature branch<sup><a id="fnr.2" class="footref" href="#fn.2" role="doc-backlink">2</a></sup> is getting very close to merging 😀.
|
||||
You'll just have to stick around to hear about those in a future edition of <span class='acr'>TMIO</span> 😉.
|
||||
You’ll just have to stick around to hear about those in a future edition of <span class='acr'>TMIO</span> 😉.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org4093549">
|
||||
<figure id="orgb975711">
|
||||
<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>
|
||||
<figcaption><span class="figure-number">Figure 1: </span>It’s right around the corner, I swear!</figcaption>
|
||||
</figure>
|
||||
<div id="outline-container-customise-reference-command" class="outline-2">
|
||||
<h2 id="customise-reference-command">Customise the reference command used in LaTeX<a aria-hidden="true" href="#customise-reference-command">#</a> </h2>
|
||||
|
|
@ -66,23 +66,23 @@ without giving it a name) — for example with <kbd>[[Profound section]]</k
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org4e948be">
|
||||
<figure id="orgd059838">
|
||||
<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, …</figcaption>
|
||||
<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, …</figcaption>
|
||||
</figure>
|
||||
|
||||
<p>
|
||||
You can now set the format string <code>org-latex-reference-command</code> (<kbd>\\ref{%s}</kbd> by
|
||||
default) to anything you'd like. For example, making use of the <a href="https://ctan.org/pkg/cleveref">cleveref</a> package
|
||||
default) to anything you’d like. For example, making use of the <a href="https://ctan.org/pkg/cleveref">cleveref</a> package
|
||||
I can set this to <kbd>\\cref{%s}</kbd> and then add <code class="src src-elisp">(<span class="org-string">"capitalize"</span> <span class="org-string">"cleveref"</span> nil)</code><sup><a id="fnr.3" class="footref" href="#fn.3" role="doc-backlink">3</a></sup> to <code>org-latex-packages-alist</code>.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org92e84d8">
|
||||
<figure id="orgcfb6619">
|
||||
<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>
|
||||
<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>
|
||||
</figure>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -91,13 +91,13 @@ I can set this to <kbd>\\cref{%s}</kbd> and then add <code class="src src-elisp"
|
|||
<div class="outline-text-2" id="text-diversion-into-writing">
|
||||
<p>
|
||||
Speaking of LaTeX exports, a member of the Org mailing list recently told us
|
||||
about <a href="https://arxiv.org/abs/2106.05096">a paper</a> pushed to <a href="https://arxiv.org/">arXiv</a> which was written <i>entirely</i> in Org. Why don't we
|
||||
about <a href="https://arxiv.org/abs/2106.05096">a paper</a> pushed to <a href="https://arxiv.org/">arXiv</a> which was written <i>entirely</i> in Org. Why don’t we
|
||||
use that as a prompt to talk a bit about generating LaTeX documents from Org?
|
||||
</p>
|
||||
|
||||
<p>
|
||||
For an experienced LaTeX-er, Org may initially appear best suited to simple
|
||||
documents, but in fact it's possible to reproduce any LaTeX structure in Org
|
||||
documents, but in fact it’s possible to reproduce any LaTeX structure in Org
|
||||
with no more difficulty (often less) than in LaTeX.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -105,7 +105,7 @@ with no more difficulty (often less) than in LaTeX.
|
|||
<h3 id="simple-elements">Simple elements<a aria-hidden="true" href="#simple-elements">#</a> </h3>
|
||||
<div class="outline-text-3" id="text-simple-elements">
|
||||
<p>
|
||||
The "basic" Org elements are simply translated to their LaTeX counterparts.
|
||||
The “basic” Org elements are simply translated to their LaTeX counterparts.
|
||||
Markup like <b>bold</b>, <i>italic</i>, etc. are simply translated through
|
||||
<code>org-latex-text-markup-alist</code>.
|
||||
</p>
|
||||
|
|
@ -113,7 +113,7 @@ Markup like <b>bold</b>, <i>italic</i>, etc. are simply translated through
|
|||
<p>
|
||||
For those of us who dabble with equations, Org is <a href="https://orgmode.org/manual/LaTeX-fragments.html">very accomodating</a>. You can
|
||||
type (LaTeX-style) inline and display equations in exactly the same way (<kbd>\( \)</kbd>
|
||||
and <kbd>\[ \]</kbd>), and what's more, if you have a LaTeX environment statement
|
||||
and <kbd>\[ \]</kbd>), and what’s more, if you have a LaTeX environment statement
|
||||
<kbd>\begin{...}</kbd> on its own line, Org will recognise it and pass it into the
|
||||
generated LaTeX.
|
||||
</p>
|
||||
|
|
@ -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="org87315cd">
|
||||
<figure id="orgaebbf1c">
|
||||
<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 & 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="orgb734b46">
|
||||
<figure id="orgf70273a">
|
||||
<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>
|
||||
|
|
@ -268,7 +268,7 @@ Org is nice and does the right thing<sup><span class='acr'>TM</span></sup> by in
|
|||
<p>
|
||||
There are also some <a href="https://orgmode.org/manual/Images-in-LaTeX-export.html">more attributes</a> you can supply to tables. Should I want the
|
||||
table to spread out I could use <kbd>#+attr_latex: :environment tabularx</kbd> (as long as
|
||||
I've loaded the <kbd>tabularx</kbd> package) and then set the columns with <kbd>:align lX</kbd>.
|
||||
I’ve loaded the <kbd>tabularx</kbd> package) and then set the columns with <kbd>:align lX</kbd>.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -277,7 +277,7 @@ I've loaded the <kbd>tabularx</kbd> package) and then set the columns with <kbd>
|
|||
<div class="outline-text-3" id="text-code-blocks">
|
||||
<p>
|
||||
By default, source code blocks are translated verbatim. We can do better than
|
||||
that however. We can tell Org to use <a href="https://ctan.org/pkg/listings">listings</a>, but I'd recommend going one step
|
||||
that however. We can tell Org to use <a href="https://ctan.org/pkg/listings">listings</a>, but I’d recommend going one step
|
||||
further and using <a href="https://ctan.org/pkg/minted">minted</a>. For this to work we need to perform three actions:
|
||||
</p>
|
||||
<ul class="org-ul">
|
||||
|
|
@ -317,7 +317,7 @@ each <kbd>minted</kbd> environment.
|
|||
Org has a number of <a href="https://orgmode.org/manual/Blocks.html">blocks</a> which are treated specially, like <kbd>#+begin_src</kbd> for
|
||||
source code, and <kbd>#+begin_centre</kbd> for centred text. When exporting this same
|
||||
syntax allows you to wrap Org content in any LaTeX environments (as long as it
|
||||
doesn't match one of Org's recognised environments).
|
||||
doesn’t match one of Org’s recognised environments).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -359,7 +359,7 @@ transferred to the generated LaTeX (this works with other formats too).
|
|||
</details>
|
||||
|
||||
<p>
|
||||
For larger snippets of LaTeX, there's always the export block.
|
||||
For larger snippets of LaTeX, there’s always the export block.
|
||||
</p>
|
||||
<details id='latex-escape-hatches,code--2' class='code' open><summary><span class="lang">Org mode</span></summary>
|
||||
<div class='gutter'>
|
||||
|
|
@ -406,7 +406,7 @@ using a certain LaTeX compiler.
|
|||
<p>
|
||||
Should you want to use a certain preset preamble, you can make use of the
|
||||
<kbd>#+latex_class</kbd> keyword. This is used to set the base preamble template used when
|
||||
generating the LaTeX. See <code>org-latex-classes</code> for what's available by default. You
|
||||
generating the LaTeX. See <code>org-latex-classes</code> for what’s available by default. You
|
||||
should see entries for:
|
||||
</p>
|
||||
<ul class="org-ul">
|
||||
|
|
@ -422,7 +422,7 @@ in the document, the template named by <code>org-latex-default-class</code> will
|
|||
</p>
|
||||
|
||||
<p>
|
||||
What's great about this is that is makes it really easy to add your own
|
||||
What’s great about this is that is makes it really easy to add your own
|
||||
templates. Each template simply takes three components:
|
||||
</p>
|
||||
<ol class="org-ol">
|
||||
|
|
@ -432,7 +432,7 @@ templates. Each template simply takes three components:
|
|||
</ol>
|
||||
|
||||
<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
|
||||
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
|
||||
following:
|
||||
</p>
|
||||
|
|
@ -464,12 +464,12 @@ preamble template in handled.
|
|||
<h2 id="other-improvements">Other improvements<a aria-hidden="true" href="#other-improvements">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-other-improvements">
|
||||
<ul class="org-ul">
|
||||
<li><kbd>ox-koma-letter.el</kbd> has been brought into Org's main directory from the ) <kbd>contrib/</kbd> repo <span class="underline">Bastien Guerry</span></li>
|
||||
<li><kbd>ox-koma-letter.el</kbd> has been brought into Org’s main directory from the ) <kbd>contrib/</kbd> repo <span class="underline">Bastien Guerry</span></li>
|
||||
<li>Speed up publishing by using delayed hooks and temp buffers instead of finding
|
||||
files <span class="underline">Gustav Wikström</span></li>
|
||||
<li>Improve generated <span class='acr'>HTML</span> quality: prevent W3C warning and add some accessibility
|
||||
labels <span class="underline"><span class='acr'>TEC</span></span></li>
|
||||
<li>Make the behaviour of the "goto variant" of <code>org-refile</code> (<code>org-speed-commands</code>)
|
||||
<li>Make the behaviour of the “goto variant” of <code>org-refile</code> (<code>org-speed-commands</code>)
|
||||
less confusing <span class="underline">Marco Wahl</span></li>
|
||||
<li>Backport an update to the OpenDocument schema <span class="underline">Kyle Meyer</span></li>
|
||||
</ul>
|
||||
|
|
@ -482,10 +482,10 @@ less confusing <span class="underline">Marco Wahl</span></li>
|
|||
<li>Off by one error in texinfo menu generation <span class="underline">Nicolas Goaziou</span></li>
|
||||
<li>Error in entry/conversion of non-24h times in the agenda <span class="underline">Nicolas Goaziou</span></li>
|
||||
<li>Only use <code>replace-buffer-contents</code> with Emacs 27+ when saving src blocks, as the
|
||||
behaviour isn't consistent until then <span class="underline">Nicolas Goaziou</span></li>
|
||||
<li>Prevent "before first headline" error in <kbd>org-clock</kbd> when clocking out <span class="underline">Nicolas Goaziou</span></li>
|
||||
behaviour isn’t consistent until then <span class="underline">Nicolas Goaziou</span></li>
|
||||
<li>Prevent “before first headline” error in <kbd>org-clock</kbd> when clocking out <span class="underline">Nicolas Goaziou</span></li>
|
||||
<li>Avoid setting the global agenda name when following a timestamp link <span class="underline">Ingo Lohmar</span></li>
|
||||
<li>Don't bind <kbd><tab></kbd> in <code>org-mode-map</code> <span class="underline">Nicolas Goaziou</span></li>
|
||||
<li>Don’t bind <kbd><tab></kbd> in <code>org-mode-map</code> <span class="underline">Nicolas Goaziou</span></li>
|
||||
<li>Erroneous tangling of source block with <kbd>:tangle no</kbd> to a file <kbd>no</kbd> when the
|
||||
tangle command is called with a single universal argument <span class="underline">Jacopo De Simoi</span></li>
|
||||
</ul>
|
||||
|
|
@ -505,8 +505,8 @@ and <a href="https://en.wikipedia.org/wiki/BibTeX">BibTeX</a>, with a number of
|
|||
</p></div></div>
|
||||
|
||||
<div class="footdef"><sup><a id="fn.3" class="footnum" href="#fnr.3" role="doc-backlink">3</a></sup> <div class="footpara" role="doc-footnote"><p class="footpara">
|
||||
I'm rather a fan of the <kbd>capitalize</kbd> option because (1) technically the
|
||||
reference to a named object is a proper noun, and (2) this means you don't have
|
||||
I’m rather a fan of the <kbd>capitalize</kbd> option because (1) technically the
|
||||
reference to a named object is a proper noun, and (2) this means you don’t have
|
||||
to worry about references not being capitalized when appearing at the start of a
|
||||
sentence.
|
||||
</p></div></div>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: June 2021
|
||||
#+date: 2021-06-34
|
||||
#+author: TEC
|
||||
|
|
|
|||
|
|
@ -11,10 +11,10 @@
|
|||
|
||||
The previous two months have been pretty good for Org development — with
|
||||
many bug fixes and feature improvements. This month has been
|
||||
substantially slower than the last[1], but that's not to say not much is
|
||||
substantially slower than the last[1], but that’s not to say not much is
|
||||
happening: in fact, there are some rather nifty contributions lined up
|
||||
for the not-too-distant future and a certain long-awaited feature
|
||||
branch[2] is getting very close to merging 😀. You'll just have to
|
||||
branch[2] is getting very close to merging 😀. You’ll just have to
|
||||
stick around to hear about those in a future edition of TMIO 😉.
|
||||
|
||||
<file:figures/dilbert-zenos-paradox.jpg>
|
||||
|
|
@ -31,7 +31,7 @@ Customise the reference command used in LaTeX
|
|||
<file:figures/org-latex-default-reference-to-sec.png>
|
||||
|
||||
You can now set the format string `org-latex-reference-command'
|
||||
(`\\ref{%s}' by default) to anything you'd like. For example, making
|
||||
(`\\ref{%s}' by default) to anything you’d like. For example, making
|
||||
use of the [cleveref] package I can set this to `\\cref{%s}' and then
|
||||
add `("capitalize" "cleveref" nil)'[3] to `org-latex-packages-alist'.
|
||||
|
||||
|
|
@ -46,11 +46,11 @@ A diversion into writing Org for LaTeX
|
|||
|
||||
Speaking of LaTeX exports, a member of the Org mailing list recently
|
||||
told us about [a paper] pushed to [arXiv] which was written /entirely/
|
||||
in Org. Why don't we use that as a prompt to talk a bit about
|
||||
in Org. Why don’t we use that as a prompt to talk a bit about
|
||||
generating LaTeX documents from Org?
|
||||
|
||||
For an experienced LaTeX-er, Org may initially appear best suited to
|
||||
simple documents, but in fact it's possible to reproduce any LaTeX
|
||||
simple documents, but in fact it’s possible to reproduce any LaTeX
|
||||
structure in Org with no more difficulty (often less) than in LaTeX.
|
||||
|
||||
|
||||
|
|
@ -61,13 +61,13 @@ A diversion into writing Org for LaTeX
|
|||
Simple elements
|
||||
───────────────
|
||||
|
||||
The "basic" Org elements are simply translated to their LaTeX
|
||||
The “basic” Org elements are simply translated to their LaTeX
|
||||
counterparts. Markup like *bold*, /italic/, etc. are simply
|
||||
translated through `org-latex-text-markup-alist'.
|
||||
|
||||
For those of us who dabble with equations, Org is [very
|
||||
accomodating]. You can type (LaTeX-style) inline and display equations
|
||||
in exactly the same way (`\( \)' and `\[ \]'), and what's more, if you
|
||||
in exactly the same way (`\( \)' and `\[ \]'), and what’s more, if you
|
||||
have a LaTeX environment statement `\begin{...}' on its own line, Org
|
||||
will recognise it and pass it into the generated LaTeX.
|
||||
|
||||
|
|
@ -154,7 +154,7 @@ Figures and tables
|
|||
|
||||
There are also some [more attributes] you can supply to tables. Should
|
||||
I want the table to spread out I could use `#+attr_latex: :environment
|
||||
tabularx' (as long as I've loaded the `tabularx' package) and then set
|
||||
tabularx' (as long as I’ve loaded the `tabularx' package) and then set
|
||||
the columns with `:align lX'.
|
||||
|
||||
|
||||
|
|
@ -168,7 +168,7 @@ Code blocks
|
|||
───────────
|
||||
|
||||
By default, source code blocks are translated verbatim. We can do
|
||||
better than that however. We can tell Org to use [listings], but I'd
|
||||
better than that however. We can tell Org to use [listings], but I’d
|
||||
recommend going one step further and using [minted]. For this to work
|
||||
we need to perform three actions:
|
||||
⁃ Tell Org we want to use `minted' environments for source code
|
||||
|
|
@ -205,7 +205,7 @@ Custom environments
|
|||
Org has a number of [blocks] which are treated specially, like
|
||||
`#+begin_src' for source code, and `#+begin_centre' for centred
|
||||
text. When exporting this same syntax allows you to wrap Org content
|
||||
in any LaTeX environments (as long as it doesn't match one of Org's
|
||||
in any LaTeX environments (as long as it doesn’t match one of Org’s
|
||||
recognised environments).
|
||||
|
||||
For example, if you wrote a `warning' environment in LaTeX to box and
|
||||
|
|
@ -234,7 +234,7 @@ The LaTeX escape hatches
|
|||
│ #+latex: \newpage
|
||||
└────
|
||||
|
||||
For larger snippets of LaTeX, there's always the export block.
|
||||
For larger snippets of LaTeX, there’s always the export block.
|
||||
┌────
|
||||
│ #+begin_export latex
|
||||
│ \cleardoublepage
|
||||
|
|
@ -265,7 +265,7 @@ Preamble content
|
|||
Should you want to use a certain preset preamble, you can make use of
|
||||
the `#+latex_class' keyword. This is used to set the base preamble
|
||||
template used when generating the LaTeX. See `org-latex-classes' for
|
||||
what's available by default. You should see entries for:
|
||||
what’s available by default. You should see entries for:
|
||||
⁃ article
|
||||
⁃ report
|
||||
⁃ book
|
||||
|
|
@ -275,14 +275,14 @@ Preamble content
|
|||
`#+latex_class' is set in the document, the template named by
|
||||
`org-latex-default-class' will be used.
|
||||
|
||||
What's great about this is that is makes it really easy to add your
|
||||
What’s great about this is that is makes it really easy to add your
|
||||
own templates. Each template simply takes three components:
|
||||
1. A name
|
||||
2. A preamble template
|
||||
3. A series of format strings to translate headings to LaTeX, with and
|
||||
without numbering
|
||||
|
||||
For example, I'm quite a fan of the [KOMA-script] family. Should I
|
||||
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
|
||||
do something like the following:
|
||||
┌────
|
||||
|
|
@ -308,13 +308,13 @@ Preamble content
|
|||
Other improvements
|
||||
══════════════════
|
||||
|
||||
⁃ `ox-koma-letter.el' has been brought into Org's main directory from
|
||||
⁃ `ox-koma-letter.el' has been brought into Org’s main directory from
|
||||
the ) `contrib/' repo _Bastien Guerry_
|
||||
⁃ Speed up publishing by using delayed hooks and temp buffers instead
|
||||
of finding files _Gustav Wikström_
|
||||
⁃ Improve generated HTML quality: prevent W3C warning and add some
|
||||
accessibility labels _TEC_
|
||||
⁃ Make the behaviour of the "goto variant" of `org-refile'
|
||||
⁃ Make the behaviour of the “goto variant” of `org-refile'
|
||||
(`org-speed-commands') less confusing _Marco Wahl_
|
||||
⁃ Backport an update to the OpenDocument schema _Kyle Meyer_
|
||||
|
||||
|
|
@ -326,13 +326,13 @@ Bugfixes
|
|||
⁃ Error in entry/conversion of non-24h times in the agenda _Nicolas
|
||||
Goaziou_
|
||||
⁃ Only use `replace-buffer-contents' with Emacs 27+ when saving src
|
||||
blocks, as the behaviour isn't consistent until then _Nicolas
|
||||
blocks, as the behaviour isn’t consistent until then _Nicolas
|
||||
Goaziou_
|
||||
⁃ Prevent "before first headline" error in `org-clock' when clocking
|
||||
⁃ Prevent “before first headline” error in `org-clock' when clocking
|
||||
out _Nicolas Goaziou_
|
||||
⁃ Avoid setting the global agenda name when following a timestamp link
|
||||
_Ingo Lohmar_
|
||||
⁃ Don't bind `<tab>' in `org-mode-map' _Nicolas Goaziou_
|
||||
⁃ Don’t bind `<tab>' in `org-mode-map' _Nicolas Goaziou_
|
||||
⁃ Erroneous tangling of source block with `:tangle no' to a file `no'
|
||||
when the tangle command is called with a single universal argument
|
||||
_Jacopo De Simoi_
|
||||
|
|
@ -349,7 +349,7 @@ for [CSL] (<https://citationstyles.org/>) and [BibTeX]
|
|||
(<https://en.wikipedia.org/wiki/BibTeX>), with a number of citation
|
||||
processors 🙌. Soon^{TM}
|
||||
|
||||
[3] I'm rather a fan of the `capitalize' option because (1)
|
||||
[3] I’m rather a fan of the `capitalize' option because (1)
|
||||
technically the reference to a named object is a proper noun, and (2)
|
||||
this means you don't have to worry about references not being
|
||||
this means you don’t have to worry about references not being
|
||||
capitalized when appearing at the start of a sentence.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>July 2021</title>
|
||||
|
|
@ -43,12 +43,12 @@
|
|||
<p class="subtitle" role="doc-subtitle">Introducing citations!</p>
|
||||
</header><p>
|
||||
Last month I not-at-all-subtly hinted that a certain long-awaited feature was
|
||||
arriving imminently. At this point, I think it's a good idea to set the tone for the rest of
|
||||
arriving imminently. At this point, I think it’s a good idea to set the tone for the rest of
|
||||
this post.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org6898ad8">
|
||||
<figure id="org0b07091">
|
||||
<img src="figures/celebrate-citations.svg" alt="celebrate-citations.svg" class="org-svg">
|
||||
|
||||
</figure>
|
||||
|
|
@ -57,17 +57,17 @@ this post.
|
|||
<div class="outline-text-2" id="text-citations">
|
||||
<p>
|
||||
After <i>years</i> of (on and off) discussion<sup><a id="fnr.1" class="footref" href="#fn.1" role="doc-backlink">1</a></sup>, I am elated to be able to present
|
||||
Org's new native citation syntax. Org has grown a thoroughly designed, modular,
|
||||
Org’s new native citation syntax. Org has grown a thoroughly designed, modular,
|
||||
capable citation system. At last you can refer to Org for all your attribution
|
||||
needs. Special thanks must go to Nicolas Goaziou for leading the charge, John
|
||||
Kitchin for paving the way with the <kbd>org-ref</kbd> package, Bruce D'Arcus for driving a
|
||||
Kitchin for paving the way with the <kbd>org-ref</kbd> package, Bruce D’Arcus for driving a
|
||||
lot of careful consideration of design decisions and starting to document some
|
||||
of the details — and the many other denizens of the mailing list who have
|
||||
contributed to the discussion over the years.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
András Simonyi's also deserves a special mention for his work creating the Elisp
|
||||
András Simonyi’s also deserves a special mention for his work creating the Elisp
|
||||
<span class='acr'>CSL</span> library <code>Citeproc.el</code>, which while not directly included in Org is crucial to
|
||||
providing robust <span class='acr'>CSL</span> support, and integrates with <kbd>oc-csl.el</kbd>.
|
||||
</p>
|
||||
|
|
@ -157,23 +157,23 @@ 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='org7282dd6' class='code' open>
|
||||
<details id='org4ae6a8f' class='code' open>
|
||||
<summary></summary>
|
||||
<div class='gutter'><a href='#org7282dd6'>#</a>
|
||||
<div class='gutter'><a href='#org4ae6a8f'>#</a>
|
||||
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
|
||||
<pre class="example" id="org7282dd6">
|
||||
<pre class="example" id="org4ae6a8f">
|
||||
#+bibliography: orgcite.bib
|
||||
</pre>
|
||||
|
||||
</details>
|
||||
|
||||
<p>
|
||||
Once you have a bibliography source, you can start referencing to your heart's
|
||||
Once you have a bibliography source, you can start referencing to your heart’s
|
||||
content! The basic citation syntax is as follows:
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="orge96e856">
|
||||
<figure id="org721f3f8">
|
||||
<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='org9348862' class='code' open>
|
||||
<details id='org9df92d6' class='code' open>
|
||||
<summary></summary>
|
||||
<div class='gutter'><a href='#org9348862'>#</a>
|
||||
<div class='gutter'><a href='#org9df92d6'>#</a>
|
||||
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
|
||||
<pre class="example" id="org9348862">
|
||||
<pre class="example" id="org9df92d6">
|
||||
#+print_bibliography:
|
||||
</pre>
|
||||
|
||||
</details>
|
||||
|
||||
<div class="info" id="orgf35d8be">
|
||||
<div class="info" id="org5a6bfbe">
|
||||
<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='org13233ab' class='code' open>
|
||||
<details id='org125df34' class='code' open>
|
||||
<summary></summary>
|
||||
<div class='gutter'><a href='#org13233ab'>#</a>
|
||||
<div class='gutter'><a href='#org125df34'>#</a>
|
||||
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
|
||||
<pre class="example" id="org13233ab">
|
||||
<pre class="example" id="org125df34">
|
||||
#+bibliography: references.bib
|
||||
[cite:@key]
|
||||
#+print_bibliography:
|
||||
|
|
@ -221,7 +221,7 @@ So, to summarise, all one needs to get started is:
|
|||
|
||||
</details>
|
||||
<p>
|
||||
That's it! 🎉
|
||||
That’s it! 🎉
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -229,13 +229,13 @@ That's it! 🎉
|
|||
<h3 id="cite-syntax">The cite syntax<a aria-hidden="true" href="#cite-syntax">#</a> </h3>
|
||||
<div class="outline-text-3" id="text-cite-syntax">
|
||||
<p>
|
||||
Don't let the simplicity in the examples above fool you, the new syntax is quite
|
||||
capable of expressing more complex forms. Here's the <i>full</i> version of the new
|
||||
Don’t let the simplicity in the examples above fool you, the new syntax is quite
|
||||
capable of expressing more complex forms. Here’s the <i>full</i> version of the new
|
||||
cite syntax:
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org9f717cf">
|
||||
<figure id="org1074ca2">
|
||||
<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>
|
||||
|
|
@ -261,7 +261,7 @@ Using the default <span class='acr'>CSL</span> citation style (Chicago author-na
|
|||
|
||||
<p>
|
||||
The citation styles and variants, and recognised locators are handled by the
|
||||
citation processors. Org cite's bundled processors currently supports the
|
||||
citation processors. Org cite’s bundled processors currently supports the
|
||||
following citation styles.
|
||||
</p>
|
||||
|
||||
|
|
@ -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='orgc3254e9' class='code' open>
|
||||
<details id='org60a54b9' class='code' open>
|
||||
<summary></summary>
|
||||
<div class='gutter'><a href='#orgc3254e9'>#</a>
|
||||
<div class='gutter'><a href='#org60a54b9'>#</a>
|
||||
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
|
||||
<pre class="example" id="orgc3254e9">
|
||||
<pre class="example" id="org60a54b9">
|
||||
#+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='orgcdfba21' class='code' open>
|
||||
<details id='org65a9b55' class='code' open>
|
||||
<summary></summary>
|
||||
<div class='gutter'><a href='#orgcdfba21'>#</a>
|
||||
<div class='gutter'><a href='#org65a9b55'>#</a>
|
||||
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
|
||||
<pre class="example" id="orgcdfba21">
|
||||
<pre class="example" id="org65a9b55">
|
||||
#+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='org8e8611d' class='code' open>
|
||||
<details id='org62f4f7e' class='code' open>
|
||||
<summary></summary>
|
||||
<div class='gutter'><a href='#org8e8611d'>#</a>
|
||||
<div class='gutter'><a href='#org62f4f7e'>#</a>
|
||||
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
|
||||
<pre class="example" id="org8e8611d">
|
||||
<pre class="example" id="org62f4f7e">
|
||||
#+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='orgb8c48a4' class='code' open>
|
||||
<details id='org4d92789' class='code' open>
|
||||
<summary></summary>
|
||||
<div class='gutter'><a href='#orgb8c48a4'>#</a>
|
||||
<div class='gutter'><a href='#org4d92789'>#</a>
|
||||
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
|
||||
<pre class="example" id="orgb8c48a4">
|
||||
<pre class="example" id="org4d92789">
|
||||
#+cite_export: csl ~/Downloads/apa.csl
|
||||
</pre>
|
||||
|
||||
|
|
@ -667,21 +667,21 @@ shrinks if you restrict yourself to applications which are:
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<a href="https://www.zotero.org/">Zotero</a> is a good option, and if you're using it it's quite easy to use it with
|
||||
<a href="https://www.zotero.org/">Zotero</a> is a good option, and if you’re using it it’s quite easy to use it with
|
||||
Org Cite. Out of the box, you can tell it to export your library, or parts of it,
|
||||
to a <kbd>.bib</kbd> file and automatically keep it in sync. I'd recommend installing the
|
||||
to a <kbd>.bib</kbd> file and automatically keep it in sync. I’d recommend installing the
|
||||
<a href="https://retorque.re/zotero-better-bibtex/">Better BibTeX</a> extension though.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="orge6b34f3">
|
||||
<figure id="org3421fca">
|
||||
<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="org13fe646">
|
||||
<figure id="org36de69f">
|
||||
<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="orgaff19e1">
|
||||
<figure id="orgb936c75">
|
||||
<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='org7322f9e' class='code' open>
|
||||
<details id='org00c3ad4' class='code' open>
|
||||
<summary></summary>
|
||||
<div class='gutter'><a href='#org7322f9e'>#</a>
|
||||
<div class='gutter'><a href='#org00c3ad4'>#</a>
|
||||
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
|
||||
<pre class="example" id="org7322f9e">
|
||||
<pre class="example" id="org00c3ad4">
|
||||
#+cite_export: csl apa.csl
|
||||
</pre>
|
||||
|
||||
|
|
@ -734,9 +734,9 @@ simply refer to <kbd>apa.csl</kbd> when using the <kbd>#+cite_export</kbd> keywo
|
|||
<div class="outline-text-3" id="text-bright-future">
|
||||
<p>
|
||||
Org Cite has only just been merged in the past month, and is yet to be included
|
||||
in an Org release, but we're seeing a tremendous degree of community interest.
|
||||
in an Org release, but we’re seeing a tremendous degree of community interest.
|
||||
There are <i>already</i> promising developments with third-party packages, such as
|
||||
<a href="https://github.com/bdarcus/bibtex-actions">bibtex-actions</a> and <a href="https://github.com/jkitchin/org-ref-cite">org-ref-cite</a>. I can't wait to see how the ecosystem continues
|
||||
<a href="https://github.com/bdarcus/bibtex-actions">bibtex-actions</a> and <a href="https://github.com/jkitchin/org-ref-cite">org-ref-cite</a>. I can’t wait to see how the ecosystem continues
|
||||
to develop 😃.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -757,13 +757,13 @@ produce citation overlays in the buffer.
|
|||
</p></div></div>
|
||||
|
||||
<div class="footdef"><sup><a id="fn.3" class="footnum" href="#fnr.3" role="doc-backlink">3</a></sup> <div class="footpara" role="doc-footnote"><p class="footpara">
|
||||
I'm talking about a certain company <a href="https://moneyweek.com/505757/great-frauds-in-history-robert-maxwell">created by a British Fraudster</a> that
|
||||
I’m talking about a certain company <a href="https://moneyweek.com/505757/great-frauds-in-history-robert-maxwell">created by a British Fraudster</a> that
|
||||
has a <a href="https://www.theguardian.com/science/2017/jun/27/profitable-business-scientific-publishing-bad-for-science">40% profit margin, engages in blackmail-like practices with universities</a>,
|
||||
prompted <a href="http://thecostofknowledge.com/">19,000 researchers</a> to boycott them, <a href="https://www.the-scientist.com/the-nutshell/elsevier-published-6-fake-journals-44160">published six fake journals</a>,
|
||||
vigorously <a href="https://web.archive.org/web/20200129202353/http://legacy.earlham.edu/~peters/fos/2007/08/publishers-launch-anti-oa-lobbying.html">lobbys against Open Access</a>, <a href="https://rossmounce.co.uk/2017/02/14/elsevier-selling-access-to-open-access-again/">charged for Open Acess articles</a>
|
||||
(repeatedly), made <a href="https://www.michaeleisen.org/blog/?p=807">financial contributions to politicians who then tried to
|
||||
prevent publicly accesible reaserch</a>, and whose reference manager <a href="https://www.zotero.org/support/kb/mendeley_import#mendeley_database_encryption">encrypted
|
||||
reaserchers' <i>own</i> databases</a> "to comply with <span class='acr'>GDPR</span>".
|
||||
reaserchers’ <i>own</i> databases</a> “to comply with <span class='acr'>GDPR</span>”.
|
||||
</p></div></div>
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: July 2021
|
||||
#+date: 2021-07-31
|
||||
#+author: TEC
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@
|
|||
|
||||
|
||||
Last month I not-at-all-subtly hinted that a certain long-awaited
|
||||
feature was arriving imminently. At this point, I think it's a good idea
|
||||
feature was arriving imminently. At this point, I think it’s a good idea
|
||||
to set the tone for the rest of this post.
|
||||
|
||||
<file:figures/celebrate-citations.svg>
|
||||
|
|
@ -20,16 +20,16 @@ Citations
|
|||
═════════
|
||||
|
||||
After /years/ of (on and off) discussion[1], I am elated to be able to
|
||||
present Org's new native citation syntax. Org has grown a thoroughly
|
||||
present Org’s new native citation syntax. Org has grown a thoroughly
|
||||
designed, modular, capable citation system. At last you can refer to
|
||||
Org for all your attribution needs. Special thanks must go to Nicolas
|
||||
Goaziou for leading the charge, John Kitchin for paving the way with
|
||||
the `org-ref' package, Bruce D'Arcus for driving a lot of careful
|
||||
the `org-ref' package, Bruce D’Arcus for driving a lot of careful
|
||||
consideration of design decisions and starting to document some of the
|
||||
details — and the many other denizens of the mailing list who have
|
||||
contributed to the discussion over the years.
|
||||
|
||||
András Simonyi's also deserves a special mention for his work creating
|
||||
András Simonyi’s also deserves a special mention for his work creating
|
||||
the Elisp CSL library `Citeproc.el', which while not directly included
|
||||
in Org is crucial to providing robust CSL support, and integrates with
|
||||
`oc-csl.el'.
|
||||
|
|
@ -118,7 +118,7 @@ Basic usage
|
|||
└────
|
||||
|
||||
Once you have a bibliography source, you can start referencing to your
|
||||
heart's content! The basic citation syntax is as follows:
|
||||
heart’s content! The basic citation syntax is as follows:
|
||||
|
||||
<file:figures/citation-structure-basic.svg>
|
||||
|
||||
|
|
@ -143,14 +143,14 @@ Basic usage
|
|||
│ [cite:@key]
|
||||
│ #+print_bibliography:
|
||||
└────
|
||||
That's it! 🎉
|
||||
That’s it! 🎉
|
||||
|
||||
|
||||
The cite syntax
|
||||
───────────────
|
||||
|
||||
Don't let the simplicity in the examples above fool you, the new
|
||||
syntax is quite capable of expressing more complex forms. Here's the
|
||||
Don’t let the simplicity in the examples above fool you, the new
|
||||
syntax is quite capable of expressing more complex forms. Here’s the
|
||||
/full/ version of the new cite syntax:
|
||||
|
||||
<file:figures/citation-structure-full.svg>
|
||||
|
|
@ -170,7 +170,7 @@ The cite syntax
|
|||
`[cite/l/b:see @OrgCitations pp. 7 for fun]' becomes see 7 for fun.
|
||||
|
||||
The citation styles and variants, and recognised locators are handled
|
||||
by the citation processors. Org cite's bundled processors currently
|
||||
by the citation processors. Org cite’s bundled processors currently
|
||||
supports the following citation styles.
|
||||
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
|
@ -320,10 +320,10 @@ Working with Zotero
|
|||
⁃ open source software
|
||||
⁃ not owned by a parasitic company[3]
|
||||
|
||||
[Zotero] is a good option, and if you're using it it's quite easy to
|
||||
[Zotero] is a good option, and if you’re using it it’s quite easy to
|
||||
use it with Org Cite. Out of the box, you can tell it to export your
|
||||
library, or parts of it, to a `.bib' file and automatically keep it in
|
||||
sync. I'd recommend installing the [Better BibTeX] extension though.
|
||||
sync. I’d recommend installing the [Better BibTeX] extension though.
|
||||
|
||||
<file:figures/zotero-export-library.png>
|
||||
|
||||
|
|
@ -359,10 +359,10 @@ A bright future
|
|||
───────────────
|
||||
|
||||
Org Cite has only just been merged in the past month, and is yet to be
|
||||
included in an Org release, but we're seeing a tremendous degree of
|
||||
included in an Org release, but we’re seeing a tremendous degree of
|
||||
community interest. There are /already/ promising developments with
|
||||
third-party packages, such as [bibtex-actions] and [org-ref-cite]. I
|
||||
can't wait to see how the ecosystem continues to develop 😃.
|
||||
can’t wait to see how the ecosystem continues to develop 😃.
|
||||
|
||||
|
||||
[bibtex-actions] <https://github.com/bdarcus/bibtex-actions>
|
||||
|
|
@ -382,7 +382,7 @@ Footnotes
|
|||
(<https://github.com/andras-simonyi/org-cite-csl-activate>) to use
|
||||
`oc.el' and `citeproc.el' to produce citation overlays in the buffer.
|
||||
|
||||
[3] I'm talking about a certain company [created by a British
|
||||
[3] I’m talking about a certain company [created by a British
|
||||
Fraudster]
|
||||
(<https://moneyweek.com/505757/great-frauds-in-history-robert-maxwell>)
|
||||
that has a [40% profit margin, engages in blackmail-like practices
|
||||
|
|
@ -398,6 +398,6 @@ vigorously [lobbys against Open Access]
|
|||
(repeatedly), made [financial contributions to politicians who then
|
||||
tried to prevent publicly accesible reaserch]
|
||||
(<https://www.michaeleisen.org/blog/?p=807>), and whose reference
|
||||
manager [encrypted reaserchers' /own/ databases]
|
||||
manager [encrypted reaserchers’ /own/ databases]
|
||||
(<https://www.zotero.org/support/kb/mendeley_import#mendeley_database_encryption>)
|
||||
"to comply with GDPR".
|
||||
“to comply with GDPR”.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>August 2021</title>
|
||||
|
|
@ -62,14 +62,14 @@ MathJax = {
|
|||
<p class="subtitle" role="doc-subtitle">Roaming around</p>
|
||||
</header><blockquote>
|
||||
<p>
|
||||
Dear readers, unfortunately I've been unusually busy as of late, and will
|
||||
continue to be for a bit over a month. As such, it's entirely likely that the
|
||||
Dear readers, unfortunately I’ve been unusually busy as of late, and will
|
||||
continue to be for a bit over a month. As such, it’s entirely likely that the
|
||||
next post or two may <del>be late</del> make use of creative dates too.
|
||||
</p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
In terms of Org development, we've had a fairly slow month — mostly tweaks and
|
||||
In terms of Org development, we’ve had a fairly slow month — mostly tweaks and
|
||||
fixes, concentrated on the new org-cite functionality. However, there have been
|
||||
big developments with Roam as of late.
|
||||
</p>
|
||||
|
|
@ -77,14 +77,14 @@ big developments with Roam as of late.
|
|||
<h2 id="org-roam-v2"><a href="https://github.com/org-roam/org-roam">Org-roam v2</a><a aria-hidden="true" href="#org-roam-v2">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-org-roam-v2">
|
||||
<p>
|
||||
Pushed to the sidelines by last month's hugely significant citations
|
||||
announcement was the release of Org-roam v2 🎉. The project's author Jethro
|
||||
wrote a nice <a href="https://blog.jethro.dev/posts/org_roam_v2/">blog post</a> outlining the major changes and motivations, and so I'll
|
||||
Pushed to the sidelines by last month’s hugely significant citations
|
||||
announcement was the release of Org-roam v2 🎉. The project’s author Jethro
|
||||
wrote a nice <a href="https://blog.jethro.dev/posts/org_roam_v2/">blog post</a> outlining the major changes and motivations, and so I’ll
|
||||
leave him to speak on that. Suffice to say, the idea of org-roam has been
|
||||
refined into a form that should better server tinkerers looking to build off Org
|
||||
roam, and make maintenance easier — thus improving the user experience in the
|
||||
long term 🙂. Should you be worried that the v1 → v2 upgrade will be painful,
|
||||
read <a href="https://macowners.club/posts/org-roam-v2-doesnt-hurt/">Org-roam v2 doesn't hurt</a>, relax, and try the upgrade wizard.
|
||||
read <a href="https://macowners.club/posts/org-roam-v2-doesnt-hurt/">Org-roam v2 doesn’t hurt</a>, relax, and try the upgrade wizard.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -92,15 +92,15 @@ read <a href="https://macowners.club/posts/org-roam-v2-doesnt-hurt/">Org-roam v2
|
|||
<h2 id="org-roam-ui"><a href="https://github.com/org-roam/org-roam-ui/">Org-roam-ui</a><a aria-hidden="true" href="#org-roam-ui">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-org-roam-ui">
|
||||
<p>
|
||||
Within a month of Roam v2's announcement, we were pleasantly surprised by the
|
||||
Within a month of Roam v2’s announcement, we were pleasantly surprised by the
|
||||
release of <a href="https://github.com/org-roam/org-roam-server">org-roam-server</a> usurper — org-roam-ui.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="orgccbd2c5">
|
||||
<figure id="org178ef09">
|
||||
<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>
|
||||
<figcaption><span class="figure-number">Figure 1: </span>org-roam-ui’s 2D overview.</figcaption>
|
||||
</figure>
|
||||
|
||||
<p>
|
||||
|
|
@ -128,7 +128,7 @@ graph view and the currently open roam file in Emacs. Furthermore, with
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org6ade445">
|
||||
<figure id="orged74fed">
|
||||
<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>
|
||||
|
|
@ -149,7 +149,7 @@ filtering and theme syncing, with more in the works. To see more, check out the
|
|||
<h2 id="new-context-exporter">New ConTeXt exporter<a aria-hidden="true" href="#new-context-exporter">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-new-context-exporter">
|
||||
<p>
|
||||
We've long been able to export to LaTeX files with <kbd>ox-latex</kbd>, but now you can
|
||||
We’ve long been able to export to LaTeX files with <kbd>ox-latex</kbd>, but now you can
|
||||
export to ConTeXt too with <a href="https://github.com/Jason-S-Ross/ox-context">ox-context</a>! While only just released, a lot of work
|
||||
has already gone into this — with development starting almost a year ago by the
|
||||
commit history.
|
||||
|
|
@ -160,7 +160,7 @@ commit history.
|
|||
</p>
|
||||
|
||||
<p>
|
||||
It's always nice to see more export options for Org, and I wish Jason all the
|
||||
It’s always nice to see more export options for Org, and I wish Jason all the
|
||||
best in developing <kbd>ox-context</kbd>.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -172,7 +172,7 @@ best in developing <kbd>ox-context</kbd>.
|
|||
<li>Refactor <kbd>oc-natbib.el</kbd>, <kbd>oc-biblatex</kbd>, <kbd>oc-basic.el</kbd>, <kbd>org-compat.el</kbd> to improve byte
|
||||
compilation <span class="underline">Maxim Nikulin</span> <span class="underline">Nicolas Goaziou</span> <span class="underline">Marco Wahl</span></li>
|
||||
<li>Allow for selecting cite style with a citation argument <span class="underline">Nicolas Goaziou</span></li>
|
||||
<li>Add support for Italian "smart quotes" <span class="underline">DPDmancul</span></li>
|
||||
<li>Add support for Italian “smart quotes” <span class="underline">DPDmancul</span></li>
|
||||
<li>Fix Spanish mistranslation in footnote Documentation <span class="underline">Juan Manuel Macias</span></li>
|
||||
<li>Define <kbd>\citeprocitem</kbd> in <kbd>oc-csl.el</kbd> for use by <kbd>citeproc-el</kbd> <span class="underline"><span class='acr'>TEC</span></span></li>
|
||||
<li>Fix error in <kbd>org-export-define-backend</kbd> docstring <span class="underline">Zachary Kanfer</span> <span class="underline">Nicolas Goaziou</span></li>
|
||||
|
|
@ -203,8 +203,8 @@ matched <span class="underline"><span class='acr'>DMG</span>, Nicolas Goaziou</s
|
|||
|
||||
<div class="footdef"><sup><a id="fn.1" class="footnum" href="#fnr.1" role="doc-backlink">1</a></sup> <div class="footpara" role="doc-footnote"><p class="footpara">
|
||||
I have found the <kbd>xwidget-webkit</kbd> experience quite unstable until I
|
||||
started using Emacs 28 with the pure-<span class='acr'>GTK</span> branch. So, if you're not getting a
|
||||
good experience now, there's a good chance you'll have a better experience in
|
||||
started using Emacs 28 with the pure-<span class='acr'>GTK</span> branch. So, if you’re not getting a
|
||||
good experience now, there’s a good chance you’ll have a better experience in
|
||||
the future.
|
||||
</p></div></div>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: August 2021
|
||||
#+date: 2021-08-38
|
||||
#+author: TEC
|
||||
|
|
|
|||
|
|
@ -9,12 +9,12 @@
|
|||
2021-08-38
|
||||
|
||||
|
||||
Dear readers, unfortunately I've been unusually busy as of
|
||||
Dear readers, unfortunately I’ve been unusually busy as of
|
||||
late, and will continue to be for a bit over a month. As
|
||||
such, it's entirely likely that the next post or two may +be
|
||||
such, it’s entirely likely that the next post or two may +be
|
||||
late+ make use of creative dates too.
|
||||
|
||||
In terms of Org development, we've had a fairly slow month — mostly
|
||||
In terms of Org development, we’ve had a fairly slow month — mostly
|
||||
tweaks and fixes, concentrated on the new org-cite
|
||||
functionality. However, there have been big developments with Roam as of
|
||||
late.
|
||||
|
|
@ -23,29 +23,29 @@ late.
|
|||
[Org-roam v2]
|
||||
═════════════
|
||||
|
||||
Pushed to the sidelines by last month's hugely significant citations
|
||||
announcement was the release of Org-roam v2 🎉. The project's author
|
||||
Pushed to the sidelines by last month’s hugely significant citations
|
||||
announcement was the release of Org-roam v2 🎉. The project’s author
|
||||
Jethro wrote a nice [blog post] outlining the major changes and
|
||||
motivations, and so I'll leave him to speak on that. Suffice to say,
|
||||
motivations, and so I’ll leave him to speak on that. Suffice to say,
|
||||
the idea of org-roam has been refined into a form that should better
|
||||
server tinkerers looking to build off Org roam, and make maintenance
|
||||
easier — thus improving the user experience in the long term
|
||||
🙂. Should you be worried that the v1 -> v2 upgrade will be painful,
|
||||
read [Org-roam v2 doesn't hurt], relax, and try the upgrade wizard.
|
||||
read [Org-roam v2 doesn’t hurt], relax, and try the upgrade wizard.
|
||||
|
||||
|
||||
[Org-roam v2] <https://github.com/org-roam/org-roam>
|
||||
|
||||
[blog post] <https://blog.jethro.dev/posts/org_roam_v2/>
|
||||
|
||||
[Org-roam v2 doesn't hurt]
|
||||
[Org-roam v2 doesn’t hurt]
|
||||
<https://macowners.club/posts/org-roam-v2-doesnt-hurt/>
|
||||
|
||||
|
||||
[Org-roam-ui]
|
||||
═════════════
|
||||
|
||||
Within a month of Roam v2's announcement, we were pleasantly surprised
|
||||
Within a month of Roam v2’s announcement, we were pleasantly surprised
|
||||
by the release of [org-roam-server] usurper — org-roam-ui.
|
||||
|
||||
<file:figures/org-roam-graph-2d-overview.png>
|
||||
|
|
@ -83,14 +83,14 @@ late.
|
|||
New ConTeXt exporter
|
||||
════════════════════
|
||||
|
||||
We've long been able to export to LaTeX files with `ox-latex', but now
|
||||
We’ve long been able to export to LaTeX files with `ox-latex', but now
|
||||
you can export to ConTeXt too with [ox-context]! While only just
|
||||
released, a lot of work has already gone into this — with development
|
||||
starting almost a year ago by the commit history.
|
||||
|
||||
//github.com/Jason-S-Ross/ox-context
|
||||
|
||||
It's always nice to see more export options for Org, and I wish Jason
|
||||
It’s always nice to see more export options for Org, and I wish Jason
|
||||
all the best in developing `ox-context'.
|
||||
|
||||
|
||||
|
|
@ -105,7 +105,7 @@ Other improvements
|
|||
Goaziou_ _Marco Wahl_
|
||||
⁃ Allow for selecting cite style with a citation argument _Nicolas
|
||||
Goaziou_
|
||||
⁃ Add support for Italian "smart quotes" _DPDmancul_
|
||||
⁃ Add support for Italian “smart quotes” _DPDmancul_
|
||||
⁃ Fix Spanish mistranslation in footnote Documentation _Juan Manuel
|
||||
Macias_
|
||||
⁃ Define `\citeprocitem' in `oc-csl.el' for use by `citeproc-el' _TEC_
|
||||
|
|
@ -138,6 +138,6 @@ Footnotes
|
|||
─────────
|
||||
|
||||
[1] I have found the `xwidget-webkit' experience quite unstable until
|
||||
I started using Emacs 28 with the pure-GTK branch. So, if you're not
|
||||
getting a good experience now, there's a good chance you'll have a
|
||||
I started using Emacs 28 with the pure-GTK branch. So, if you’re not
|
||||
getting a good experience now, there’s a good chance you’ll have a
|
||||
better experience in the future.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>October 2021</title>
|
||||
|
|
@ -43,15 +43,15 @@
|
|||
<p class="subtitle" role="doc-subtitle">Release 9.5</p>
|
||||
</header><blockquote>
|
||||
<p>
|
||||
Turns out that life became busy enough that instead of delaying, last month's
|
||||
post had to be cancelled. We're now back to business as usual though 🙂.
|
||||
Turns out that life became busy enough that instead of delaying, last month’s
|
||||
post had to be cancelled. We’re now back to business as usual though 🙂.
|
||||
</p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
There have been some cool recent developments in Org over the past two months,
|
||||
but you'll have to learn about those is next month's edition as <i>Org 9.5 has been
|
||||
released</i> 🎉. So, let's go over some of the changes I'm most excited about, in no
|
||||
but you’ll have to learn about those is next month’s edition as <i>Org 9.5 has been
|
||||
released</i> 🎉. So, let’s go over some of the changes I’m most excited about, in no
|
||||
particular order. To get a more complete picture of the latest changes, see
|
||||
<a href="https://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/etc/ORG-NEWS?h=release_9.5#n14"><span class='acr'>ORG</span>-<span class='acr'>NEWS</span></a>.
|
||||
</p>
|
||||
|
|
@ -59,8 +59,8 @@ particular order. To get a more complete picture of the latest changes, see
|
|||
<h2 id="new-citation-engine">The new citation engine<a aria-hidden="true" href="#new-citation-engine">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-new-citation-engine">
|
||||
<p>
|
||||
As tempted as I am to wax lyrical about the lovely new citation engine, I've
|
||||
already dedicated <a href="2021-07-31-citations.html">July's post</a> to it, and so will simply highlight how versatile
|
||||
As tempted as I am to wax lyrical about the lovely new citation engine, I’ve
|
||||
already dedicated <a href="2021-07-31-citations.html">July’s post</a> to it, and so will simply highlight how versatile
|
||||
the syntax is. Combined with the ability to swap out the default backends
|
||||
(basic, <span class='acr'>CSL</span>, natbib, and bib(la)tex) for a 3rd party backend (for example,
|
||||
provided by a package) it is capable of meeting your citation and technical
|
||||
|
|
@ -68,7 +68,7 @@ document publishing needs, whatever they may be.
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org3d5d213">
|
||||
<figure id="org38c4d6c">
|
||||
<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>
|
||||
|
|
@ -76,13 +76,13 @@ document publishing needs, whatever they may be.
|
|||
|
||||
<p>
|
||||
Since the announcement of org-cite, the ecosystem has continued to expand with a
|
||||
number of promising packages like Bruce D'Arcus' <a href="https://github.com/bdarcus/citar">citar</a> (previously
|
||||
number of promising packages like Bruce D’Arcus’ <a href="https://github.com/bdarcus/citar">citar</a> (previously
|
||||
<i>bibtex-actions</i>), which currently provides what is arguably the best citation
|
||||
insertion experience.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="orgbc1feea">
|
||||
<figure id="org95924c1">
|
||||
<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>
|
||||
|
|
@ -93,7 +93,7 @@ insertion experience.
|
|||
<h2 id="asynchronous-session-evaluation">Asynchronous session evaluation<a aria-hidden="true" href="#asynchronous-session-evaluation">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-asynchronous-session-evaluation">
|
||||
<p>
|
||||
Since being featured in <a href="2021-05-31-async.html">May's post</a>, we've had the initial python support
|
||||
Since being featured in <a href="2021-05-31-async.html">May’s post</a>, we’ve had the initial python support
|
||||
expanded with support for R too. I have good reason to believe that more
|
||||
backends will join this list in the future.
|
||||
</p>
|
||||
|
|
@ -124,7 +124,7 @@ and more.
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org25cb2f8">
|
||||
<figure id="orgd10e7b4">
|
||||
<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>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: October 2021
|
||||
#+date: 2021-10-31
|
||||
#+author: TEC
|
||||
|
|
|
|||
|
|
@ -10,13 +10,13 @@
|
|||
|
||||
|
||||
Turns out that life became busy enough that instead of
|
||||
delaying, last month's post had to be cancelled. We're now
|
||||
delaying, last month’s post had to be cancelled. We’re now
|
||||
back to business as usual though 🙂.
|
||||
|
||||
There have been some cool recent developments in Org over the past two
|
||||
months, but you'll have to learn about those is next month's edition as
|
||||
/Org 9.5 has been released/ 🎉. So, let's go over some of the changes
|
||||
I'm most excited about, in no particular order. To get a more complete
|
||||
months, but you’ll have to learn about those is next month’s edition as
|
||||
/Org 9.5 has been released/ 🎉. So, let’s go over some of the changes
|
||||
I’m most excited about, in no particular order. To get a more complete
|
||||
picture of the latest changes, see [ORG-NEWS].
|
||||
|
||||
|
||||
|
|
@ -28,7 +28,7 @@ The new citation engine
|
|||
═══════════════════════
|
||||
|
||||
As tempted as I am to wax lyrical about the lovely new citation
|
||||
engine, I've already dedicated [July's post] to it, and so will simply
|
||||
engine, I’ve already dedicated [July’s post] to it, and so will simply
|
||||
highlight how versatile the syntax is. Combined with the ability to
|
||||
swap out the default backends (basic, CSL, natbib, and bib(la)tex) for
|
||||
a 3rd party backend (for example, provided by a package) it is capable
|
||||
|
|
@ -38,14 +38,14 @@ The new citation engine
|
|||
<file:figures/citation-structure-full.svg>
|
||||
|
||||
Since the announcement of org-cite, the ecosystem has continued to
|
||||
expand with a number of promising packages like Bruce D'Arcus' [citar]
|
||||
expand with a number of promising packages like Bruce D’Arcus’ [citar]
|
||||
(previously /bibtex-actions/), which currently provides what is
|
||||
arguably the best citation insertion experience.
|
||||
|
||||
<file:figures/org-citar-insertion.png>
|
||||
|
||||
|
||||
[July's post] <file:2021-07-31-citations.org>
|
||||
[July’s post] <file:2021-07-31-citations.org>
|
||||
|
||||
[citar] <https://github.com/bdarcus/citar>
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ The new citation engine
|
|||
Asynchronous session evaluation
|
||||
═══════════════════════════════
|
||||
|
||||
Since being featured in [May's post], we've had the initial python
|
||||
Since being featured in [May’s post], we’ve had the initial python
|
||||
support expanded with support for R too. I have good reason to believe
|
||||
that more backends will join this list in the future.
|
||||
|
||||
|
|
@ -61,7 +61,7 @@ Asynchronous session evaluation
|
|||
R source blocks with a `:session'.
|
||||
|
||||
|
||||
[May's post] <file:2021-05-31-async.org>
|
||||
[May’s post] <file:2021-05-31-async.org>
|
||||
|
||||
|
||||
LaTeX environment `#+results' are now removed
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>November 2021</title>
|
||||
|
|
@ -42,8 +42,8 @@
|
|||
<h1 class="title">November 2021</h1>
|
||||
<p class="subtitle" role="doc-subtitle">Elementary improvements</p>
|
||||
</header><p>
|
||||
With a 9.5 release highlight post last month, and the month before skipped, it's
|
||||
now <i>three months</i> since the last regular instalment of <span class='acr'>TMIO</span>. Let's get back up
|
||||
With a 9.5 release highlight post last month, and the month before skipped, it’s
|
||||
now <i>three months</i> since the last regular instalment of <span class='acr'>TMIO</span>. Let’s get back up
|
||||
to date on some of the latest happenings with Org.
|
||||
</p>
|
||||
<div id="outline-container-org-as-markup" class="outline-2">
|
||||
|
|
@ -53,8 +53,8 @@ to date on some of the latest happenings with Org.
|
|||
Looking at the wider ecosystem, it certainly appears that there is a growing
|
||||
appetite for Org markup outside org-mode. More projects like <a href="https://gohugo.io/">Hugo</a> and <a href="https://logseq.com/">Logseq</a>
|
||||
seem to be interested in supporting Org markup, and there has been a recent
|
||||
growth in editor extensions like Neovim's <a href="https://github.com/nvim-orgmode/orgmode/">orgmode.nvim</a> (started in March this
|
||||
year) and Sublime Text's <a href="https://packagecontrol.io/packages/OrgExtended">OrgExtended</a> (started in June this year).
|
||||
growth in editor extensions like Neovim’s <a href="https://github.com/nvim-orgmode/orgmode/">orgmode.nvim</a> (started in March this
|
||||
year) and Sublime Text’s <a href="https://packagecontrol.io/packages/OrgExtended">OrgExtended</a> (started in June this year).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -63,7 +63,7 @@ project. Primarily lead by Nicolas Goaziou, there is an ongoing attempt to
|
|||
codify the Org syntax in a formal specification in the Worg document <a href="https://orgmode.org/worg/dev/org-syntax.html">Org Syntax
|
||||
(draft)</a>. Other members of the Org mailing list have directed their effort to
|
||||
creating non-elisp parsers for Org, both to help Org tools be created in other
|
||||
languages, and as put in the <span class='acr'>README</span> for Tom Gillespie's <a href="https://github.com/tgbugs/laundry">laundry</a> parser
|
||||
languages, and as put in the <span class='acr'>README</span> for Tom Gillespie’s <a href="https://github.com/tgbugs/laundry">laundry</a> parser
|
||||
</p>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -77,15 +77,15 @@ for an implementation of Org mode.
|
|||
Earlier this week Karl Voit, the author of the rather well-known document <a href="https://karl-voit.at/2017/09/23/orgmode-as-markup-only/">Org
|
||||
Mode Is One of the Most Reasonable Markup Languages to Use for Text</a>, surprised
|
||||
the mailing list by announcing his independent creation of a multi-leveled
|
||||
standard for Org syntax subsets called "Orgdown" (the name is a blend of
|
||||
"Org-mode" and "markdown", but the standard is only a subset of Org). Each level
|
||||
standard for Org syntax subsets called “Orgdown” (the name is a blend of
|
||||
“Org-mode” and “markdown”, but the standard is only a subset of Org). Each level
|
||||
defines a compliance score given by a mix of parsing and editing support, with
|
||||
example compliance scores for the first (and currently only) level of the
|
||||
standard given for common tools.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
At this stage, it isn't clear exactly how the Org-outside-Emacs landscape will
|
||||
At this stage, it isn’t clear exactly how the Org-outside-Emacs landscape will
|
||||
evolve, but the swelling interest is very encouraging.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -94,7 +94,7 @@ evolve, but the swelling interest is very encouraging.
|
|||
<h2 id="an-org-parser">An Org parser in Julia<a aria-hidden="true" href="#an-org-parser">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-an-org-parser">
|
||||
<p>
|
||||
Speaking of parsers, I may be somewhat biased but I'm quite happy that a Org
|
||||
Speaking of parsers, I may be somewhat biased but I’m quite happy that a Org
|
||||
parser for <a href="https://julialang.org/">Julia</a> now exists 🎉.
|
||||
</p>
|
||||
|
||||
|
|
@ -104,7 +104,7 @@ parser for <a href="https://julialang.org/">Julia</a> now exists 🎉.
|
|||
|
||||
<p>
|
||||
OrgMode.jl is a parser, but also intended as a general-purpose Org library for
|
||||
Julia. It's only been a week since development started, but it currently
|
||||
Julia. It’s only been a week since development started, but it currently
|
||||
supports most of the <a href="https://orgmode.org/worg/dev/org-syntax.html">Org Syntax</a> draft specification, along with the rendering of
|
||||
a parsed Org <span class='acr'>AST</span> to a <span class='acr'>TTY</span> or back to Org text. A few utility functions are also
|
||||
included, such as <code>filtermap</code> which operates similarly to <code>org-element-map</code>.
|
||||
|
|
@ -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='orgc8750fb' class='code' open>
|
||||
<details id='org3915936' class='code' open>
|
||||
<summary></summary>
|
||||
<div class='gutter'><a href='#orgc8750fb'>#</a>
|
||||
<div class='gutter'><a href='#org3915936'>#</a>
|
||||
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
|
||||
<pre class="example" id="orgc8750fb">
|
||||
<pre class="example" id="org3915936">
|
||||
#+cite_export: FORMAT ...
|
||||
</pre>
|
||||
|
||||
|
|
@ -146,8 +146,8 @@ This should make getting started with citations in Org just a bit easier.
|
|||
<div class="outline-text-2" id="text-nicer-tangle-mode">
|
||||
<p>
|
||||
The standard way of setting a <kbd>:tangle-mode</kbd> has typically been by providing a
|
||||
closure that makes use of Elisp's octal syntax, such as <kbd>(identity #o755)</kbd>. This
|
||||
is unnecessarily verbose, and certainly doesn't feel natural.
|
||||
closure that makes use of Elisp’s octal syntax, such as <kbd>(identity #o755)</kbd>. This
|
||||
is unnecessarily verbose, and certainly doesn’t feel natural.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -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='orgfa29bb3' class='code' open>
|
||||
<details id='org248fb38' class='code' open>
|
||||
<summary></summary>
|
||||
<div class='gutter'><a href='#orgfa29bb3'>#</a>
|
||||
<div class='gutter'><a href='#org248fb38'>#</a>
|
||||
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
|
||||
<pre class="example" id="orgfa29bb3">
|
||||
<pre class="example" id="org248fb38">
|
||||
: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-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">
|
||||
<div id="outline-container-113526722" class="outline-2">
|
||||
<h2 id="113526722">Org element parser cache<a aria-hidden="true" href="#113526722">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-113526722">
|
||||
<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>
|
||||
|
|
@ -206,7 +206,7 @@ correctness guarantees on one or two properties in particular cases.
|
|||
Several org-mode <span class='acr'>API</span><small>s</small> now make use of the cache to dramatically improve speed.
|
||||
Aside from improvements to typically slow operations, this is ideal for
|
||||
situations involving frequent buffer edits.
|
||||
It's no understatement to say that this work is transformative.
|
||||
It’s no understatement to say that this work is transformative.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -224,21 +224,21 @@ to be built on <kbd>org-element</kbd> instead.
|
|||
<div class="outline-text-2" id="text-inline-source-block">
|
||||
<p>
|
||||
I think <a href="https://orgmode.org/manual/Structure-of-Code-Blocks.html">inline source code blocks</a> are an underappreciated feature of Org. I
|
||||
don't think it's helped that they have not been visually treated at all
|
||||
don’t think it’s helped that they have not been visually treated at all
|
||||
differently from plain text. Now though, they have a new dedicated face
|
||||
(<code>org-inline-src-block</code>) <i>and</i> in the same manner as source blocks, based on
|
||||
<code>org-src-fontify-natively</code> can be fontified using the language's major mode.
|
||||
<code>org-src-fontify-natively</code> can be fontified using the language’s major mode.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org2816665">
|
||||
<figure id="orgbac6797">
|
||||
<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>
|
||||
</figure>
|
||||
|
||||
<p>
|
||||
If you aren't familiar with inline source blocks, you're missing out. They are
|
||||
If you aren’t familiar with inline source blocks, you’re missing out. They are
|
||||
very much the inline cousin of source blocks, and so support all your favourite
|
||||
Babel features like code execution and header arguments. This provides a
|
||||
fantastic capacity to inline dynamically computed expressions, and optionally
|
||||
|
|
@ -246,7 +246,7 @@ show the code that produces them.
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="orgcb0073f">
|
||||
<figure id="org039e913">
|
||||
<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>
|
||||
|
|
@ -280,7 +280,7 @@ with Babel:
|
|||
</details>
|
||||
|
||||
<p>
|
||||
In a Jupyter-style (<kbd>.ipynb</kbd>) or throwaway document, we likely don't care about
|
||||
In a Jupyter-style (<kbd>.ipynb</kbd>) or throwaway document, we likely don’t care about
|
||||
the file name at all. With these new capabilities, we can provide a file name
|
||||
dynamically as a default argument!
|
||||
</p>
|
||||
|
|
@ -306,8 +306,8 @@ suitable file name, like so
|
|||
</details>
|
||||
|
||||
<p>
|
||||
Let's also write a function to guess whether the source block produces a plot by
|
||||
checking if there's a plot command on the last line.
|
||||
Let’s also write a function to guess whether the source block produces a plot by
|
||||
checking if there’s a plot command on the last line.
|
||||
</p>
|
||||
|
||||
<details id='functions-as-default,code--3' class='code' open><summary><span class="lang">Emacs Lisp</span></summary>
|
||||
|
|
@ -325,7 +325,7 @@ checking if there's a plot command on the last line.
|
|||
|
||||
<p>
|
||||
Then we can just use these function in place of a static value in the default
|
||||
header arguments variable — that's all it takes.
|
||||
header arguments variable — that’s all it takes.
|
||||
</p>
|
||||
|
||||
<details id='functions-as-default,code--4' class='code' open><summary><span class="lang">Emacs Lisp</span></summary>
|
||||
|
|
@ -358,7 +358,7 @@ This means for most cases we can now get away without any header arguments at al
|
|||
</details>
|
||||
|
||||
<p>
|
||||
It's always lovely to see more ways of reducing boilerplate.
|
||||
It’s always lovely to see more ways of reducing boilerplate.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -381,7 +381,7 @@ accessible text width in the buffer.
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="orgbd6df71">
|
||||
<figure id="orgfb0a353">
|
||||
<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>
|
||||
|
|
@ -392,7 +392,7 @@ This means that a width parameter like <kbd>#+attr_latex: :width 0.7\linewidth</
|
|||
image will displayed as 70% of the buffer text width.
|
||||
This also supports percentage value, like <kbd>#+attr_html: :width 80%</kbd> by dividing
|
||||
the number before the <kbd>%</kbd> by 100 as a floating-point value.
|
||||
As always, if you don't like the way display width is inferred here you can
|
||||
As always, if you don’t like the way display width is inferred here you can
|
||||
override it by putting a <kbd>#+attr_org: :width X</kbd> statement first.
|
||||
</p>
|
||||
|
||||
|
|
@ -445,7 +445,7 @@ the maintainer burden <span class="underline">Bastien</span></li>
|
|||
<li>Fix display error with <kbd>ob-plantuml</kbd> and html export <span class="underline">Su Lin</span></li>
|
||||
<li>More tests! <span class="underline">Ihor Radchenko</span></li>
|
||||
<li>Documentation improvements! <span class="underline">Marco Wahl</span> <span class="underline">Stefan Kangas</span> <span class="underline">Daniel Fleischer</span> <span class="underline">Wiliam
|
||||
Denton</span> <span class="underline">Thomas Dye</span> <span class="underline">Bastien</span> <span class="underline">Bruce D'Arcus</span> <span class="underline">Kyle Meyer</span> <span class="underline">Nicolas Goaziou</span></li>
|
||||
Denton</span> <span class="underline">Thomas Dye</span> <span class="underline">Bastien</span> <span class="underline">Bruce D’Arcus</span> <span class="underline">Kyle Meyer</span> <span class="underline">Nicolas Goaziou</span></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -461,7 +461,7 @@ Denton</span> <span class="underline">Thomas Dye</span> <span class="underline">
|
|||
<li>No more duplicated logbook entries for repeated tasks <span class="underline">Ihor Radchenko</span></li>
|
||||
<li>A headline fontification edge case <span class="underline">Sébastien Miquel</span></li>
|
||||
<li>Refactor code that needed Emacs 28 <span class="underline">Kyle Meyer</span></li>
|
||||
<li>Make sure a terminating emphasis marker can't be used as a beginning emphasis
|
||||
<li>Make sure a terminating emphasis marker can’t be used as a beginning emphasis
|
||||
marker in fontification <span class="underline">Ihor Radchenko</span></li>
|
||||
<li>Allow footnotes at footnote definition start <span class="underline">Nicholas Goaziou</span></li>
|
||||
</ul>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: November 2021
|
||||
#+date: 2021-11-30
|
||||
#+author: TEC
|
||||
|
|
|
|||
|
|
@ -10,8 +10,8 @@
|
|||
|
||||
|
||||
With a 9.5 release highlight post last month, and the month before
|
||||
skipped, it's now /three months/ since the last regular instalment of
|
||||
TMIO. Let's get back up to date on some of the latest happenings with
|
||||
skipped, it’s now /three months/ since the last regular instalment of
|
||||
TMIO. Let’s get back up to date on some of the latest happenings with
|
||||
Org.
|
||||
|
||||
|
||||
|
|
@ -21,8 +21,8 @@ Org as markup
|
|||
Looking at the wider ecosystem, it certainly appears that there is a
|
||||
growing appetite for Org markup outside org-mode. More projects like
|
||||
[Hugo] and [Logseq] seem to be interested in supporting Org markup,
|
||||
and there has been a recent growth in editor extensions like Neovim's
|
||||
[orgmode.nvim] (started in March this year) and Sublime Text's
|
||||
and there has been a recent growth in editor extensions like Neovim’s
|
||||
[orgmode.nvim] (started in March this year) and Sublime Text’s
|
||||
[OrgExtended] (started in June this year).
|
||||
|
||||
Interest in Org as a general-usage markup format can also be seen
|
||||
|
|
@ -31,7 +31,7 @@ Org as markup
|
|||
the Worg document [Org Syntax (draft)]. Other members of the Org
|
||||
mailing list have directed their effort to creating non-elisp parsers
|
||||
for Org, both to help Org tools be created in other languages, and as
|
||||
put in the README for Tom Gillespie's [laundry] parser
|
||||
put in the README for Tom Gillespie’s [laundry] parser
|
||||
The long term goal of this work is to provide a reference
|
||||
that can be used to standardize Org syntax and behavior
|
||||
and to specify various levels of compliance for an
|
||||
|
|
@ -41,13 +41,13 @@ Org as markup
|
|||
document [Org Mode Is One of the Most Reasonable Markup Languages to
|
||||
Use for Text], surprised the mailing list by announcing his
|
||||
independent creation of a multi-leveled standard for Org syntax
|
||||
subsets called "Orgdown" (the name is a blend of "Org-mode" and
|
||||
"markdown", but the standard is only a subset of Org). Each level
|
||||
subsets called “Orgdown” (the name is a blend of “Org-mode” and
|
||||
“markdown”, but the standard is only a subset of Org). Each level
|
||||
defines a compliance score given by a mix of parsing and editing
|
||||
support, with example compliance scores for the first (and currently
|
||||
only) level of the standard given for common tools.
|
||||
|
||||
At this stage, it isn't clear exactly how the Org-outside-Emacs
|
||||
At this stage, it isn’t clear exactly how the Org-outside-Emacs
|
||||
landscape will evolve, but the swelling interest is very encouraging.
|
||||
|
||||
|
||||
|
|
@ -70,13 +70,13 @@ Text] <https://karl-voit.at/2017/09/23/orgmode-as-markup-only/>
|
|||
An Org parser in Julia
|
||||
══════════════════════
|
||||
|
||||
Speaking of parsers, I may be somewhat biased but I'm quite happy that
|
||||
Speaking of parsers, I may be somewhat biased but I’m quite happy that
|
||||
a Org parser for [Julia] now exists 🎉.
|
||||
|
||||
//github.com/tecosaur/OrgMode.jl
|
||||
|
||||
OrgMode.jl is a parser, but also intended as a general-purpose Org
|
||||
library for Julia. It's only been a week since development started,
|
||||
library for Julia. It’s only been a week since development started,
|
||||
but it currently supports most of the [Org Syntax] draft
|
||||
specification, along with the rendering of a parsed Org AST to a TTY
|
||||
or back to Org text. A few utility functions are also included, such
|
||||
|
|
@ -110,9 +110,9 @@ A nicer `:tangle-mode' syntax
|
|||
═════════════════════════════
|
||||
|
||||
The standard way of setting a `:tangle-mode' has typically been by
|
||||
providing a closure that makes use of Elisp's octal syntax, such as
|
||||
providing a closure that makes use of Elisp’s octal syntax, such as
|
||||
`(identity #o755)'. This is unnecessarily verbose, and certainly
|
||||
doesn't feel natural.
|
||||
doesn’t feel natural.
|
||||
|
||||
With the addition of a small mode-interpreting function
|
||||
(`org-babel-interpret-file-mode') It is now possible to specify
|
||||
|
|
@ -159,7 +159,7 @@ Org element parser cache
|
|||
|
||||
Several org-mode APIs now make use of the cache to dramatically
|
||||
improve speed. Aside from improvements to typically slow operations,
|
||||
this is ideal for situations involving frequent buffer edits. It's no
|
||||
this is ideal for situations involving frequent buffer edits. It’s no
|
||||
understatement to say that this work is transformative.
|
||||
|
||||
One potential beneficiary from this work is actually fontification. It
|
||||
|
|
@ -175,15 +175,15 @@ Inline source block fontification
|
|||
═════════════════════════════════
|
||||
|
||||
I think [inline source code blocks] are an underappreciated feature of
|
||||
Org. I don't think it's helped that they have not been visually
|
||||
Org. I don’t think it’s helped that they have not been visually
|
||||
treated at all differently from plain text. Now though, they have a
|
||||
new dedicated face (`org-inline-src-block') /and/ in the same manner
|
||||
as source blocks, based on `org-src-fontify-natively' can be fontified
|
||||
using the language's major mode.
|
||||
using the language’s major mode.
|
||||
|
||||
<file:figures/inline-src-block-fontified-vs-code.png>
|
||||
|
||||
If you aren't familiar with inline source blocks, you're missing
|
||||
If you aren’t familiar with inline source blocks, you’re missing
|
||||
out. They are very much the inline cousin of source blocks, and so
|
||||
support all your favourite Babel features like code execution and
|
||||
header arguments. This provides a fantastic capacity to inline
|
||||
|
|
@ -214,7 +214,7 @@ Functions as default heading arguments
|
|||
│ #+end_src
|
||||
└────
|
||||
|
||||
In a Jupyter-style (`.ipynb') or throwaway document, we likely don't
|
||||
In a Jupyter-style (`.ipynb') or throwaway document, we likely don’t
|
||||
care about the file name at all. With these new capabilities, we can
|
||||
provide a file name dynamically as a default argument!
|
||||
|
||||
|
|
@ -230,8 +230,8 @@ Functions as default heading arguments
|
|||
│ ".svg"))
|
||||
└────
|
||||
|
||||
Let's also write a function to guess whether the source block produces
|
||||
a plot by checking if there's a plot command on the last line.
|
||||
Let’s also write a function to guess whether the source block produces
|
||||
a plot by checking if there’s a plot command on the last line.
|
||||
|
||||
┌────
|
||||
│ (defun my/org-src-guess-results-type ()
|
||||
|
|
@ -241,7 +241,7 @@ Functions as default heading arguments
|
|||
└────
|
||||
|
||||
Then we can just use these function in place of a static value in the
|
||||
default header arguments variable — that's all it takes.
|
||||
default header arguments variable — that’s all it takes.
|
||||
|
||||
┌────
|
||||
│ (setq org-babel-default-header-args:R
|
||||
|
|
@ -259,7 +259,7 @@ Functions as default heading arguments
|
|||
│ #+end_src
|
||||
└────
|
||||
|
||||
It's always lovely to see more ways of reducing boilerplate.
|
||||
It’s always lovely to see more ways of reducing boilerplate.
|
||||
|
||||
|
||||
Proportional image widths
|
||||
|
|
@ -284,7 +284,7 @@ Proportional image widths
|
|||
0.7\linewidth' the image will displayed as 70% of the buffer text
|
||||
width. This also supports percentage value, like `#+attr_html: :width
|
||||
80%' by dividing the number before the `%' by 100 as a floating-point
|
||||
value. As always, if you don't like the way display width is inferred
|
||||
value. As always, if you don’t like the way display width is inferred
|
||||
here you can override it by putting a `#+attr_org: :width X' statement
|
||||
first.
|
||||
|
||||
|
|
@ -338,7 +338,7 @@ Other improvements
|
|||
⁃ Fix display error with `ob-plantuml' and html export _Su Lin_
|
||||
⁃ More tests! _Ihor Radchenko_
|
||||
⁃ Documentation improvements! _Marco Wahl_ _Stefan Kangas_ _Daniel
|
||||
Fleischer_ _Wiliam Denton_ _Thomas Dye_ _Bastien_ _Bruce D'Arcus_
|
||||
Fleischer_ _Wiliam Denton_ _Thomas Dye_ _Bastien_ _Bruce D’Arcus_
|
||||
_Kyle Meyer_ _Nicolas Goaziou_
|
||||
|
||||
|
||||
|
|
@ -356,7 +356,7 @@ Bugfixes
|
|||
Radchenko_
|
||||
⁃ A headline fontification edge case _Sébastien Miquel_
|
||||
⁃ Refactor code that needed Emacs 28 _Kyle Meyer_
|
||||
⁃ Make sure a terminating emphasis marker can't be used as a beginning
|
||||
⁃ Make sure a terminating emphasis marker can’t be used as a beginning
|
||||
emphasis marker in fontification _Ihor Radchenko_
|
||||
⁃ Allow footnotes at footnote definition start _Nicholas Goaziou_
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>December 2021</title>
|
||||
|
|
@ -43,8 +43,8 @@
|
|||
<p class="subtitle" role="doc-subtitle">Looking back on my first year of blogging</p>
|
||||
</header><p>
|
||||
Just over eight months ago, I kicked off <i>This Month in Org</i> with an emphatic
|
||||
announcement of the blog's in the form of a <a href="2021-04-26-Welcome.html">Welcome</a> post. If you haven't
|
||||
guessed, this is the first "blog post" I've ever written. In that <i>welcome</i> post,
|
||||
announcement of the blog’s in the form of a <a href="2021-04-26-Welcome.html">Welcome</a> post. If you haven’t
|
||||
guessed, this is the first “blog post” I’ve ever written. In that <i>welcome</i> post,
|
||||
I gave my motivation for starting the blog — essentially to bridge a perceived
|
||||
gap in information sources between a subscription to the Org project mailing
|
||||
list, and nothing.
|
||||
|
|
@ -62,7 +62,7 @@ mention what <i>I</i> want to accomplish with it. By starting <i>TMiO</i> I hope
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
Since then, I've effused about Org to the tune of around ten thousand words. We
|
||||
Since then, I’ve effused about Org to the tune of around ten thousand words. We
|
||||
started off with a fairly dry recount recent changes, which (after initial
|
||||
feedback) has shifted slightly to try to give more context on the improvements
|
||||
and how they may be used. In June I even went as far as to make the majority of
|
||||
|
|
@ -71,7 +71,7 @@ This change has been made to:
|
|||
</p>
|
||||
<ul class="org-ul">
|
||||
<li>Try to make the blog posts a little more interesting, and less tedious.</li>
|
||||
<li>Potentially introduce readers to nice features of Org they weren't aware of before.</li>
|
||||
<li>Potentially introduce readers to nice features of Org they weren’t aware of before.</li>
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
|
|
@ -80,9 +80,9 @@ has this blog been in achieving its goals?</i>
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Let's start off by looking at engagement. There is no tracking on this site, and
|
||||
I'm not even counting page views. We could read into Reddit upvotes (which
|
||||
usually hover around 100-ish per post), but with no strong trend I'm wary of
|
||||
Let’s start off by looking at engagement. There is no tracking on this site, and
|
||||
I’m not even counting page views. We could read into Reddit upvotes (which
|
||||
usually hover around 100-ish per post), but with no strong trend I’m wary of
|
||||
reading too much into those numbers. What about engendering an interest in
|
||||
contributing? This is even harder to consider. It is similarly difficult to
|
||||
judge whether this blog might be helping (even if only a bit) foster a stronger
|
||||
|
|
@ -96,27 +96,27 @@ I make to the style of posts, if any?</i>
|
|||
|
||||
<p>
|
||||
Hmmm, this is a prickly one too. Both of these questions suffer from the same
|
||||
problem — <i>I</i> can't answer them. Simply put, I need to hear from <i>you</i>. Whether it
|
||||
problem — <i>I</i> can’t answer them. Simply put, I need to hear from <i>you</i>. Whether it
|
||||
be in the Reddit comments section, or by Email (<kbd>tec@</kbd> this domain), to direct
|
||||
2022's posts I am <i>very</i> interested in hearing your thoughts on:
|
||||
2022’s posts I am <i>very</i> interested in hearing your thoughts on:
|
||||
</p>
|
||||
<ul class="org-ul">
|
||||
<li>How engaging you've found this blog? (the content, the style of writing, etc.)</li>
|
||||
<li>How engaging you’ve found this blog? (the content, the style of writing, etc.)</li>
|
||||
<li>Whether this blog has influenced your feelings on the Org project and/or community?</li>
|
||||
<li>Whether this blog has affected your thoughts on contributing to Org?</li>
|
||||
<li>What you think this blog has done well/badly over the past year?</li>
|
||||
<li>If there's anything you'd be interested in this blog doing differently in 2022?</li>
|
||||
<li>If there’s anything you’d be interested in this blog doing differently in 2022?</li>
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
That's all for now! Thank you for reading, and have a great new year 🙂
|
||||
That’s all for now! Thank you for reading, and have a great new year 🙂
|
||||
</p>
|
||||
<div id="footnotes">
|
||||
<h2 class="footnotes">Footnotes: </h2>
|
||||
<div id="text-footnotes">
|
||||
|
||||
<div class="footdef"><sup><a id="fn.1" class="footnum" href="#fnr.1" role="doc-backlink">1</a></sup> <div class="footpara" role="doc-footnote"><p class="footpara">
|
||||
Both the org-mode codebase, and also the ecosystem that's sprung up
|
||||
Both the org-mode codebase, and also the ecosystem that’s sprung up
|
||||
around it
|
||||
</p></div></div>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: December 2021
|
||||
#+date: 2021-12-31
|
||||
#+author: TEC
|
||||
|
|
|
|||
|
|
@ -10,8 +10,8 @@
|
|||
|
||||
|
||||
Just over eight months ago, I kicked off /This Month in Org/ with an
|
||||
emphatic announcement of the blog's in the form of a [Welcome] post. If
|
||||
you haven't guessed, this is the first "blog post" I've ever written. In
|
||||
emphatic announcement of the blog’s in the form of a [Welcome] post. If
|
||||
you haven’t guessed, this is the first “blog post” I’ve ever written. In
|
||||
that /welcome/ post, I gave my motivation for starting the blog —
|
||||
essentially to bridge a perceived gap in information sources between a
|
||||
subscription to the Org project mailing list, and nothing.
|
||||
|
|
@ -25,7 +25,7 @@ neglected to mention what /I/ want to accomplish with it. By starting
|
|||
⁃ Foster a stronger sense of an Org[1] community, outside the mailing
|
||||
list.
|
||||
|
||||
Since then, I've effused about Org to the tune of around ten thousand
|
||||
Since then, I’ve effused about Org to the tune of around ten thousand
|
||||
words. We started off with a fairly dry recount recent changes, which
|
||||
(after initial feedback) has shifted slightly to try to give more
|
||||
context on the improvements and how they may be used. In June I even
|
||||
|
|
@ -33,16 +33,16 @@ went as far as to make the majority of the post about pre-existing
|
|||
features (writing Org for LaTeX). This change has been made to:
|
||||
⁃ Try to make the blog posts a little more interesting, and less
|
||||
tedious.
|
||||
⁃ Potentially introduce readers to nice features of Org they weren't
|
||||
⁃ Potentially introduce readers to nice features of Org they weren’t
|
||||
aware of before.
|
||||
|
||||
We have now arrived at the first crucial question of this post: /How
|
||||
effective has this blog been in achieving its goals?/
|
||||
|
||||
Let's start off by looking at engagement. There is no tracking on this
|
||||
site, and I'm not even counting page views. We could read into Reddit
|
||||
Let’s start off by looking at engagement. There is no tracking on this
|
||||
site, and I’m not even counting page views. We could read into Reddit
|
||||
upvotes (which usually hover around 100-ish per post), but with no
|
||||
strong trend I'm wary of reading too much into those numbers. What about
|
||||
strong trend I’m wary of reading too much into those numbers. What about
|
||||
engendering an interest in contributing? This is even harder to
|
||||
consider. It is similarly difficult to judge whether this blog might be
|
||||
helping (even if only a bit) foster a stronger sense of community.
|
||||
|
|
@ -51,20 +51,20 @@ Ok, how about the second crucial question: /Moving forwards, what
|
|||
changes should I make to the style of posts, if any?/
|
||||
|
||||
Hmmm, this is a prickly one too. Both of these questions suffer from the
|
||||
same problem — /I/ can't answer them. Simply put, I need to hear from
|
||||
same problem — /I/ can’t answer them. Simply put, I need to hear from
|
||||
/you/. Whether it be in the Reddit comments section, or by Email (`tec@'
|
||||
this domain), to direct 2022's posts I am /very/ interested in hearing
|
||||
this domain), to direct 2022’s posts I am /very/ interested in hearing
|
||||
your thoughts on:
|
||||
⁃ How engaging you've found this blog? (the content, the style of
|
||||
⁃ How engaging you’ve found this blog? (the content, the style of
|
||||
writing, etc.)
|
||||
⁃ Whether this blog has influenced your feelings on the Org project
|
||||
and/or community?
|
||||
⁃ Whether this blog has affected your thoughts on contributing to Org?
|
||||
⁃ What you think this blog has done well/badly over the past year?
|
||||
⁃ If there's anything you'd be interested in this blog doing differently
|
||||
⁃ If there’s anything you’d be interested in this blog doing differently
|
||||
in 2022?
|
||||
|
||||
That's all for now! Thank you for reading, and have a great new year 🙂
|
||||
That’s all for now! Thank you for reading, and have a great new year 🙂
|
||||
|
||||
|
||||
[Welcome] <file:2021-04-26-Welcome.org>
|
||||
|
|
@ -74,5 +74,5 @@ That's all for now! Thank you for reading, and have a great new year 🙂
|
|||
Footnotes
|
||||
─────────
|
||||
|
||||
[1] Both the org-mode codebase, and also the ecosystem that's sprung
|
||||
[1] Both the org-mode codebase, and also the ecosystem that’s sprung
|
||||
up around it
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>January 2022</title>
|
||||
|
|
@ -42,7 +42,7 @@
|
|||
<h1 class="title">January 2022</h1>
|
||||
<p class="subtitle" role="doc-subtitle">Caching</p>
|
||||
</header><p>
|
||||
There are less "obvious user-facing changes" this month, but a lot of good work
|
||||
There are less “obvious user-facing changes” this month, but a lot of good work
|
||||
has been happening 🙂.
|
||||
</p>
|
||||
<div id="outline-container-cache-continues-make" class="outline-2">
|
||||
|
|
@ -54,19 +54,19 @@ existed for a while now, but it used to be too buggy to be useful.
|
|||
</p>
|
||||
|
||||
<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#org6c447c2">November</a>, however Ihor has continued to make strides with the
|
||||
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#orgff73293">November</a>, however Ihor has continued to make strides with the
|
||||
cache.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Getting the cache right is tough though, and so while the situation is much
|
||||
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:
|
||||
only take one thing away from the post, I’d like it to be this:
|
||||
</p>
|
||||
|
||||
<div class="info" id="orgfc1b754">
|
||||
<div class="info" id="orgb17f9b2">
|
||||
<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='org70e1330' class='code' open>
|
||||
<details id='org8ad0fdd' class='code' open>
|
||||
<summary></summary>
|
||||
<div class='gutter'><a href='#org70e1330'>#</a>
|
||||
<div class='gutter'><a href='#org8ad0fdd'>#</a>
|
||||
<button title='Copy to clipboard' onclick='copyPreToClipbord(this)'>⎘</button></div>
|
||||
<pre class="example" id="org70e1330">
|
||||
<pre class="example" id="org8ad0fdd">
|
||||
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
|
||||
|
|
@ -102,17 +102,17 @@ The buffer is: config.org
|
|||
|
||||
<p>
|
||||
A good way to start is by copying this to your clipboard and then trying <kbd>M-x
|
||||
org-submit-bug-report</kbd>. Regardless of whether you're using an Emacs mail client,
|
||||
org-submit-bug-report</kbd>. Regardless of whether you’re using an Emacs mail client,
|
||||
this will collect all the important information (org-mode version, etc.) and
|
||||
populate a buffer with it. Add the warning text, and that will be a great help!
|
||||
After all, it's quite hard to fix bugs we don't know about 😆.
|
||||
After all, it’s quite hard to fix bugs we don’t know about 😆.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<p>
|
||||
As of October 2021, "bulk" heading promotion/demotion operations are now faster
|
||||
As of October 2021, “bulk” heading promotion/demotion operations are now faster
|
||||
thanks to the cache, and there have now been further improvements relating to
|
||||
headings. It used to be the case that every time heading properties changed the
|
||||
entire heading (and contents) were re-parsed. Now, cache heuristics prevent the
|
||||
|
|
@ -151,7 +151,7 @@ Ever linked to an online image like
|
|||
<kbd>https://orgmode.org/resources/img/org-mode-unicorn.svg</kbd> in an Org document, seen
|
||||
it look nice in the <span class='acr'>HTML</span> export and then be disappointed to just see a link in
|
||||
LaTeX? Well I have. Thankfully this is no longer the case though, thanks to a
|
||||
helper function <code>org-export-link-localise</code> that's just been added to <kbd>ox.el</kbd>.
|
||||
helper function <code>org-export-link-localise</code> that’s just been added to <kbd>ox.el</kbd>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -161,7 +161,7 @@ to provide support for not just <span class='acr'>HTTPS</span> links but also tr
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org288b81f">
|
||||
<figure id="org75c72b5">
|
||||
<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>
|
||||
|
|
@ -169,7 +169,7 @@ to provide support for not just <span class='acr'>HTTPS</span> links but also tr
|
|||
|
||||
<p>
|
||||
While this is currently only implemented for <kbd>ox-latex</kbd>, this can be applied
|
||||
generally, and so there's a good chance you'll hear more about this in the future.
|
||||
generally, and so there’s a good chance you’ll hear more about this in the future.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: January 2022
|
||||
#+date: 2022-01-31
|
||||
#+author: TEC
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@
|
|||
2022-01-31
|
||||
|
||||
|
||||
There are less "obvious user-facing changes" this month, but a lot of
|
||||
There are less “obvious user-facing changes” this month, but a lot of
|
||||
good work has been happening 🙂.
|
||||
|
||||
|
||||
|
|
@ -20,14 +20,14 @@ The cache continues to make strides
|
|||
cache has existed for a while now, but it used to be too buggy to be
|
||||
useful.
|
||||
|
||||
This is no longer the case! We're finally confident enough to flip
|
||||
`org-element-use-cache''s default from `nil' to `t'. I mentioned some
|
||||
This is no longer the case! We’re finally confident enough to flip
|
||||
`org-element-use-cache'’s default from `nil' to `t'. I mentioned some
|
||||
of the improvements in [November], however Ihor has continued to make
|
||||
strides with the cache.
|
||||
|
||||
Getting the cache right is tough though, and so while the situation is
|
||||
much 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
|
||||
down. If you only take one thing away from the post, I’d like it to be
|
||||
this:
|
||||
|
||||
The cache is actively being developed now, for the first time in
|
||||
|
|
@ -51,13 +51,13 @@ The cache continues to make strides
|
|||
└────
|
||||
|
||||
A good way to start is by copying this to your clipboard and then
|
||||
trying `M-x org-submit-bug-report'. Regardless of whether you're using
|
||||
trying `M-x org-submit-bug-report'. Regardless of whether you’re using
|
||||
an Emacs mail client, this will collect all the important information
|
||||
(org-mode version, etc.) and populate a buffer with it. Add the
|
||||
warning text, and that will be a great help! After all, it's quite
|
||||
hard to fix bugs we don't know about 😆.
|
||||
warning text, and that will be a great help! After all, it’s quite
|
||||
hard to fix bugs we don’t know about 😆.
|
||||
|
||||
As of October 2021, "bulk" heading promotion/demotion operations are
|
||||
As of October 2021, “bulk” heading promotion/demotion operations are
|
||||
now faster thanks to the cache, and there have now been further
|
||||
improvements relating to headings. It used to be the case that every
|
||||
time heading properties changed the entire heading (and contents) were
|
||||
|
|
@ -99,7 +99,7 @@ Exporting documents with remote resources
|
|||
document, seen it look nice in the HTML export and then be
|
||||
disappointed to just see a link in LaTeX? Well I have. Thankfully this
|
||||
is no longer the case though, thanks to a helper function
|
||||
`org-export-link-localise' that's just been added to `ox.el'.
|
||||
`org-export-link-localise' that’s just been added to `ox.el'.
|
||||
|
||||
Using `org-persist.el' this acquires a local copy of the remote
|
||||
resource and substitutes it in for the remote link. This is currently
|
||||
|
|
@ -109,7 +109,7 @@ Exporting documents with remote resources
|
|||
<file:figures/ox-latex-image-link-localisation-demo.png>
|
||||
|
||||
While this is currently only implemented for `ox-latex', this can be
|
||||
applied generally, and so there's a good chance you'll hear more about
|
||||
applied generally, and so there’s a good chance you’ll hear more about
|
||||
this in the future.
|
||||
|
||||
There are also thoughts of moving this to the links file (`ol.el')
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>February 2022</title>
|
||||
|
|
@ -53,14 +53,14 @@ experience outside Emacs.
|
|||
</p>
|
||||
|
||||
<p>
|
||||
"But I use Emacs, I don't care" you may say. In that case, I'd like to point out
|
||||
“But I use Emacs, I don’t care” you may say. In that case, I’d like to point out
|
||||
that wider spread and better Org support enriches the Org ecosystem as a whole.
|
||||
It makes the format more approachable, and <i>useful</i> for other people. This is good
|
||||
for everybody.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Without any further ado, here's the guest post kindly written by Kristijan.
|
||||
Without any further ado, here’s the guest post kindly written by Kristijan.
|
||||
Enjoy!
|
||||
</p>
|
||||
|
||||
|
|
@ -68,12 +68,12 @@ Enjoy!
|
|||
|
||||
<p>
|
||||
Like every beginner Vim user, at some point I ran into a usual editor war post:
|
||||
Vim vs Emacs. At that time, I didn't have an idea what "Emacs" was.
|
||||
Vim vs Emacs. At that time, I didn’t have an idea what “Emacs” was.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
A simple Google search yielded something that seemed just like a very simple
|
||||
editor with strange, but more familiar shortcuts. I didn't bother too much to
|
||||
editor with strange, but more familiar shortcuts. I didn’t bother too much to
|
||||
figure out what it is, because I was already pulled in fairly deep into Vim and
|
||||
its philosophy.
|
||||
</p>
|
||||
|
|
@ -93,19 +93,19 @@ natural choice.
|
|||
|
||||
<p>
|
||||
That worked very well for a period, until the need for writing quick notes
|
||||
arise. Vimwiki didn't have anything that would allow that. I could of course
|
||||
arise. Vimwiki didn’t have anything that would allow that. I could of course
|
||||
have a mapping that opens a specific file where I can add notes, but that just
|
||||
never felt right in my mind. I would keep a bunch of things in the same place,
|
||||
and then later I needed to spend some time organizing them.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
At that point, I wasn't sure how to achieve what I want. I did a brief look at
|
||||
<a href="https://orgmode.org/">Emacs OrgMode</a> to see what's all the fuss about, but to me, it seemed just like a
|
||||
At that point, I wasn’t sure how to achieve what I want. I did a brief look at
|
||||
<a href="https://orgmode.org/">Emacs OrgMode</a> to see what’s all the fuss about, but to me, it seemed just like a
|
||||
different version of Markdown. You put some unordered lists as your notes, and
|
||||
that's it. I never spent more time trying to see all the neat features. I even
|
||||
that’s it. I never spent more time trying to see all the neat features. I even
|
||||
tried creating some of my custom note taking tools, but I never managed to
|
||||
finish them because I didn't have a clear idea of how to solve my problems.
|
||||
finish them because I didn’t have a clear idea of how to solve my problems.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -114,24 +114,24 @@ finish them because I didn't have a clear idea of how to solve my problems.
|
|||
<div class="outline-text-2" id="text-first-encounter-with">
|
||||
<p>
|
||||
One weekend, I was browsing through Vim subreddit, as I usually do at least once
|
||||
a day. There was a post about an "Orgmode like task logging" plugin called
|
||||
<a href="https://github.com/dhruvasagar/vim-dotoo">vim-dotoo</a>. I opened it up, and I didn't see much at that point. I wasn't too
|
||||
a day. There was a post about an “Orgmode like task logging” plugin called
|
||||
<a href="https://github.com/dhruvasagar/vim-dotoo">vim-dotoo</a>. I opened it up, and I didn’t see much at that point. I wasn’t too
|
||||
excited. I went through readme, and noticed that author (<a href="https://github.com/dhruvasagar">dhruvasagar</a>) put a
|
||||
fairly big emphasis on the "Agenda view". I had no idea what "Agenda view" is.
|
||||
fairly big emphasis on the “Agenda view”. I had no idea what “Agenda view” is.
|
||||
Thankfully, the author also made a <a href="https://www.youtube.com/watch?v=nsv33iOnH34">screencast</a>, which is rather long (1.5h), but
|
||||
I had some time, so I went through it.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
At that point, I was first met with "Capturing" and "Refiling". <b>My mind was
|
||||
At that point, I was first met with “Capturing” and “Refiling”. <b>My mind was
|
||||
blown!</b> What a simple, yet extremely powerful idea! How had that never crossed my
|
||||
mind? From that point on, this plugin had my full attention.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
I'm always emphasizing that <a href="https://github.com/dhruvasagar">dhruvasagar</a> and his <a href="https://github.com/dhruvasagar/vim-dotoo">vim-dotoo</a> plugin are most
|
||||
I’m always emphasizing that <a href="https://github.com/dhruvasagar">dhruvasagar</a> and his <a href="https://github.com/dhruvasagar/vim-dotoo">vim-dotoo</a> plugin are most
|
||||
deserving for having inspired <a href="https://github.com/nvim-orgmode/orgmode">https://github.com/nvim-orgmode/orgmode</a>, and I
|
||||
can't thank him enough for that.
|
||||
can’t thank him enough for that.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -144,7 +144,7 @@ was a breath of fresh air. Alongside that, I started getting more interest in
|
|||
the original Emacs Orgmode. I started noticing the differences, and some of the
|
||||
missing features that were now looking quite attractive. I made <a href="https://github.com/dhruvasagar/vim-dotoo/pulls?q=is%3Apr+sort%3Aupdated-desc+author%3Akristijanhusak+is%3Aclosed">few
|
||||
contributions</a> to vim-dotoo. As time passed, and my notes started to grow, things
|
||||
began being slow. I did some profiling, and figured out that it's just a usual
|
||||
began being slow. I did some profiling, and figured out that it’s just a usual
|
||||
Vim problem, Vimscript performance. It was just too slow for certain things that
|
||||
Orgmode provides, and it would hardly get any better as more things are added.
|
||||
</p>
|
||||
|
|
@ -155,7 +155,7 @@ was still being developed. I was using Neovim from version 0.3, and was
|
|||
carefully following the progress on it. Lua was introduced as a first class
|
||||
citizen. A Bunch of new plugins arise from it. All the benchmarks showed that
|
||||
Lua outperforms Vimscript in almost everything. Besides the performance, Lua is
|
||||
a "normal" programming language, which means that support for it is much better.
|
||||
a “normal” programming language, which means that support for it is much better.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -183,9 +183,9 @@ Besides parsing, I had a few more challenges to overcome:
|
|||
<h3 id="understanding-orgmode-syntax">Understanding the OrgMode syntax and all the functionality<a aria-hidden="true" href="#understanding-orgmode-syntax">#</a> </h3>
|
||||
<div class="outline-text-3" id="text-understanding-orgmode-syntax">
|
||||
<p>
|
||||
This is still the biggest challenge. I didn't have any idea how big and robust
|
||||
OrgMode is. If I would know it at that time, I wouldn't even jump on this train.
|
||||
It's really hard to grasp all of it. Considering I've only used it for around 8
|
||||
This is still the biggest challenge. I didn’t have any idea how big and robust
|
||||
OrgMode is. If I would know it at that time, I wouldn’t even jump on this train.
|
||||
It’s really hard to grasp all of it. Considering I’ve only used it for around 8
|
||||
months, I think I made some good progress on learning it.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -222,7 +222,7 @@ From my experience, dates are challenging in all areas of programming,
|
|||
so this is not so surprising. There are some Lua plugins for dates, but
|
||||
those seemed a bit too basic for my use case, and I wanted to keep
|
||||
external plugins to the minimum. I went with a custom solution that uses
|
||||
Lua's native dates, which has certain limitations, but works out for
|
||||
Lua’s native dates, which has certain limitations, but works out for
|
||||
most of the things.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -231,15 +231,15 @@ most of the things.
|
|||
<h3 id="highlighting-mostly-agenda">Highlighting, mostly in Agenda view<a aria-hidden="true" href="#highlighting-mostly-agenda">#</a> </h3>
|
||||
<div class="outline-text-3" id="text-highlighting-mostly-agenda">
|
||||
<p>
|
||||
Vim's syntax engine is fairly old, but still very much used, especially
|
||||
Vim’s syntax engine is fairly old, but still very much used, especially
|
||||
in the Vim community. Implementation of tree-sitter slightly improved
|
||||
this experience in Neovim, because "Highlight matches" are found via
|
||||
this experience in Neovim, because “Highlight matches” are found via
|
||||
tree-sitter, instead of a bunch of regexes.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
This helped me out later for the Org file itself, but agenda view is
|
||||
still something that's built as a custom view. Old Syntax highlight engine
|
||||
still something that’s built as a custom view. Old Syntax highlight engine
|
||||
would be really hard to add, because the content is too dynamic. I went
|
||||
with the Neovim highlight <span class='acr'>API</span> that allows Highlighting things by their
|
||||
exact position in the buffer. Tree-sitter implementation does something
|
||||
|
|
@ -258,7 +258,7 @@ same as in Emacs.
|
|||
</p>
|
||||
|
||||
<p>
|
||||
For example, Here's a comparison of few options between Emacs and
|
||||
For example, Here’s a comparison of few options between Emacs and
|
||||
Neovim:
|
||||
</p>
|
||||
|
||||
|
|
@ -335,7 +335,7 @@ and people started testing it and reporting bugs.
|
|||
</p>
|
||||
|
||||
<p>
|
||||
One of the common questions was: <i>"Any plans to introduce tree-sitter parser?"</i>.
|
||||
One of the common questions was: <i>“Any plans to introduce tree-sitter parser?”</i>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -347,25 +347,25 @@ had.
|
|||
|
||||
<p>
|
||||
One day, Emilia (<a href="https://github.com/milisims">milisims</a>) contacted me via email to ask me if I would be
|
||||
willing to try the tree-sitter parser she's been working on for some time. I
|
||||
willing to try the tree-sitter parser she’s been working on for some time. I
|
||||
gladly accepted. She gave me access to the repository, and I started tinkering
|
||||
with it in a separate branch. No one was aware at that point that tree-sitter
|
||||
support would happen some time soon.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
After some time, I set up a "beta" branch called "tree-sitter" and <a href="https://www.reddit.com/r/neovim/comments/ph2xqc/orgmodenvim_treesitter_support/">announced it
|
||||
After some time, I set up a “beta” branch called “tree-sitter” and <a href="https://www.reddit.com/r/neovim/comments/ph2xqc/orgmodenvim_treesitter_support/">announced it
|
||||
for testing</a>. Once the reported bugs slowed to a trickle, I merged it into the
|
||||
"master" branch.
|
||||
“master” branch.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
I believe that tree-sitter grammar for Org could help out other editors to
|
||||
implement their version of Orgmode plugin, but I don't think it would ever be
|
||||
implement their version of Orgmode plugin, but I don’t think it would ever be
|
||||
helpful for Emacs. Emacs parser is the one and only that has it all implemented.
|
||||
Also, as much as tree-sitter is powerful, its main purpose is to parse
|
||||
programming languages, which mostly has "static" patterns to match. Orgmode is
|
||||
by its nature dynamic, which causes a variety of issues for a parser that's not
|
||||
programming languages, which mostly has “static” patterns to match. Orgmode is
|
||||
by its nature dynamic, which causes a variety of issues for a parser that’s not
|
||||
meant for that kind of usage.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -375,13 +375,13 @@ meant for that kind of usage.
|
|||
<div class="outline-text-2" id="text-limitations">
|
||||
<p>
|
||||
(Neo)Vim is a great editor, but it still cannot compare to Emacs in certain
|
||||
things. Manipulating the "View" part of the editor is tricky or impossible for
|
||||
things. Manipulating the “View” part of the editor is tricky or impossible for
|
||||
certain things.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
I even <a href="https://github.com/nvim-orgmode/orgmode/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Aneovim-dependency">made a label</a> for reported issues where Neovim support for certain things
|
||||
is a blocker. I'm hoping that at least some of these will be available in future
|
||||
is a blocker. I’m hoping that at least some of these will be available in future
|
||||
Neovim releases.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -396,9 +396,9 @@ not exist as a built/-in feature in the Emacs Orgmode: <a href="https://github.c
|
|||
</p>
|
||||
|
||||
<p>
|
||||
This allows getting a "desktop notification" for tasks that are within
|
||||
This allows getting a “desktop notification” for tasks that are within
|
||||
the specified threshold for schedule/deadline time. It requires some
|
||||
configuration to set up a cron job, but it's been working great for me
|
||||
configuration to set up a cron job, but it’s been working great for me
|
||||
for several months now.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -407,16 +407,16 @@ for several months now.
|
|||
<h2 id="plans">Plans<a aria-hidden="true" href="#plans">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-plans">
|
||||
<p>
|
||||
The current state of the project is very usable for me. I'm not lacking any of
|
||||
the major features, mostly because I'm not used to using them. Nevertheless,
|
||||
there are plans to add more things, and I'm getting a lot of help from the
|
||||
The current state of the project is very usable for me. I’m not lacking any of
|
||||
the major features, mostly because I’m not used to using them. Nevertheless,
|
||||
there are plans to add more things, and I’m getting a lot of help from the
|
||||
community. I want to specifically mention <a href="https://github.com/levouh">levouh</a> and <a href="https://github.com/lukas-reineke">lukas-reineke</a>, since they
|
||||
added a lot of value to the project, and I want to thank them and everyone else
|
||||
who contributed. Their help is much appreciated.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
There are few high priority tasks that I'm hoping to flush out first:
|
||||
There are few high priority tasks that I’m hoping to flush out first:
|
||||
</p>
|
||||
|
||||
<ul class="org-ul">
|
||||
|
|
@ -445,14 +445,14 @@ programming)</li>
|
|||
<h2 id="closing-thoughts">Closing thoughts<a aria-hidden="true" href="#closing-thoughts">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-closing-thoughts">
|
||||
<p>
|
||||
When I started working on <a href="https://github.com/nvim-orgmode/orgmode">nvim-orgmode</a>, I didn't have a clue what I'm jumping
|
||||
into. Every day I learn about more and more Orgmode features that I wasn't even
|
||||
When I started working on <a href="https://github.com/nvim-orgmode/orgmode">nvim-orgmode</a>, I didn’t have a clue what I’m jumping
|
||||
into. Every day I learn about more and more Orgmode features that I wasn’t even
|
||||
aware existed.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
I'm certain that this project will never manage to clone the Orgmode
|
||||
functionality completely, but I'm hoping it will get close enough so everyone
|
||||
I’m certain that this project will never manage to clone the Orgmode
|
||||
functionality completely, but I’m hoping it will get close enough so everyone
|
||||
from Neovim community and Emacsers trying out Neovim will be able to use it for
|
||||
their needs.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: February 2022
|
||||
#+date: 2022-02-30
|
||||
#+author: Kristijan Husak
|
||||
|
|
|
|||
|
|
@ -15,22 +15,22 @@ efforts to provide a good experience outside Emacs.
|
|||
|
||||
//github.com/nvim-orgmode/orgmode
|
||||
|
||||
"But I use Emacs, I don't care" you may say. In that case, I'd like to
|
||||
“But I use Emacs, I don’t care” you may say. In that case, I’d like to
|
||||
point out that wider spread and better Org support enriches the Org
|
||||
ecosystem as a whole. It makes the format more approachable, and
|
||||
/useful/ for other people. This is good for everybody.
|
||||
|
||||
Without any further ado, here's the guest post kindly written by
|
||||
Without any further ado, here’s the guest post kindly written by
|
||||
Kristijan. Enjoy!
|
||||
|
||||
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
|
||||
|
||||
Like every beginner Vim user, at some point I ran into a usual editor
|
||||
war post: Vim vs Emacs. At that time, I didn't have an idea what "Emacs"
|
||||
war post: Vim vs Emacs. At that time, I didn’t have an idea what “Emacs”
|
||||
was.
|
||||
|
||||
A simple Google search yielded something that seemed just like a very
|
||||
simple editor with strange, but more familiar shortcuts. I didn't bother
|
||||
simple editor with strange, but more familiar shortcuts. I didn’t bother
|
||||
too much to figure out what it is, because I was already pulled in
|
||||
fairly deep into Vim and its philosophy.
|
||||
|
||||
|
|
@ -46,19 +46,19 @@ Note taking in (Neo)Vim
|
|||
[vimwiki] was the natural choice.
|
||||
|
||||
That worked very well for a period, until the need for writing quick
|
||||
notes arise. Vimwiki didn't have anything that would allow that. I
|
||||
notes arise. Vimwiki didn’t have anything that would allow that. I
|
||||
could of course have a mapping that opens a specific file where I can
|
||||
add notes, but that just never felt right in my mind. I would keep a
|
||||
bunch of things in the same place, and then later I needed to spend
|
||||
some time organizing them.
|
||||
|
||||
At that point, I wasn't sure how to achieve what I want. I did a brief
|
||||
look at [Emacs OrgMode] to see what's all the fuss about, but to me,
|
||||
At that point, I wasn’t sure how to achieve what I want. I did a brief
|
||||
look at [Emacs OrgMode] to see what’s all the fuss about, but to me,
|
||||
it seemed just like a different version of Markdown. You put some
|
||||
unordered lists as your notes, and that's it. I never spent more time
|
||||
unordered lists as your notes, and that’s it. I never spent more time
|
||||
trying to see all the neat features. I even tried creating some of my
|
||||
custom note taking tools, but I never managed to finish them because I
|
||||
didn't have a clear idea of how to solve my problems.
|
||||
didn’t have a clear idea of how to solve my problems.
|
||||
|
||||
|
||||
[vimwiki] <https://github.com/vimwiki/vimwiki>
|
||||
|
|
@ -70,22 +70,22 @@ First encounter with Orgmode like tool: vim-dotoo
|
|||
═════════════════════════════════════════════════
|
||||
|
||||
One weekend, I was browsing through Vim subreddit, as I usually do at
|
||||
least once a day. There was a post about an "Orgmode like task
|
||||
logging" plugin called [vim-dotoo]. I opened it up, and I didn't see
|
||||
much at that point. I wasn't too excited. I went through readme, and
|
||||
least once a day. There was a post about an “Orgmode like task
|
||||
logging” plugin called [vim-dotoo]. I opened it up, and I didn’t see
|
||||
much at that point. I wasn’t too excited. I went through readme, and
|
||||
noticed that author ([dhruvasagar]) put a fairly big emphasis on the
|
||||
"Agenda view". I had no idea what "Agenda view" is. Thankfully, the
|
||||
“Agenda view”. I had no idea what “Agenda view” is. Thankfully, the
|
||||
author also made a [screencast], which is rather long (1.5h), but I
|
||||
had some time, so I went through it.
|
||||
|
||||
At that point, I was first met with "Capturing" and "Refiling". *My
|
||||
At that point, I was first met with “Capturing” and “Refiling”. *My
|
||||
mind was blown!* What a simple, yet extremely powerful idea! How had
|
||||
that never crossed my mind? From that point on, this plugin had my
|
||||
full attention.
|
||||
|
||||
I'm always emphasizing that [dhruvasagar] and his [vim-dotoo] plugin
|
||||
I’m always emphasizing that [dhruvasagar] and his [vim-dotoo] plugin
|
||||
are most deserving for having inspired
|
||||
<https://github.com/nvim-orgmode/orgmode>, and I can't thank him
|
||||
<https://github.com/nvim-orgmode/orgmode>, and I can’t thank him
|
||||
enough for that.
|
||||
|
||||
|
||||
|
|
@ -105,7 +105,7 @@ First steps with vim-dotoo and birth of orgmode.nvim
|
|||
noticing the differences, and some of the missing features that were
|
||||
now looking quite attractive. I made [few contributions] to
|
||||
vim-dotoo. As time passed, and my notes started to grow, things began
|
||||
being slow. I did some profiling, and figured out that it's just a
|
||||
being slow. I did some profiling, and figured out that it’s just a
|
||||
usual Vim problem, Vimscript performance. It was just too slow for
|
||||
certain things that Orgmode provides, and it would hardly get any
|
||||
better as more things are added.
|
||||
|
|
@ -115,7 +115,7 @@ First steps with vim-dotoo and birth of orgmode.nvim
|
|||
version 0.3, and was carefully following the progress on it. Lua was
|
||||
introduced as a first class citizen. A Bunch of new plugins arise from
|
||||
it. All the benchmarks showed that Lua outperforms Vimscript in almost
|
||||
everything. Besides the performance, Lua is a "normal" programming
|
||||
everything. Besides the performance, Lua is a “normal” programming
|
||||
language, which means that support for it is much better.
|
||||
|
||||
At that point, I became curious: Could Lua be the path to the faster
|
||||
|
|
@ -146,10 +146,10 @@ First steps with vim-dotoo and birth of orgmode.nvim
|
|||
Understanding the OrgMode syntax and all the functionality
|
||||
──────────────────────────────────────────────────────────
|
||||
|
||||
This is still the biggest challenge. I didn't have any idea how big
|
||||
and robust OrgMode is. If I would know it at that time, I wouldn't
|
||||
even jump on this train. It's really hard to grasp all of
|
||||
it. Considering I've only used it for around 8 months, I think I made
|
||||
This is still the biggest challenge. I didn’t have any idea how big
|
||||
and robust OrgMode is. If I would know it at that time, I wouldn’t
|
||||
even jump on this train. It’s really hard to grasp all of
|
||||
it. Considering I’ve only used it for around 8 months, I think I made
|
||||
some good progress on learning it.
|
||||
|
||||
|
||||
|
|
@ -178,20 +178,20 @@ Working with dates
|
|||
so this is not so surprising. There are some Lua plugins for dates,
|
||||
but those seemed a bit too basic for my use case, and I wanted to keep
|
||||
external plugins to the minimum. I went with a custom solution that
|
||||
uses Lua's native dates, which has certain limitations, but works out
|
||||
uses Lua’s native dates, which has certain limitations, but works out
|
||||
for most of the things.
|
||||
|
||||
|
||||
Highlighting, mostly in Agenda view
|
||||
───────────────────────────────────
|
||||
|
||||
Vim's syntax engine is fairly old, but still very much used,
|
||||
Vim’s syntax engine is fairly old, but still very much used,
|
||||
especially in the Vim community. Implementation of tree-sitter
|
||||
slightly improved this experience in Neovim, because "Highlight
|
||||
matches" are found via tree-sitter, instead of a bunch of regexes.
|
||||
slightly improved this experience in Neovim, because “Highlight
|
||||
matches” are found via tree-sitter, instead of a bunch of regexes.
|
||||
|
||||
This helped me out later for the Org file itself, but agenda view is
|
||||
still something that's built as a custom view. Old Syntax highlight
|
||||
still something that’s built as a custom view. Old Syntax highlight
|
||||
engine would be really hard to add, because the content is too
|
||||
dynamic. I went with the Neovim highlight API that allows Highlighting
|
||||
things by their exact position in the buffer. Tree-sitter
|
||||
|
|
@ -207,7 +207,7 @@ Keeping configuration simple and familiar to Emacs OrgMode
|
|||
Emacs OrgMode user, by having as many options as possible named
|
||||
completely the same as in Emacs.
|
||||
|
||||
For example, Here's a comparison of few options between Emacs and
|
||||
For example, Here’s a comparison of few options between Emacs and
|
||||
Neovim:
|
||||
|
||||
Emacs:
|
||||
|
|
@ -262,8 +262,8 @@ First release of orgmode.nvim and introduction of tree-sitter parser
|
|||
used. It got some traction, and people started testing it and
|
||||
reporting bugs.
|
||||
|
||||
One of the common questions was: /"Any plans to introduce tree-sitter
|
||||
parser?"/.
|
||||
One of the common questions was: /“Any plans to introduce tree-sitter
|
||||
parser?”/.
|
||||
|
||||
I knew about [tree-sitter] and used it in my day-to-day job for a few
|
||||
programming languages, but I had absolutely no idea how it worked, and
|
||||
|
|
@ -271,23 +271,23 @@ First release of orgmode.nvim and introduction of tree-sitter parser
|
|||
continued working on what I had.
|
||||
|
||||
One day, Emilia ([milisims]) contacted me via email to ask me if I
|
||||
would be willing to try the tree-sitter parser she's been working on
|
||||
would be willing to try the tree-sitter parser she’s been working on
|
||||
for some time. I gladly accepted. She gave me access to the
|
||||
repository, and I started tinkering with it in a separate branch. No
|
||||
one was aware at that point that tree-sitter support would happen some
|
||||
time soon.
|
||||
|
||||
After some time, I set up a "beta" branch called "tree-sitter" and
|
||||
After some time, I set up a “beta” branch called “tree-sitter” and
|
||||
[announced it for testing]. Once the reported bugs slowed to a
|
||||
trickle, I merged it into the "master" branch.
|
||||
trickle, I merged it into the “master” branch.
|
||||
|
||||
I believe that tree-sitter grammar for Org could help out other
|
||||
editors to implement their version of Orgmode plugin, but I don't
|
||||
editors to implement their version of Orgmode plugin, but I don’t
|
||||
think it would ever be helpful for Emacs. Emacs parser is the one and
|
||||
only that has it all implemented. Also, as much as tree-sitter is
|
||||
powerful, its main purpose is to parse programming languages, which
|
||||
mostly has "static" patterns to match. Orgmode is by its nature
|
||||
dynamic, which causes a variety of issues for a parser that's not
|
||||
mostly has “static” patterns to match. Orgmode is by its nature
|
||||
dynamic, which causes a variety of issues for a parser that’s not
|
||||
meant for that kind of usage.
|
||||
|
||||
|
||||
|
|
@ -306,11 +306,11 @@ Limitations
|
|||
═══════════
|
||||
|
||||
(Neo)Vim is a great editor, but it still cannot compare to Emacs in
|
||||
certain things. Manipulating the "View" part of the editor is tricky
|
||||
certain things. Manipulating the “View” part of the editor is tricky
|
||||
or impossible for certain things.
|
||||
|
||||
I even [made a label] for reported issues where Neovim support for
|
||||
certain things is a blocker. I'm hoping that at least some of these
|
||||
certain things is a blocker. I’m hoping that at least some of these
|
||||
will be available in future Neovim releases.
|
||||
|
||||
|
||||
|
|
@ -326,9 +326,9 @@ Features
|
|||
mention one feature that does not exist as a built/-in feature in the
|
||||
Emacs Orgmode: [Notifications].
|
||||
|
||||
This allows getting a "desktop notification" for tasks that are within
|
||||
This allows getting a “desktop notification” for tasks that are within
|
||||
the specified threshold for schedule/deadline time. It requires some
|
||||
configuration to set up a cron job, but it's been working great for me
|
||||
configuration to set up a cron job, but it’s been working great for me
|
||||
for several months now.
|
||||
|
||||
|
||||
|
|
@ -342,15 +342,15 @@ Features
|
|||
Plans
|
||||
═════
|
||||
|
||||
The current state of the project is very usable for me. I'm not
|
||||
lacking any of the major features, mostly because I'm not used to
|
||||
using them. Nevertheless, there are plans to add more things, and I'm
|
||||
The current state of the project is very usable for me. I’m not
|
||||
lacking any of the major features, mostly because I’m not used to
|
||||
using them. Nevertheless, there are plans to add more things, and I’m
|
||||
getting a lot of help from the community. I want to specifically
|
||||
mention [levouh] and [lukas-reineke], since they added a lot of value
|
||||
to the project, and I want to thank them and everyone else who
|
||||
contributed. Their help is much appreciated.
|
||||
|
||||
There are few high priority tasks that I'm hoping to flush out first:
|
||||
There are few high priority tasks that I’m hoping to flush out first:
|
||||
|
||||
• Implementing [v1.0.0] release of the tree-sitter parser. This should
|
||||
allow for faster and less error-prone parsing.
|
||||
|
|
@ -393,12 +393,12 @@ Plans
|
|||
Closing thoughts
|
||||
════════════════
|
||||
|
||||
When I started working on [nvim-orgmode], I didn't have a clue what
|
||||
I'm jumping into. Every day I learn about more and more Orgmode
|
||||
features that I wasn't even aware existed.
|
||||
When I started working on [nvim-orgmode], I didn’t have a clue what
|
||||
I’m jumping into. Every day I learn about more and more Orgmode
|
||||
features that I wasn’t even aware existed.
|
||||
|
||||
I'm certain that this project will never manage to clone the Orgmode
|
||||
functionality completely, but I'm hoping it will get close enough so
|
||||
I’m certain that this project will never manage to clone the Orgmode
|
||||
functionality completely, but I’m hoping it will get close enough so
|
||||
everyone from Neovim community and Emacsers trying out Neovim will be
|
||||
able to use it for their needs.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>Special Announcement</title>
|
||||
|
|
@ -55,27 +55,27 @@ 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.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org24d0a1f">
|
||||
<figure id="org3ee46f3">
|
||||
<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>
|
||||
<figcaption><span class="figure-number">Figure 1: </span>Translation between Org’s syntax and our new Confluence overlords’s equivalents</figcaption>
|
||||
</figure>
|
||||
|
||||
<p>
|
||||
We'd like to thank the <span class='acr'>FSF</span> for giving the Org project the space and support to
|
||||
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
|
||||
Atlassian prior to contributing.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
This new partnership enables new and exciting integrations with Atlassian's
|
||||
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
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: Special Announcement
|
||||
#+date: 2022-04-01
|
||||
#+author: TEC
|
||||
|
|
|
|||
|
|
@ -20,19 +20,19 @@ 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.
|
||||
|
||||
<file:figures/org-markup-to-confluence.svg>
|
||||
|
||||
We'd like to thank the FSF for giving the Org project the space and
|
||||
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 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
|
||||
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
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<!-- 2024-01-12 Fri 13:05 -->
|
||||
<!-- 2024-01-12 Fri 13:39 -->
|
||||
<meta charset="utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>May 2022</title>
|
||||
|
|
@ -62,14 +62,14 @@ MathJax = {
|
|||
<p class="subtitle" role="doc-subtitle">Folding more improvement into Org</p>
|
||||
</header><p>
|
||||
Finding time as of late has been more difficult than I anticipated, and on top
|
||||
of that, just as I was thinking of writing last month's post, I got distracted
|
||||
of that, just as I was thinking of writing last month’s post, I got distracted
|
||||
by an exciting patchset that has been in the works for over a year finally
|
||||
getting sorted out and landing. So, I hope that some of the fun developments in
|
||||
this post will make up the absense of the last one 🙂.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Since it's been longer than I thought since the last standard post, we've got a
|
||||
Since it’s been longer than I thought since the last standard post, we’ve got a
|
||||
fair few commits to catch up on — about 200. Most of these are miscellaneous
|
||||
minor improvements and bugfixes, but a few notable changes have arrived too.
|
||||
</p>
|
||||
|
|
@ -77,7 +77,7 @@ minor improvements and bugfixes, but a few notable changes have arrived too.
|
|||
<h2 id="folding">Folding<a aria-hidden="true" href="#folding">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-folding">
|
||||
<p>
|
||||
The fabulous new folding engine (<kbd>org-fold-core</kbd>) should noticeably improve Org's
|
||||
The fabulous new folding engine (<kbd>org-fold-core</kbd>) should noticeably improve Org’s
|
||||
performance with large files. It contains a number of key optimisations to
|
||||
improve speed, namely:
|
||||
</p>
|
||||
|
|
@ -94,21 +94,21 @@ kind enough to whip up some benchmarks.
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org02e48a4">
|
||||
<figure id="org7c32a15">
|
||||
<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="org6c3910b">
|
||||
<figure id="orgcaf3374">
|
||||
<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>
|
||||
</figure>
|
||||
|
||||
<p>
|
||||
Well this looks very promising<sup><a id="fnr.1" class="footref" href="#fn.1" role="doc-backlink">1</a></sup>! Let's see how much of an improvement this is overall.
|
||||
Well this looks very promising<sup><a id="fnr.1" class="footref" href="#fn.1" role="doc-backlink">1</a></sup>! Let’s see how much of an improvement this is overall.
|
||||
</p>
|
||||
|
||||
<div id='folding,table--1' class='table'>
|
||||
|
|
@ -183,23 +183,23 @@ Well this looks very promising<sup><a id="fnr.1" class="footref" href="#fn.1" ro
|
|||
|
||||
<p>
|
||||
To be clear, even the smallest file in this data — a 1.1 Mb Org file with around
|
||||
a thousand headings, is fairly large. So, it's unlikely you'll notice much of a
|
||||
a thousand headings, is fairly large. So, it’s unlikely you’ll notice much of a
|
||||
difference with small–medium files, but if you a few large+ files this should
|
||||
be a <i>fantastic</i> improvement. Once again, thanks Ihor!
|
||||
</p>
|
||||
|
||||
<div class="warning" id="org1c64527">
|
||||
<div class="warning" id="orgab1bff5">
|
||||
<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>.
|
||||
If you are involved in any packages affected by this, you'll either want to
|
||||
packages like <kbd>evil-search</kbd> and <kbd>consult</kbd>’s <code>consult-line</code>.
|
||||
If you are involved in any packages affected by this, you’ll either want to
|
||||
consider supporting invisible text, or look at <code>isearch-filter-predicate</code> and
|
||||
<code>isearch-mode-end-hook</code>, which <kbd>org-fold</kbd> now uses.
|
||||
If you're an end-user, perhaps politely make an issue on the repo for a project
|
||||
If you’re an end-user, perhaps politely make an issue on the repo for a project
|
||||
<i>if no issue currently exists</i>, and either:
|
||||
</p>
|
||||
<ul class="org-ul">
|
||||
<li>Stay off Org's bleeding edge till the package ecosystem has adapted to this change</li>
|
||||
<li>Stay off Org’s bleeding edge till the package ecosystem has adapted to this change</li>
|
||||
<li>Help the packages you use adapt to this change</li>
|
||||
<li>Set <code>org-fold-core-style</code> to <code>overlays</code> to restore the old behaviour</li>
|
||||
</ul>
|
||||
|
|
@ -214,18 +214,18 @@ If you're an end-user, perhaps politely make an issue on the repo for a project
|
|||
All too often exporting code to LaTeX has been a disappointment, with lovely
|
||||
syntax highlighting from Emacs major modes replaced with a markedly inferior
|
||||
attempt by pygments (setting <code>org-latex-listings</code> to <code>minted</code>) in a colour scheme I
|
||||
don't really like.
|
||||
don’t really like.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
A bit over a year ago, a project called <a href="https://github.com/tecosaur/engrave-faces">engrave-faces</a> started with the aim of
|
||||
making Emacs' font-lock more exportable, like a generalised <kbd>htmlize.el</kbd>. This has
|
||||
making Emacs’ font-lock more exportable, like a generalised <kbd>htmlize.el</kbd>. This has
|
||||
recently been used to provide a new option for inline and block source code
|
||||
exports in LaTeX.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="orgf39b777">
|
||||
<figure id="orgf152c8a">
|
||||
<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,14 +250,14 @@ The theme can also be set on a per-block level using the LaTeX attribute
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org3ce23a5">
|
||||
<figure id="orgeceade1">
|
||||
<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>
|
||||
</figure>
|
||||
|
||||
<p>
|
||||
Here's what using these new capabilities looks like in practice.
|
||||
Here’s what using these new capabilities looks like in practice.
|
||||
</p>
|
||||
|
||||
<details id='-engraved-source,code--1' class='code' open><summary><span class="lang">Org mode</span></summary>
|
||||
|
|
@ -290,9 +290,9 @@ currently available, but I am a tad biased 😛.
|
|||
<h2 id="texinfo-export-improvements">TexInfo export improvements<a aria-hidden="true" href="#texinfo-export-improvements">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-texinfo-export-improvements">
|
||||
<p>
|
||||
Jonas Bernoulli has been using a custom TexInfo backend for Magit's
|
||||
documentation for a while now, and over the past few months he's worked the
|
||||
features he was missing into Org's built-in TexInfo exporter.
|
||||
Jonas Bernoulli has been using a custom TexInfo backend for Magit’s
|
||||
documentation for a while now, and over the past few months he’s worked the
|
||||
features he was missing into Org’s built-in TexInfo exporter.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -347,18 +347,18 @@ Instead of
|
|||
<h2 id="package-highlight-org">Package highlight: org-modern<a aria-hidden="true" href="#package-highlight-org">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-package-highlight-org">
|
||||
<p>
|
||||
I think we've all <a href="https://github.com/integral-dw/org-superstar-mode">seen</a> <a href="https://github.com/sabof/org-bullets">plenty</a> of <kbd>org-mode</kbd> <a href="https://github.com/Fuco1/org-pretty-table">prettification</a> <a href="https://github.com/harrybournis/org-fancy-priorities">packages</a> <a href="https://gitlab.com/marcowahl/org-pretty-tags">before</a>, so
|
||||
what makes Minad's <a href="https://github.com/minad/org-modern">org-modern</a> special? It's actually doing something similar to
|
||||
Ihor's org-fold improvements, switching out slower overlay-based approaches for
|
||||
I think we’ve all <a href="https://github.com/integral-dw/org-superstar-mode">seen</a> <a href="https://github.com/sabof/org-bullets">plenty</a> of <kbd>org-mode</kbd> <a href="https://github.com/Fuco1/org-pretty-table">prettification</a> <a href="https://github.com/harrybournis/org-fancy-priorities">packages</a> <a href="https://gitlab.com/marcowahl/org-pretty-tags">before</a>, so
|
||||
what makes Minad’s <a href="https://github.com/minad/org-modern">org-modern</a> special? It’s actually doing something similar to
|
||||
Ihor’s org-fold improvements, switching out slower overlay-based approaches for
|
||||
text properties. I can confirm that switching out <kbd>org-superstar-mode</kbd> for
|
||||
<kbd>org-modern</kbd> has made a substantial improvement in my experience, halving the
|
||||
first-load time of my <kbd>config.org</kbd> to around 20 seconds. If you're a fan of Org
|
||||
prettification and haven't taken a look at this package, I highly recommend
|
||||
first-load time of my <kbd>config.org</kbd> to around 20 seconds. If you’re a fan of Org
|
||||
prettification and haven’t taken a look at this package, I highly recommend
|
||||
giving it a shot.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org701b21b">
|
||||
<figure id="org7ef011c">
|
||||
<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>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Created 2024-01-12 Fri 13:05
|
||||
# Created 2024-01-12 Fri 13:39
|
||||
#+title: May 2022
|
||||
#+date: 2022-05-31
|
||||
#+author: TEC
|
||||
|
|
|
|||
|
|
@ -10,14 +10,14 @@
|
|||
|
||||
|
||||
Finding time as of late has been more difficult than I anticipated, and
|
||||
on top of that, just as I was thinking of writing last month's post, I
|
||||
on top of that, just as I was thinking of writing last month’s post, I
|
||||
got distracted by an exciting patchset that has been in the works for
|
||||
over a year finally getting sorted out and landing. So, I hope that some
|
||||
of the fun developments in this post will make up the absense of the
|
||||
last one 🙂.
|
||||
|
||||
Since it's been longer than I thought since the last standard post,
|
||||
we've got a fair few commits to catch up on — about 200. Most of these
|
||||
Since it’s been longer than I thought since the last standard post,
|
||||
we’ve got a fair few commits to catch up on — about 200. Most of these
|
||||
are miscellaneous minor improvements and bugfixes, but a few notable
|
||||
changes have arrived too.
|
||||
|
||||
|
|
@ -26,7 +26,7 @@ Folding
|
|||
═══════
|
||||
|
||||
The fabulous new folding engine (`org-fold-core') should noticeably
|
||||
improve Org's performance with large files. It contains a number of
|
||||
improve Org’s performance with large files. It contains a number of
|
||||
key optimisations to improve speed, namely:
|
||||
⁃ Deferring fontification of folded regions
|
||||
⁃ Using text properties (𝒪(n log n)) instead of overlays (𝒪(n^2)) for
|
||||
|
|
@ -43,7 +43,7 @@ Folding
|
|||
|
||||
<file:figures/org-fold-perf-shifttab-showall.svg>
|
||||
|
||||
Well this looks very promising[1]! Let's see how much of an
|
||||
Well this looks very promising[1]! Let’s see how much of an
|
||||
improvement this is overall.
|
||||
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
|
@ -59,20 +59,20 @@ Folding
|
|||
display modes (in seconds).
|
||||
|
||||
To be clear, even the smallest file in this data — a 1.1 Mb Org file
|
||||
with around a thousand headings, is fairly large. So, it's unlikely
|
||||
you'll notice much of a difference with small–medium files, but if you
|
||||
with around a thousand headings, is fairly large. So, it’s unlikely
|
||||
you’ll notice much of a difference with small–medium files, but if you
|
||||
a few large+ files this should be a /fantastic/ improvement. Once
|
||||
again, thanks Ihor!
|
||||
|
||||
The change to text properties instead of overlays breaks a number of
|
||||
third party packages like `evil-search' and `consult''s
|
||||
third party packages like `evil-search' and `consult'’s
|
||||
`consult-line'. If you are involved in any packages affected by this,
|
||||
you'll either want to consider supporting invisible text, or look at
|
||||
you’ll either want to consider supporting invisible text, or look at
|
||||
`isearch-filter-predicate' and `isearch-mode-end-hook', which
|
||||
`org-fold' now uses. If you're an end-user, perhaps politely make an
|
||||
`org-fold' now uses. If you’re an end-user, perhaps politely make an
|
||||
issue on the repo for a project /if no issue currently exists/, and
|
||||
either:
|
||||
⁃ Stay off Org's bleeding edge till the package ecosystem has adapted
|
||||
⁃ Stay off Org’s bleeding edge till the package ecosystem has adapted
|
||||
to this change
|
||||
⁃ Help the packages you use adapt to this change
|
||||
⁃ Set `org-fold-core-style' to `overlays' to restore the old behaviour
|
||||
|
|
@ -84,10 +84,10 @@ Folding
|
|||
All too often exporting code to LaTeX has been a disappointment, with
|
||||
lovely syntax highlighting from Emacs major modes replaced with a
|
||||
markedly inferior attempt by pygments (setting `org-latex-listings' to
|
||||
`minted') in a colour scheme I don't really like.
|
||||
`minted') in a colour scheme I don’t really like.
|
||||
|
||||
A bit over a year ago, a project called [engrave-faces] started with
|
||||
the aim of making Emacs' font-lock more exportable, like a generalised
|
||||
the aim of making Emacs’ font-lock more exportable, like a generalised
|
||||
`htmlize.el'. This has recently been used to provide a new option for
|
||||
inline and block source code exports in LaTeX.
|
||||
|
||||
|
|
@ -109,7 +109,7 @@ Folding
|
|||
|
||||
<file:figures/engraved-faces-multitheme.png>
|
||||
|
||||
Here's what using these new capabilities looks like in practice.
|
||||
Here’s what using these new capabilities looks like in practice.
|
||||
|
||||
┌────
|
||||
│ #+title: Engraving source blocks
|
||||
|
|
@ -135,9 +135,9 @@ Folding
|
|||
TexInfo export improvements
|
||||
═══════════════════════════
|
||||
|
||||
Jonas Bernoulli has been using a custom TexInfo backend for Magit's
|
||||
documentation for a while now, and over the past few months he's
|
||||
worked the features he was missing into Org's built-in TexInfo
|
||||
Jonas Bernoulli has been using a custom TexInfo backend for Magit’s
|
||||
documentation for a while now, and over the past few months he’s
|
||||
worked the features he was missing into Org’s built-in TexInfo
|
||||
exporter.
|
||||
|
||||
Upstreaming like this always takes a fair bit of effort, so thank you
|
||||
|
|
@ -180,14 +180,14 @@ Toggle noweb prefix handling
|
|||
Package highlight: org-modern
|
||||
═════════════════════════════
|
||||
|
||||
I think we've all [seen] [plenty] of `org-mode' [prettification]
|
||||
[packages] [before], so what makes Minad's [org-modern] special? It's
|
||||
actually doing something similar to Ihor's org-fold improvements,
|
||||
I think we’ve all [seen] [plenty] of `org-mode' [prettification]
|
||||
[packages] [before], so what makes Minad’s [org-modern] special? It’s
|
||||
actually doing something similar to Ihor’s org-fold improvements,
|
||||
switching out slower overlay-based approaches for text properties. I
|
||||
can confirm that switching out `org-superstar-mode' for `org-modern'
|
||||
has made a substantial improvement in my experience, halving the
|
||||
first-load time of my `config.org' to around 20 seconds. If you're a
|
||||
fan of Org prettification and haven't taken a look at this package, I
|
||||
first-load time of my `config.org' to around 20 seconds. If you’re a
|
||||
fan of Org prettification and haven’t taken a look at this package, I
|
||||
highly recommend giving it a shot.
|
||||
|
||||
<file:figures/org-modern-readme-demo.gif>
|
||||
|
|
|
|||
114
index.html
114
index.html
|
|
@ -89,14 +89,14 @@ Posts are published in <kbd>.html</kbd>, <kbd>.org</kbd>, <kbd>.org.html</kbd>,
|
|||
<div class="outline-text-2" id="text-htmla-href2022-05">
|
||||
<p>
|
||||
Finding time as of late has been more difficult than I anticipated, and on top
|
||||
of that, just as I was thinking of writing last month's post, I got distracted
|
||||
of that, just as I was thinking of writing last month’s post, I got distracted
|
||||
by an exciting patchset that has been in the works for over a year finally
|
||||
getting sorted out and landing. So, I hope that some of the fun developments in
|
||||
this post will make up the absense of the last one 🙂.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Since it's been longer than I thought since the last standard post, we've got a
|
||||
Since it’s been longer than I thought since the last standard post, we’ve got a
|
||||
fair few commits to catch up on — about 200. Most of these are miscellaneous
|
||||
minor improvements and bugfixes, but a few notable changes have arrived too.
|
||||
</p>
|
||||
|
|
@ -105,7 +105,7 @@ minor improvements and bugfixes, but a few notable changes have arrived too.
|
|||
<h3 id="folding">Folding<a aria-hidden="true" href="#folding">#</a> </h3>
|
||||
<div class="outline-text-3" id="text-folding">
|
||||
<p>
|
||||
The fabulous new folding engine (<kbd>org-fold-core</kbd>) should noticeably improve Org's
|
||||
The fabulous new folding engine (<kbd>org-fold-core</kbd>) should noticeably improve Org’s
|
||||
performance with large files. It contains a number of key optimisations to
|
||||
improve speed, namely:
|
||||
</p>
|
||||
|
|
@ -122,21 +122,21 @@ kind enough to whip up some benchmarks.
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org0dd184c">
|
||||
<figure id="org19e7b58">
|
||||
<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="org0fcffbe">
|
||||
<figure id="orga75bade">
|
||||
<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>
|
||||
</figure>
|
||||
|
||||
<p>
|
||||
Well this looks very promising<sup><a id="fnr.1" class="footref" href="#fn.1" role="doc-backlink">1</a></sup>! Let's see how much of an improvement this is overall.
|
||||
Well this looks very promising<sup><a id="fnr.1" class="footref" href="#fn.1" role="doc-backlink">1</a></sup>! Let’s see how much of an improvement this is overall.
|
||||
</p>
|
||||
|
||||
<div id='folding,table--1' class='table'>
|
||||
|
|
@ -211,23 +211,23 @@ Well this looks very promising<sup><a id="fnr.1" class="footref" href="#fn.1" ro
|
|||
|
||||
<p>
|
||||
To be clear, even the smallest file in this data — a 1.1 Mb Org file with around
|
||||
a thousand headings, is fairly large. So, it's unlikely you'll notice much of a
|
||||
a thousand headings, is fairly large. So, it’s unlikely you’ll notice much of a
|
||||
difference with small–medium files, but if you a few large+ files this should
|
||||
be a <i>fantastic</i> improvement. Once again, thanks Ihor!
|
||||
</p>
|
||||
|
||||
<div class="warning" id="org6e3b1ea">
|
||||
<div class="warning" id="org8909b99">
|
||||
<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>.
|
||||
If you are involved in any packages affected by this, you'll either want to
|
||||
packages like <kbd>evil-search</kbd> and <kbd>consult</kbd>’s <code>consult-line</code>.
|
||||
If you are involved in any packages affected by this, you’ll either want to
|
||||
consider supporting invisible text, or look at <code>isearch-filter-predicate</code> and
|
||||
<code>isearch-mode-end-hook</code>, which <kbd>org-fold</kbd> now uses.
|
||||
If you're an end-user, perhaps politely make an issue on the repo for a project
|
||||
If you’re an end-user, perhaps politely make an issue on the repo for a project
|
||||
<i>if no issue currently exists</i>, and either:
|
||||
</p>
|
||||
<ul class="org-ul">
|
||||
<li>Stay off Org's bleeding edge till the package ecosystem has adapted to this change</li>
|
||||
<li>Stay off Org’s bleeding edge till the package ecosystem has adapted to this change</li>
|
||||
<li>Help the packages you use adapt to this change</li>
|
||||
<li>Set <code>org-fold-core-style</code> to <code>overlays</code> to restore the old behaviour</li>
|
||||
</ul>
|
||||
|
|
@ -242,18 +242,18 @@ If you're an end-user, perhaps politely make an issue on the repo for a project
|
|||
All too often exporting code to LaTeX has been a disappointment, with lovely
|
||||
syntax highlighting from Emacs major modes replaced with a markedly inferior
|
||||
attempt by pygments (setting <code>org-latex-listings</code> to <code>minted</code>) in a colour scheme I
|
||||
don't really like.
|
||||
don’t really like.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
A bit over a year ago, a project called <a href="https://github.com/tecosaur/engrave-faces">engrave-faces</a> started with the aim of
|
||||
making Emacs' font-lock more exportable, like a generalised <kbd>htmlize.el</kbd>. This has
|
||||
making Emacs’ font-lock more exportable, like a generalised <kbd>htmlize.el</kbd>. This has
|
||||
recently been used to provide a new option for inline and block source code
|
||||
exports in LaTeX.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org0d80784">
|
||||
<figure id="org17d2444">
|
||||
<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,14 +278,14 @@ The theme can also be set on a per-block level using the LaTeX attribute
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org26c0201">
|
||||
<figure id="org1fad198">
|
||||
<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>
|
||||
</figure>
|
||||
|
||||
<p>
|
||||
Here's what using these new capabilities looks like in practice.
|
||||
Here’s what using these new capabilities looks like in practice.
|
||||
</p>
|
||||
|
||||
<details id='-engraved-source,code--1' class='code' open><summary><span class="lang">Org mode</span></summary>
|
||||
|
|
@ -318,9 +318,9 @@ currently available, but I am a tad biased 😛.
|
|||
<h3 id="texinfo-export-improvements">TexInfo export improvements<a aria-hidden="true" href="#texinfo-export-improvements">#</a> </h3>
|
||||
<div class="outline-text-3" id="text-texinfo-export-improvements">
|
||||
<p>
|
||||
Jonas Bernoulli has been using a custom TexInfo backend for Magit's
|
||||
documentation for a while now, and over the past few months he's worked the
|
||||
features he was missing into Org's built-in TexInfo exporter.
|
||||
Jonas Bernoulli has been using a custom TexInfo backend for Magit’s
|
||||
documentation for a while now, and over the past few months he’s worked the
|
||||
features he was missing into Org’s built-in TexInfo exporter.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -375,18 +375,18 @@ Instead of
|
|||
<h3 id="package-highlight-org">Package highlight: org-modern<a aria-hidden="true" href="#package-highlight-org">#</a> </h3>
|
||||
<div class="outline-text-3" id="text-package-highlight-org">
|
||||
<p>
|
||||
I think we've all <a href="https://github.com/integral-dw/org-superstar-mode">seen</a> <a href="https://github.com/sabof/org-bullets">plenty</a> of <kbd>org-mode</kbd> <a href="https://github.com/Fuco1/org-pretty-table">prettification</a> <a href="https://github.com/harrybournis/org-fancy-priorities">packages</a> <a href="https://gitlab.com/marcowahl/org-pretty-tags">before</a>, so
|
||||
what makes Minad's <a href="https://github.com/minad/org-modern">org-modern</a> special? It's actually doing something similar to
|
||||
Ihor's org-fold improvements, switching out slower overlay-based approaches for
|
||||
I think we’ve all <a href="https://github.com/integral-dw/org-superstar-mode">seen</a> <a href="https://github.com/sabof/org-bullets">plenty</a> of <kbd>org-mode</kbd> <a href="https://github.com/Fuco1/org-pretty-table">prettification</a> <a href="https://github.com/harrybournis/org-fancy-priorities">packages</a> <a href="https://gitlab.com/marcowahl/org-pretty-tags">before</a>, so
|
||||
what makes Minad’s <a href="https://github.com/minad/org-modern">org-modern</a> special? It’s actually doing something similar to
|
||||
Ihor’s org-fold improvements, switching out slower overlay-based approaches for
|
||||
text properties. I can confirm that switching out <kbd>org-superstar-mode</kbd> for
|
||||
<kbd>org-modern</kbd> has made a substantial improvement in my experience, halving the
|
||||
first-load time of my <kbd>config.org</kbd> to around 20 seconds. If you're a fan of Org
|
||||
prettification and haven't taken a look at this package, I highly recommend
|
||||
first-load time of my <kbd>config.org</kbd> to around 20 seconds. If you’re a fan of Org
|
||||
prettification and haven’t taken a look at this package, I highly recommend
|
||||
giving it a shot.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="orga39661b">
|
||||
<figure id="orge46b563">
|
||||
<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>
|
||||
|
|
@ -447,7 +447,7 @@ 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.
|
||||
</p>
|
||||
|
|
@ -471,14 +471,14 @@ experience outside Emacs.
|
|||
</p>
|
||||
|
||||
<p>
|
||||
"But I use Emacs, I don't care" you may say. In that case, I'd like to point out
|
||||
“But I use Emacs, I don’t care” you may say. In that case, I’d like to point out
|
||||
that wider spread and better Org support enriches the Org ecosystem as a whole.
|
||||
It makes the format more approachable, and <i>useful</i> for other people. This is good
|
||||
for everybody.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Without any further ado, here's the guest post kindly written by Kristijan.
|
||||
Without any further ado, here’s the guest post kindly written by Kristijan.
|
||||
Enjoy!
|
||||
</p>
|
||||
|
||||
|
|
@ -486,7 +486,7 @@ Enjoy!
|
|||
|
||||
<p>
|
||||
Like every beginner Vim user, at some point I ran into a usual editor war post:
|
||||
Vim vs Emacs. At that time, I didn't have an idea what "Emacs" was.
|
||||
Vim vs Emacs. At that time, I didn’t have an idea what “Emacs” was.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -498,7 +498,7 @@ Vim vs Emacs. At that time, I didn't have an idea what "Emacs" was.
|
|||
<h2 id="htmla-href2022-01"><a href='2022-01-31-caching.html' style='text-decoration:none;color:inherit'> January 2022 <span class='tag'><span>2022-01-31</span></span></a><a aria-hidden="true" href="#htmla-href2022-01">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-htmla-href2022-01">
|
||||
<p>
|
||||
There are less "obvious user-facing changes" this month, but a lot of good work
|
||||
There are less “obvious user-facing changes” this month, but a lot of good work
|
||||
has been happening 🙂.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -511,8 +511,8 @@ existed for a while now, but it used to be too buggy to be useful.
|
|||
</p>
|
||||
|
||||
<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
|
||||
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 , however Ihor has continued to make strides with the
|
||||
cache.
|
||||
</p>
|
||||
|
|
@ -520,7 +520,7 @@ cache.
|
|||
<p>
|
||||
Getting the cache right is tough though, and so while the situation is much
|
||||
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:
|
||||
only take one thing away from the post, I’d like it to be this:
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -534,8 +534,8 @@ only take one thing away from the post, I'd like it to be this:
|
|||
<div class="outline-text-2" id="text-htmla-href2021-12">
|
||||
<p>
|
||||
Just over eight months ago, I kicked off <i>This Month in Org</i> with an emphatic
|
||||
announcement of the blog's in the form of a <a href="2021-04-26-Welcome.html">Welcome</a> post. If you haven't
|
||||
guessed, this is the first "blog post" I've ever written. In that <i>welcome</i> post,
|
||||
announcement of the blog’s in the form of a <a href="2021-04-26-Welcome.html">Welcome</a> post. If you haven’t
|
||||
guessed, this is the first “blog post” I’ve ever written. In that <i>welcome</i> post,
|
||||
I gave my motivation for starting the blog — essentially to bridge a perceived
|
||||
gap in information sources between a subscription to the Org project mailing
|
||||
list, and nothing.
|
||||
|
|
@ -556,8 +556,8 @@ mention what <i>I</i> want to accomplish with it. By starting <i>TMiO</i> I hope
|
|||
<h2 id="htmla-href2021-11"><a href='2021-11-30-element.html' style='text-decoration:none;color:inherit'> November 2021 <span class='tag'><span>2021-11-30</span></span></a><a aria-hidden="true" href="#htmla-href2021-11">#</a> </h2>
|
||||
<div class="outline-text-2" id="text-htmla-href2021-11">
|
||||
<p>
|
||||
With a 9.5 release highlight post last month, and the month before skipped, it's
|
||||
now <i>three months</i> since the last regular instalment of <span class='acr'>TMIO</span>. Let's get back up
|
||||
With a 9.5 release highlight post last month, and the month before skipped, it’s
|
||||
now <i>three months</i> since the last regular instalment of <span class='acr'>TMIO</span>. Let’s get back up
|
||||
to date on some of the latest happenings with Org.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -568,8 +568,8 @@ to date on some of the latest happenings with Org.
|
|||
Looking at the wider ecosystem, it certainly appears that there is a growing
|
||||
appetite for Org markup outside org-mode. More projects like <a href="https://gohugo.io/">Hugo</a> and <a href="https://logseq.com/">Logseq</a>
|
||||
seem to be interested in supporting Org markup, and there has been a recent
|
||||
growth in editor extensions like Neovim's <a href="https://github.com/nvim-orgmode/orgmode/">orgmode.nvim</a> (started in March this
|
||||
year) and Sublime Text's <a href="https://packagecontrol.io/packages/OrgExtended">OrgExtended</a> (started in June this year).
|
||||
growth in editor extensions like Neovim’s <a href="https://github.com/nvim-orgmode/orgmode/">orgmode.nvim</a> (started in March this
|
||||
year) and Sublime Text’s <a href="https://packagecontrol.io/packages/OrgExtended">OrgExtended</a> (started in June this year).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -583,15 +583,15 @@ year) and Sublime Text's <a href="https://packagecontrol.io/packages/OrgExtended
|
|||
<div class="outline-text-2" id="text-htmla-href2021-10">
|
||||
<blockquote>
|
||||
<p>
|
||||
Turns out that life became busy enough that instead of delaying, last month's
|
||||
post had to be cancelled. We're now back to business as usual though 🙂.
|
||||
Turns out that life became busy enough that instead of delaying, last month’s
|
||||
post had to be cancelled. We’re now back to business as usual though 🙂.
|
||||
</p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
There have been some cool recent developments in Org over the past two months,
|
||||
but you'll have to learn about those is next month's edition as <i>Org 9.5 has been
|
||||
released</i> 🎉. So, let's go over some of the changes I'm most excited about, in no
|
||||
but you’ll have to learn about those is next month’s edition as <i>Org 9.5 has been
|
||||
released</i> 🎉. So, let’s go over some of the changes I’m most excited about, in no
|
||||
particular order. To get a more complete picture of the latest changes, see
|
||||
<a href="https://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/etc/ORG-NEWS?h=release_9.5#n14"><span class='acr'>ORG</span>-<span class='acr'>NEWS</span></a>.
|
||||
</p>
|
||||
|
|
@ -610,14 +610,14 @@ particular order. To get a more complete picture of the latest changes, see
|
|||
<div class="outline-text-2" id="text-htmla-href2021-08">
|
||||
<blockquote>
|
||||
<p>
|
||||
Dear readers, unfortunately I've been unusually busy as of late, and will
|
||||
continue to be for a bit over a month. As such, it's entirely likely that the
|
||||
Dear readers, unfortunately I’ve been unusually busy as of late, and will
|
||||
continue to be for a bit over a month. As such, it’s entirely likely that the
|
||||
next post or two may <del>be late</del> make use of creative dates too.
|
||||
</p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
In terms of Org development, we've had a fairly slow month — mostly tweaks and
|
||||
In terms of Org development, we’ve had a fairly slow month — mostly tweaks and
|
||||
fixes, concentrated on the new org-cite functionality. However, there have been
|
||||
big developments with Roam as of late.
|
||||
</p>
|
||||
|
|
@ -636,12 +636,12 @@ big developments with Roam as of late.
|
|||
<div class="outline-text-2" id="text-htmla-href2021-07">
|
||||
<p>
|
||||
Last month I not-at-all-subtly hinted that a certain long-awaited feature was
|
||||
arriving imminently. At this point, I think it's a good idea to set the tone for the rest of
|
||||
arriving imminently. At this point, I think it’s a good idea to set the tone for the rest of
|
||||
this post.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org372a347">
|
||||
<figure id="org030f7db">
|
||||
<img src="figures/celebrate-citations.svg" alt="celebrate-citations.svg" class="org-svg">
|
||||
|
||||
</figure>
|
||||
|
|
@ -661,17 +661,17 @@ this post.
|
|||
<p>
|
||||
The previous two months have been pretty good for Org development — with many
|
||||
bug fixes and feature improvements. This month has been substantially slower
|
||||
than the last<sup>[1]</sup>, but that's not to say not much is happening: in fact, there are
|
||||
than the last<sup>[1]</sup>, but that’s not to say not much is happening: in fact, there are
|
||||
some rather nifty contributions lined up for the not-too-distant future and a
|
||||
certain long-awaited feature branch<sup>[2]</sup> is getting very close to merging 😀.
|
||||
You'll just have to stick around to hear about those in a future edition of <span class='acr'>TMIO</span> 😉.
|
||||
You’ll just have to stick around to hear about those in a future edition of <span class='acr'>TMIO</span> 😉.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="orgbb06346">
|
||||
<figure id="org4428302">
|
||||
<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>
|
||||
<figcaption><span class="figure-number">Figure 6: </span>It’s right around the corner, I swear!</figcaption>
|
||||
</figure>
|
||||
</div>
|
||||
<div id="outline-container-customise-reference-command" class="outline-3">
|
||||
|
|
@ -696,7 +696,7 @@ asynchronous output from source blocks <i>with full support for sessions</i>
|
|||
</p>
|
||||
|
||||
<p>
|
||||
If you haven't used sessions before, you're in for a treat! By simply assigning
|
||||
If you haven’t used sessions before, you’re in for a treat! By simply assigning
|
||||
a named session to a source code block, e.g. <kbd>:session foo</kbd>, the same process will
|
||||
be reused for any other code blocks that specify the <kbd>foo</kbd> session. To do this for
|
||||
a certain language across the entire document, you can set the header argument
|
||||
|
|
@ -732,7 +732,7 @@ not-too-distant future 😍.
|
|||
<h3 id="discussion-contributor-support">A discussion on contributor support<a aria-hidden="true" href="#discussion-contributor-support">#</a> </h3>
|
||||
<div class="outline-text-3" id="text-discussion-contributor-support">
|
||||
<p>
|
||||
Concerns <a href="https://lists.gnu.org/archive/html/emacs-orgmode/2021-04/msg00291.html">were raised</a><sup>[1]</sup> about some contributors' patches languishing, and it not
|
||||
Concerns <a href="https://lists.gnu.org/archive/html/emacs-orgmode/2021-04/msg00291.html">were raised</a><sup>[1]</sup> about some contributors’ patches languishing, and it not
|
||||
being made clear how long it might take to get a response from someone.
|
||||
</p>
|
||||
|
||||
|
|
@ -767,8 +767,8 @@ and core maintainers:
|
|||
<div class="outline-text-3" id="text-introduction">
|
||||
<p>
|
||||
Org is an absolutely marvellous project. However, a quick glance at
|
||||
<a href="https://orgmode.org">https://orgmode.org</a> can lead one to think "so… it's an Emacs version of
|
||||
Markdown? What's the big deal?". While it's easy to understand how someone might
|
||||
<a href="https://orgmode.org">https://orgmode.org</a> can lead one to think “so… it’s an Emacs version of
|
||||
Markdown? What’s the big deal?”. While it’s easy to understand how someone might
|
||||
think that at first, that impression misses two crucial points:
|
||||
</p>
|
||||
<ul class="org-ul">
|
||||
|
|
|
|||
226
rss.xml
226
rss.xml
|
|
@ -14,8 +14,8 @@
|
|||
<link>https://blog.tecosaur.net/tmio/</link>
|
||||
<description><![CDATA[]]></description>
|
||||
<language>en</language>
|
||||
<pubDate>Fri, 12 Jan 2024 13:07:35 +0800</pubDate>
|
||||
<lastBuildDate>Fri, 12 Jan 2024 13:07:35 +0800</lastBuildDate>
|
||||
<pubDate>Fri, 12 Jan 2024 13:39:50 +0800</pubDate>
|
||||
<lastBuildDate>Fri, 12 Jan 2024 13:39:50 +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#orgf4b49e3">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#orgec8e566">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="orgcc126eb">
|
||||
<div class="info" id="org39a57e1">
|
||||
<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="org75bef27">
|
||||
<pre class="example" id="orgcafcbf2">
|
||||
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="org9423af2">
|
||||
<figure id="org6f50599">
|
||||
<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>
|
||||
|
|
@ -218,14 +218,14 @@
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org9f7a5bb">
|
||||
<figure id="orgd99fc4f">
|
||||
<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="org6f6ed94">
|
||||
<figure id="org5b274b2">
|
||||
<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="orge7922ee">
|
||||
<div class="warning" id="org95471ce">
|
||||
<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>.
|
||||
|
|
@ -354,7 +354,7 @@
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="orgbe36c8a">
|
||||
<figure id="org7b01426">
|
||||
<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>
|
||||
|
|
@ -538,9 +538,9 @@
|
|||
<h3 id="understanding-orgmode-syntax"><span class="section-number-3">4.1.</span> Understanding the OrgMode syntax and all the functionality</h3>
|
||||
<div class="outline-text-3" id="text-4-1">
|
||||
<p>
|
||||
This is still the biggest challenge. I didn't have any idea how big and robust
|
||||
OrgMode is. If I would know it at that time, I wouldn't even jump on this train.
|
||||
It's really hard to grasp all of it. Considering I've only used it for around 8
|
||||
This is still the biggest challenge. I didn’t have any idea how big and robust
|
||||
OrgMode is. If I would know it at that time, I wouldn’t even jump on this train.
|
||||
It’s really hard to grasp all of it. Considering I’ve only used it for around 8
|
||||
months, I think I made some good progress on learning it.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -577,7 +577,7 @@
|
|||
so this is not so surprising. There are some Lua plugins for dates, but
|
||||
those seemed a bit too basic for my use case, and I wanted to keep
|
||||
external plugins to the minimum. I went with a custom solution that uses
|
||||
Lua's native dates, which has certain limitations, but works out for
|
||||
Lua’s native dates, which has certain limitations, but works out for
|
||||
most of the things.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -586,15 +586,15 @@
|
|||
<h3 id="highlighting-mostly-agenda"><span class="section-number-3">4.4.</span> Highlighting, mostly in Agenda view</h3>
|
||||
<div class="outline-text-3" id="text-4-4">
|
||||
<p>
|
||||
Vim's syntax engine is fairly old, but still very much used, especially
|
||||
Vim’s syntax engine is fairly old, but still very much used, especially
|
||||
in the Vim community. Implementation of tree-sitter slightly improved
|
||||
this experience in Neovim, because "Highlight matches" are found via
|
||||
this experience in Neovim, because “Highlight matches” are found via
|
||||
tree-sitter, instead of a bunch of regexes.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
This helped me out later for the Org file itself, but agenda view is
|
||||
still something that's built as a custom view. Old Syntax highlight engine
|
||||
still something that’s built as a custom view. Old Syntax highlight engine
|
||||
would be really hard to add, because the content is too dynamic. I went
|
||||
with the Neovim highlight API that allows Highlighting things by their
|
||||
exact position in the buffer. Tree-sitter implementation does something
|
||||
|
|
@ -613,7 +613,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
For example, Here's a comparison of few options between Emacs and
|
||||
For example, Here’s a comparison of few options between Emacs and
|
||||
Neovim:
|
||||
</p>
|
||||
|
||||
|
|
@ -679,7 +679,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
One of the common questions was: <i>"Any plans to introduce tree-sitter parser?"</i>.
|
||||
One of the common questions was: <i>“Any plans to introduce tree-sitter parser?”</i>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -691,25 +691,25 @@
|
|||
|
||||
<p>
|
||||
One day, Emilia (<a href="https://github.com/milisims">milisims</a>) contacted me via email to ask me if I would be
|
||||
willing to try the tree-sitter parser she's been working on for some time. I
|
||||
willing to try the tree-sitter parser she’s been working on for some time. I
|
||||
gladly accepted. She gave me access to the repository, and I started tinkering
|
||||
with it in a separate branch. No one was aware at that point that tree-sitter
|
||||
support would happen some time soon.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
After some time, I set up a "beta" branch called "tree-sitter" and <a href="https://www.reddit.com/r/neovim/comments/ph2xqc/orgmodenvim_treesitter_support/">announced it
|
||||
After some time, I set up a “beta” branch called “tree-sitter” and <a href="https://www.reddit.com/r/neovim/comments/ph2xqc/orgmodenvim_treesitter_support/">announced it
|
||||
for testing</a>. Once the reported bugs slowed to a trickle, I merged it into the
|
||||
"master" branch.
|
||||
“master” branch.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
I believe that tree-sitter grammar for Org could help out other editors to
|
||||
implement their version of Orgmode plugin, but I don't think it would ever be
|
||||
implement their version of Orgmode plugin, but I don’t think it would ever be
|
||||
helpful for Emacs. Emacs parser is the one and only that has it all implemented.
|
||||
Also, as much as tree-sitter is powerful, its main purpose is to parse
|
||||
programming languages, which mostly has "static" patterns to match. Orgmode is
|
||||
by its nature dynamic, which causes a variety of issues for a parser that's not
|
||||
programming languages, which mostly has “static” patterns to match. Orgmode is
|
||||
by its nature dynamic, which causes a variety of issues for a parser that’s not
|
||||
meant for that kind of usage.
|
||||
</p>
|
||||
|
||||
|
|
@ -719,13 +719,13 @@
|
|||
|
||||
<p>
|
||||
(Neo)Vim is a great editor, but it still cannot compare to Emacs in certain
|
||||
things. Manipulating the "View" part of the editor is tricky or impossible for
|
||||
things. Manipulating the “View” part of the editor is tricky or impossible for
|
||||
certain things.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
I even <a href="https://github.com/nvim-orgmode/orgmode/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Aneovim-dependency">made a label</a> for reported issues where Neovim support for certain things
|
||||
is a blocker. I'm hoping that at least some of these will be available in future
|
||||
is a blocker. I’m hoping that at least some of these will be available in future
|
||||
Neovim releases.
|
||||
</p>
|
||||
|
||||
|
|
@ -740,9 +740,9 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
This allows getting a "desktop notification" for tasks that are within
|
||||
This allows getting a “desktop notification” for tasks that are within
|
||||
the specified threshold for schedule/deadline time. It requires some
|
||||
configuration to set up a cron job, but it's been working great for me
|
||||
configuration to set up a cron job, but it’s been working great for me
|
||||
for several months now.
|
||||
</p>
|
||||
|
||||
|
|
@ -751,16 +751,16 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
The current state of the project is very usable for me. I'm not lacking any of
|
||||
the major features, mostly because I'm not used to using them. Nevertheless,
|
||||
there are plans to add more things, and I'm getting a lot of help from the
|
||||
The current state of the project is very usable for me. I’m not lacking any of
|
||||
the major features, mostly because I’m not used to using them. Nevertheless,
|
||||
there are plans to add more things, and I’m getting a lot of help from the
|
||||
community. I want to specifically mention <a href="https://github.com/levouh">levouh</a> and <a href="https://github.com/lukas-reineke">lukas-reineke</a>, since they
|
||||
added a lot of value to the project, and I want to thank them and everyone else
|
||||
who contributed. Their help is much appreciated.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
There are few high priority tasks that I'm hoping to flush out first:
|
||||
There are few high priority tasks that I’m hoping to flush out first:
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -786,14 +786,14 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
When I started working on <a href="https://github.com/nvim-orgmode/orgmode">nvim-orgmode</a>, I didn't have a clue what I'm jumping
|
||||
into. Every day I learn about more and more Orgmode features that I wasn't even
|
||||
When I started working on <a href="https://github.com/nvim-orgmode/orgmode">nvim-orgmode</a>, I didn’t have a clue what I’m jumping
|
||||
into. Every day I learn about more and more Orgmode features that I wasn’t even
|
||||
aware existed.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
I'm certain that this project will never manage to clone the Orgmode
|
||||
functionality completely, but I'm hoping it will get close enough so everyone
|
||||
I’m certain that this project will never manage to clone the Orgmode
|
||||
functionality completely, but I’m hoping it will get close enough so everyone
|
||||
from Neovim community and Emacsers trying out Neovim will be able to use it for
|
||||
their needs.
|
||||
</p>
|
||||
|
|
@ -980,7 +980,7 @@
|
|||
<p>
|
||||
Now, if you have a line like:
|
||||
</p>
|
||||
<pre class="example" id="orgb5adb53">
|
||||
<pre class="example" id="org95c6892">
|
||||
#+cite_export: FORMAT ...
|
||||
</pre>
|
||||
<p>
|
||||
|
|
@ -1014,7 +1014,7 @@
|
|||
<p>
|
||||
This means the following forms are now all equivalent:
|
||||
</p>
|
||||
<pre class="example" id="org63e5501">
|
||||
<pre class="example" id="orgc264332">
|
||||
:tangle-mode (identity #o755)
|
||||
:tangle-mode o755
|
||||
:tangle-mode a=rx,u+w
|
||||
|
|
@ -1074,7 +1074,7 @@
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org163b65b">
|
||||
<figure id="orgadbdd38">
|
||||
<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="orgee7a6c4">
|
||||
<figure id="org87fd167">
|
||||
<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="orgc75d165">
|
||||
<figure id="org42118b3">
|
||||
<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="org9d6cbb9">
|
||||
<figure id="org873eb33">
|
||||
<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>
|
||||
|
|
@ -1615,7 +1615,7 @@
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="orgf27c9bd">
|
||||
<figure id="org87c9955">
|
||||
<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="org8628c32">
|
||||
<figure id="orgf49e93a">
|
||||
<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="orgef00c46">
|
||||
<figure id="orge52da01">
|
||||
<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="org1d62981">
|
||||
<div class="info" id="orgf6a899f">
|
||||
<p>
|
||||
<b>Ways you can contribute to the project</b>
|
||||
</p>
|
||||
|
|
@ -1958,7 +1958,7 @@
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org835ce20">
|
||||
<figure id="orgf8aa190">
|
||||
<img src="https://blog.tecosaur.net/tmio/figures/celebrate-citations.svg" alt="celebrate-citations.svg" class="org-svg">
|
||||
|
||||
</figure>
|
||||
|
|
@ -2057,17 +2057,17 @@
|
|||
<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="orgc4635b9">
|
||||
<pre class="example" id="org39f3c91">
|
||||
#+bibliography: orgcite.bib
|
||||
</pre>
|
||||
|
||||
<p>
|
||||
Once you have a bibliography source, you can start referencing to your heart's
|
||||
Once you have a bibliography source, you can start referencing to your heart’s
|
||||
content! The basic citation syntax is as follows:
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org8b523f5">
|
||||
<figure id="orgfe4afed">
|
||||
<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="org96f8ada">
|
||||
<pre class="example" id="org98e73ee">
|
||||
#+print_bibliography:
|
||||
</pre>
|
||||
|
||||
<div class="info" id="org6fb2faa">
|
||||
<div class="info" id="org49c8994">
|
||||
<style>.csl-entry{text-indent: -1.5em; margin-left: 1.5em;}</style><div class="csl-bib-body">
|
||||
</div>
|
||||
|
||||
|
|
@ -2096,13 +2096,13 @@
|
|||
<p>
|
||||
So, to summarise, all one needs to get started is:
|
||||
</p>
|
||||
<pre class="example" id="org7a46bad">
|
||||
<pre class="example" id="org3922a66">
|
||||
#+bibliography: references.bib
|
||||
[cite:@key]
|
||||
#+print_bibliography:
|
||||
</pre>
|
||||
<p>
|
||||
That's it! 🎉
|
||||
That’s it! 🎉
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -2110,13 +2110,13 @@
|
|||
<h3 id="cite-syntax"><span class="section-number-3">10.3.</span> The cite syntax</h3>
|
||||
<div class="outline-text-3" id="text-10-3">
|
||||
<p>
|
||||
Don't let the simplicity in the examples above fool you, the new syntax is quite
|
||||
capable of expressing more complex forms. Here's the <i>full</i> version of the new
|
||||
Don’t let the simplicity in the examples above fool you, the new syntax is quite
|
||||
capable of expressing more complex forms. Here’s the <i>full</i> version of the new
|
||||
cite syntax:
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org9462168">
|
||||
<figure id="orgac2460e">
|
||||
<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>
|
||||
|
|
@ -2140,7 +2140,7 @@
|
|||
|
||||
<p>
|
||||
The citation styles and variants, and recognised locators are handled by the
|
||||
citation processors. Org cite's bundled processors currently supports the
|
||||
citation processors. Org cite’s bundled processors currently supports the
|
||||
following citation styles.
|
||||
</p>
|
||||
|
||||
|
|
@ -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="org0d415b1">
|
||||
<pre class="example" id="org1e994a8">
|
||||
#+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="org725e95e">
|
||||
<pre class="example" id="org8b6d689">
|
||||
#+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="orgd359f15">
|
||||
<pre class="example" id="org3e8a3e6">
|
||||
#+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="org734efba">
|
||||
<pre class="example" id="orgd167eac">
|
||||
#+cite_export: csl ~/Downloads/apa.csl
|
||||
</pre>
|
||||
|
||||
|
|
@ -2508,21 +2508,21 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="https://www.zotero.org/">Zotero</a> is a good option, and if you're using it it's quite easy to use it with
|
||||
<a href="https://www.zotero.org/">Zotero</a> is a good option, and if you’re using it it’s quite easy to use it with
|
||||
Org Cite. Out of the box, you can tell it to export your library, or parts of it,
|
||||
to a <kbd>.bib</kbd> file and automatically keep it in sync. I'd recommend installing the
|
||||
to a <kbd>.bib</kbd> file and automatically keep it in sync. I’d recommend installing the
|
||||
<a href="https://retorque.re/zotero-better-bibtex/">Better BibTeX</a> extension though.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="orgc22f107">
|
||||
<figure id="org3ac50b6">
|
||||
<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="org3ce83fb">
|
||||
<figure id="org3ea0c81">
|
||||
<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="orgf35b296">
|
||||
<figure id="orgd277016">
|
||||
<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="orgb94c0c3">
|
||||
<pre class="example" id="org75c7bed">
|
||||
#+cite_export: csl apa.csl
|
||||
</pre>
|
||||
</div>
|
||||
|
|
@ -2564,9 +2564,9 @@
|
|||
<div class="outline-text-3" id="text-10-7">
|
||||
<p>
|
||||
Org Cite has only just been merged in the past month, and is yet to be included
|
||||
in an Org release, but we're seeing a tremendous degree of community interest.
|
||||
in an Org release, but we’re seeing a tremendous degree of community interest.
|
||||
There are <i>already</i> promising developments with third-party packages, such as
|
||||
<a href="https://github.com/bdarcus/bibtex-actions">bibtex-actions</a> and <a href="https://github.com/jkitchin/org-ref-cite">org-ref-cite</a>. I can't wait to see how the ecosystem continues
|
||||
<a href="https://github.com/bdarcus/bibtex-actions">bibtex-actions</a> and <a href="https://github.com/jkitchin/org-ref-cite">org-ref-cite</a>. I can’t wait to see how the ecosystem continues
|
||||
to develop 😃.
|
||||
</p>
|
||||
|
||||
|
|
@ -2585,13 +2585,13 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
[fn3] I'm talking about a certain company <a href="https://moneyweek.com/505757/great-frauds-in-history-robert-maxwell">created by a British Fraudster</a> that
|
||||
[fn3] I’m talking about a certain company <a href="https://moneyweek.com/505757/great-frauds-in-history-robert-maxwell">created by a British Fraudster</a> that
|
||||
has a <a href="https://www.theguardian.com/science/2017/jun/27/profitable-business-scientific-publishing-bad-for-science">40% profit margin, engages in blackmail-like practices with universities</a>,
|
||||
prompted <a href="http://thecostofknowledge.com/">19,000 researchers</a> to boycott them, <a href="https://www.the-scientist.com/the-nutshell/elsevier-published-6-fake-journals-44160">published six fake journals</a>,
|
||||
vigorously <a href="https://web.archive.org/web/20200129202353/http://legacy.earlham.edu/~peters/fos/2007/08/publishers-launch-anti-oa-lobbying.html">lobbys against Open Access</a>, <a href="https://rossmounce.co.uk/2017/02/14/elsevier-selling-access-to-open-access-again/">charged for Open Acess articles</a>
|
||||
(repeatedly), made <a href="https://www.michaeleisen.org/blog/?p=807">financial contributions to politicians who then tried to
|
||||
prevent publicly accesible reaserch</a>, and whose reference manager <a href="https://www.zotero.org/support/kb/mendeley_import#mendeley_database_encryption">encrypted
|
||||
reaserchers' <i>own</i> databases</a> "to comply with GDPR".
|
||||
reaserchers’ <i>own</i> databases</a> “to comply with GDPR”.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -2643,7 +2643,7 @@
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org07dce1d">
|
||||
<figure id="orgc91819d">
|
||||
<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="org62b4001">
|
||||
<figure id="orgb578e31">
|
||||
<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="org584a1d2">
|
||||
<figure id="org803cb9b">
|
||||
<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="org683a6fd">
|
||||
<figure id="orgfe56243">
|
||||
<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="org1df8331">
|
||||
<figure id="orgd62de58">
|
||||
<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>
|
||||
|
|
@ -2804,7 +2804,7 @@
|
|||
<h3 id="simple-elements"><span class="section-number-3">12.1.</span> Simple elements</h3>
|
||||
<div class="outline-text-3" id="text-12-1">
|
||||
<p>
|
||||
The "basic" Org elements are simply translated to their LaTeX counterparts.
|
||||
The “basic” Org elements are simply translated to their LaTeX counterparts.
|
||||
Markup like <b>bold</b>, <i>italic</i>, etc. are simply translated through
|
||||
<code>org-latex-text-markup-alist</code>.
|
||||
</p>
|
||||
|
|
@ -2812,7 +2812,7 @@
|
|||
<p>
|
||||
For those of us who dabble with equations, Org is <a href="https://orgmode.org/manual/LaTeX-fragments.html">very accomodating</a>. You can
|
||||
type (LaTeX-style) inline and display equations in exactly the same way (<kbd>\( \)</kbd>
|
||||
and <kbd>\[ \]</kbd>), and what's more, if you have a LaTeX environment statement
|
||||
and <kbd>\[ \]</kbd>), and what’s more, if you have a LaTeX environment statement
|
||||
<kbd>\begin{...}</kbd> on its own line, Org will recognise it and pass it into the
|
||||
generated LaTeX.
|
||||
</p>
|
||||
|
|
@ -2861,7 +2861,7 @@
|
|||
keyword, this works nicely in HTML too 🙂.
|
||||
</p>
|
||||
|
||||
<figure id="orgbb09719">
|
||||
<figure id="org9868867">
|
||||
<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="org3aa9563">
|
||||
<figure id="org4fcba8c">
|
||||
<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>
|
||||
|
|
@ -2932,7 +2932,7 @@
|
|||
<p>
|
||||
There are also some <a href="https://orgmode.org/manual/Images-in-LaTeX-export.html">more attributes</a> you can supply to tables. Should I want the
|
||||
table to spread out I could use <kbd>#+attr_latex: :environment tabularx</kbd> (as long as
|
||||
I've loaded the <kbd>tabularx</kbd> package) and then set the columns with <kbd>:align lX</kbd>.
|
||||
I’ve loaded the <kbd>tabularx</kbd> package) and then set the columns with <kbd>:align lX</kbd>.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -2941,7 +2941,7 @@
|
|||
<div class="outline-text-3" id="text-12-3">
|
||||
<p>
|
||||
By default, source code blocks are translated verbatim. We can do better than
|
||||
that however. We can tell Org to use <a href="https://ctan.org/pkg/listings">listings</a>, but I'd recommend going one step
|
||||
that however. We can tell Org to use <a href="https://ctan.org/pkg/listings">listings</a>, but I’d recommend going one step
|
||||
further and using <a href="https://ctan.org/pkg/minted">minted</a>. For this to work we need to perform three actions:
|
||||
Tell Org we want to use <kbd>minted</kbd> environments for source code
|
||||
Load the <kbd>minted</kbd> package by default
|
||||
|
|
@ -2974,7 +2974,7 @@
|
|||
Org has a number of <a href="https://orgmode.org/manual/Blocks.html">blocks</a> which are treated specially, like <kbd>#+begin_src</kbd> for
|
||||
source code, and <kbd>#+begin_centre</kbd> for centred text. When exporting this same
|
||||
syntax allows you to wrap Org content in any LaTeX environments (as long as it
|
||||
doesn't match one of Org's recognised environments).
|
||||
doesn’t match one of Org’s recognised environments).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -3006,7 +3006,7 @@
|
|||
</div>
|
||||
|
||||
<p>
|
||||
For larger snippets of LaTeX, there's always the export block.
|
||||
For larger snippets of LaTeX, there’s always the export block.
|
||||
</p>
|
||||
<div class="org-src-container">
|
||||
<pre class="src src-org"><span class="org-org-block-begin-line">#+begin_export latex</span>
|
||||
|
|
@ -3043,7 +3043,7 @@
|
|||
<p>
|
||||
Should you want to use a certain preset preamble, you can make use of the
|
||||
<kbd>#+latex_class</kbd> keyword. This is used to set the base preamble template used when
|
||||
generating the LaTeX. See <code>org-latex-classes</code> for what's available by default. You
|
||||
generating the LaTeX. See <code>org-latex-classes</code> for what’s available by default. You
|
||||
should see entries for:
|
||||
article
|
||||
report
|
||||
|
|
@ -3057,7 +3057,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
What's great about this is that is makes it really easy to add your own
|
||||
What’s great about this is that is makes it really easy to add your own
|
||||
templates. Each template simply takes three components:
|
||||
A name
|
||||
A preamble template
|
||||
|
|
@ -3065,7 +3065,7 @@
|
|||
</p>
|
||||
|
||||
<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
|
||||
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
|
||||
following:
|
||||
</p>
|
||||
|
|
@ -3088,22 +3088,22 @@
|
|||
|
||||
<p>
|
||||
Other improvements
|
||||
<kbd>ox-koma-letter.el</kbd> has been brought into Org's main directory from the ) <kbd>contrib/</kbd> repo <span class="underline">Bastien Guerry</span>
|
||||
<kbd>ox-koma-letter.el</kbd> has been brought into Org’s main directory from the ) <kbd>contrib/</kbd> repo <span class="underline">Bastien Guerry</span>
|
||||
Speed up publishing by using delayed hooks and temp buffers instead of finding
|
||||
files <span class="underline">Gustav Wikström</span>
|
||||
Improve generated HTML quality: prevent W3C warning and add some accessibility
|
||||
labels <span class="underline">TEC</span>
|
||||
Make the behaviour of the "goto variant" of <code>org-refile</code> (<code>org-speed-commands</code>)
|
||||
Make the behaviour of the “goto variant” of <code>org-refile</code> (<code>org-speed-commands</code>)
|
||||
less confusing <span class="underline">Marco Wahl</span>
|
||||
Backport an update to the OpenDocument schema <span class="underline">Kyle Meyer</span>
|
||||
Bugfixes
|
||||
Off by one error in texinfo menu generation <span class="underline">Nicolas Goaziou</span>
|
||||
Error in entry/conversion of non-24h times in the agenda <span class="underline">Nicolas Goaziou</span>
|
||||
Only use <code>replace-buffer-contents</code> with Emacs 27+ when saving src blocks, as the
|
||||
behaviour isn't consistent until then <span class="underline">Nicolas Goaziou</span>
|
||||
Prevent "before first headline" error in <kbd>org-clock</kbd> when clocking out <span class="underline">Nicolas Goaziou</span>
|
||||
behaviour isn’t consistent until then <span class="underline">Nicolas Goaziou</span>
|
||||
Prevent “before first headline” error in <kbd>org-clock</kbd> when clocking out <span class="underline">Nicolas Goaziou</span>
|
||||
Avoid setting the global agenda name when following a timestamp link <span class="underline">Ingo Lohmar</span>
|
||||
Don't bind <kbd><tab></kbd> in <code>org-mode-map</code> <span class="underline">Nicolas Goaziou</span>
|
||||
Don’t bind <kbd><tab></kbd> in <code>org-mode-map</code> <span class="underline">Nicolas Goaziou</span>
|
||||
Erroneous tangling of source block with <kbd>:tangle no</kbd> to a file <kbd>no</kbd> when the
|
||||
tangle command is called with a single universal argument <span class="underline">Jacopo De Simoi</span>
|
||||
Footnotes
|
||||
|
|
@ -3119,8 +3119,8 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
[fn3] I'm rather a fan of the <kbd>capitalize</kbd> option because (1) technically the
|
||||
reference to a named object is a proper noun, and (2) this means you don't have
|
||||
[fn3] I’m rather a fan of the <kbd>capitalize</kbd> option because (1) technically the
|
||||
reference to a named object is a proper noun, and (2) this means you don’t have
|
||||
to worry about references not being capitalized when appearing at the start of a
|
||||
sentence.
|
||||
</p>
|
||||
|
|
@ -3206,14 +3206,14 @@
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org7a2e29c">
|
||||
<figure id="org02ea3b5">
|
||||
<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>
|
||||
</figure>
|
||||
|
||||
<p>
|
||||
It's very slick, and Bastien built a <a href="https://github.com/bzg/woof">mailbox monitor</a> just for it — so be sure
|
||||
It’s very slick, and Bastien built a <a href="https://github.com/bzg/woof">mailbox monitor</a> just for it — so be sure
|
||||
to check it out. This should make it easier to see what needs doing. If you feel
|
||||
inclined to help out with Org check out the <i>Help requests</i> section in particular.
|
||||
</p>
|
||||
|
|
@ -3240,7 +3240,7 @@
|
|||
</p>
|
||||
|
||||
|
||||
<figure id="org00406c4">
|
||||
<figure id="org511b8ff">
|
||||
<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>
|
||||
|
|
@ -3256,12 +3256,12 @@
|
|||
<h3 id="use-org-edit"><span class="section-number-3">13.3.</span> Use <code>org-edit-special</code> (<kbd>C-c '</kbd>) with LaTeX fragments</h3>
|
||||
<div class="outline-text-3" id="text-13-3">
|
||||
<p>
|
||||
It's great how in Org you can jump into a LaTeX-mode minibuffer for LaTeX
|
||||
environments, but why leave inline LaTeX fragments out? We'll, they're now in.
|
||||
It’s great how in Org you can jump into a LaTeX-mode minibuffer for LaTeX
|
||||
environments, but why leave inline LaTeX fragments out? We’ll, they’re now in.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="orgd11dfa5">
|
||||
<figure id="org2b44cd9">
|
||||
<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>
|
||||
|
|
@ -3272,21 +3272,21 @@
|
|||
<h3 id="control-heading-display"><span class="section-number-3">13.4.</span> Control heading display on startup</h3>
|
||||
<div class="outline-text-3" id="text-13-4">
|
||||
<p>
|
||||
<kbd>org-num-mode</kbd> is great for when you're keeping an eye on section numbers, but
|
||||
it's not fun to find yourself enabling it every time you open a file where you
|
||||
<kbd>org-num-mode</kbd> is great for when you’re keeping an eye on section numbers, but
|
||||
it’s not fun to find yourself enabling it every time you open a file where you
|
||||
want it. With the new option <kbd>#+startup: num</kbd> by Bastien, you can set and forget
|
||||
at last.
|
||||
</p>
|
||||
|
||||
|
||||
<figure id="org60c1d2a">
|
||||
<figure id="org2674cb9">
|
||||
<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>
|
||||
</figure>
|
||||
|
||||
<p>
|
||||
Should you want to set the number of levels you see on opening a file, there's
|
||||
Should you want to set the number of levels you see on opening a file, there’s
|
||||
now an option for that too. Gustav Wikström has added <i>another</i> new option
|
||||
<kbd>#+startup: show<n>levels</kbd> (where <kbd><n></kbd> is between 2 and 5, inclusive).
|
||||
<i>NB: This is part of the upcoming 9.5 release</i>
|
||||
|
|
@ -3297,8 +3297,8 @@
|
|||
<h3 id="set-permissions-tangled"><span class="section-number-3">13.5.</span> Set permissions of tangled files</h3>
|
||||
<div class="outline-text-3" id="text-13-5">
|
||||
<p>
|
||||
Are you particular about your file permissions? If so you'll likely like John
|
||||
Herrlin's new source block header argument <kbd>:file-mode</kbd> pertinent. The easiest way
|
||||
Are you particular about your file permissions? If so you’ll likely like John
|
||||
Herrlin’s new source block header argument <kbd>:file-mode</kbd> pertinent. The easiest way
|
||||
to set a permission is with an <a href="https://docs.nersc.gov/filesystems/unix-file-permissions/">octal value</a>, like so:
|
||||
</p>
|
||||
<div class="org-src-container">
|
||||
|
|
@ -3314,15 +3314,15 @@
|
|||
<h3 id="collection-improvements-source"><span class="section-number-3">13.6.</span> A collection of improvements to source block header arguments</h3>
|
||||
<div class="outline-text-3" id="text-13-6">
|
||||
<p>
|
||||
These's been a whole set of these, so I'll just list them off.
|
||||
These’s been a whole set of these, so I’ll just list them off.
|
||||
python, improved <kbd>:return</kbd> Now works with sessions and the <kbd>:epilogue</kbd>
|
||||
argument (Jack Kamm)
|
||||
Java, new argument <kbd>:cmdargs</kbd> Add some command line arguments to be passed to
|
||||
<code>java</code> (Jarmo Hurri)
|
||||
C/C++, non-system headers with <kbd>:includes</kbd> values that don't start with <kbd><</kbd>
|
||||
C/C++, non-system headers with <kbd>:includes</kbd> values that don’t start with <kbd><</kbd>
|
||||
will now be formatted as double-quoted <code class="src src-C"><span class="org-preprocessor">#include</span></code> statements (Brandon
|
||||
Guttersohn)
|
||||
Screen, new argument <kbd>:screenrc</kbd> For those of you who still haven't moved to
|
||||
Screen, new argument <kbd>:screenrc</kbd> For those of you who still haven’t moved to
|
||||
<kbd>tmux</kbd> (Kenneth D. Mankoff)
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -3344,7 +3344,7 @@
|
|||
structures, Org also has the advantage of not having <a href="https://github.com/commonmark/commonmark-spec/wiki/markdown-flavors">40 functionally distinct
|
||||
specifications</a>. There is only one Org. <br>
|
||||
NB: If you attempt to be pedantic you may say that there are multiple Orgs
|
||||
because, for example, GitHub uses <a href="https://github.com/wallyqs/org-ruby">org-ruby</a>. However, that's just an incomplete
|
||||
because, for example, GitHub uses <a href="https://github.com/wallyqs/org-ruby">org-ruby</a>. However, that’s just an incomplete
|
||||
implementation — not a <a href="https://orgmode.org/worg/dev/org-syntax.html">specification</a>.
|
||||
</p>
|
||||
|
||||
|
|
@ -3355,7 +3355,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
[fn3] There is <a href="https://code.orgmode.org/bzg/org-mode/src/master/etc/ORG-NEWS">ORG-NEWS</a>, but do you <i>really</i> check that? Besides, it doesn't even
|
||||
[fn3] There is <a href="https://code.orgmode.org/bzg/org-mode/src/master/etc/ORG-NEWS">ORG-NEWS</a>, but do you <i>really</i> check that? Besides, it doesn’t even
|
||||
have pictures.
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
Loading…
Reference in New Issue