Re: Where is Elisp evaluation documented in the Org Manual?

> On Sep 30, 2022, at 11:07, Max Nikulin wrote: > > On 30/09/2022 21:15, Perry Smith wrote: > >> I discovered that it can be done like {{{kbd(M-TAB)}}} >> Fascinating!!! And I bet expr in the form of {{{ expr }}} could be any >> Elisp expression. Cool! &

Where is Elisp evaluation documented in the Org Manual?

I wanted to format a key binding in Org mode and, of course, I wanted to do it properly so I started surfing around and then hit upon the idea of just looking at the source of the Org manual for examples. I discovered that it can be done like {{{kbd(M-TAB)}}} Fascinating!!! And I bet expr in

#+ candidates

The manual says I can type #+ and then hit M-tab to get the list of completions. In my case, flyspell-mode had stolen that key binding so I disabled flyspell-mode. There are 100 #+ candidates. Is there a nice place that lists them and documents each one? So far, I’ve yet to find one. It is

Re: Org mode "style sheet" for software documentation

> On Sep 9, 2022, at 00:09, Ihor Radchenko wrote: > > Perry Smith writes: > >> So… it seems I didn’t the two BORDER characters do not need to match. So >> I’m off trying to figure out a way to create more emphasis MARKERS. In the >> old days, we had

Re: Org mode "style sheet" for software documentation

> On Sep 8, 2022, at 11:20, Perry Smith wrote: > > I don’t understand this page: > https://orgmode.org/worg/dev/org-syntax.html#Emphasis_Markers > <https://orgmode.org/worg/dev/org-syntax.html#Emphasis_Markers> > > In particular, the BORDER BODY BORDER part. No

Org mode "style sheet" for software documentation

I don’t understand this page: https://orgmode.org/worg/dev/org-syntax.html#Emphasis_Markers In particular, the BORDER BODY BORDER part. Note that this is the CONTENT which is already between MARKERS. What I *think* I want is the

Simple but repetitive http links

I'm new to Org mode. I found this page https://orgmode.org/manual/Link-Abbreviations.html about Link Abbreviations but I wanted to report my confusion. I added: #+LINK: rails https://rubyonrails.org to my org file and then I wrote [[rails][Rails]] and when I clicked the text, it asked me if I

Footnote 60 in Org Manual

The text has “For example, to specify a date December 12, 2005 …” and then all of the examples use 12 and 1 as if the intention was “to specify a date December 1, 2005”. I doubt if you want to use December 12 because the specification would be 12 12 2005 but it would be hard to tell the user

Org.texi (the Org Manual) in ePub format

I joined this list about a month ago to ask how I could get the manual in ePub format but I also started searching. Long story short, I joined the TexInfo Help mailing list and submitted a question[1] (which also references two other threads if you are interested). The net net net is you may