[BUG] Org export fails on $k$-ary

Dear all, I would expect this to be exported to HTML and LaTeX correctly: "A $k$-ary function has $k$ arguments" In 12.5.1 LaTeX fragments, this use of a hyphen is documented: "To avoid conflicts with currency specifications, single ‘$’ characters are only recognized as math delimiters if the

Re: Suggestions for Text-To-Speech (TTS) from Org sources?

On 2023-09-28, Jude DaShiell wrote: > espeak-ng likes to have speechdispatcher on a system Does this improve the quality of the generated speech? > and festival likes to have language-specific voices on it to use. Indeed. Which one(s) do you recommend? I tried voice_cmu_us_slt_arctic_hts and

Re: Suggestions for Text-To-Speech (TTS) from Org sources?

Dear all, some time ago I asked for suggestions concerning Text-To-Speech (TTS) from Org sources. Thank you to everyone who provided suggestions! In case you are interested, you can listen to sample results at [1]. Briefly, Emacspeak, espeak-ng, and festival are not good enough for my

Re: Suggestions for Text-To-Speech (TTS) from Org sources?

ely from a cdrom" craze--which > still is very useful in many ways--suggest you give Knoppix & Adriane a look > > On Mon, Sep 11, 2023 at 4:02 AM Christian Thäter wrote: > >> On Sun, 10 Sep 2023 16:39:26 +0200 >> Jens Lechtenboerger wrote: >> >> > On 2023-

Re: Suggestions for Text-To-Speech (TTS) from Org sources?

On 2023-09-10, Christian Thäter wrote: > On Sun, 10 Sep 2023 16:39:26 +0200 > Jens Lechtenboerger wrote: > >> On 2023-09-10, Ihor Radchenko wrote: >> >> > Jens Lechtenboerger writes: >> > >> >> does someone here produce audio via Text-To

Re: Suggestions for Text-To-Speech (TTS) from Org sources?

On 2023-09-10, Ihor Radchenko wrote: > Jens Lechtenboerger writes: > >> does someone here produce audio via Text-To-Speech (TTS) from Org >> sources? I plan to do that in the context of emacs-reveal to >> generate voice-over for reveal.js presentations, with open questi

Re: Suggestions for Text-To-Speech (TTS) from Org sources?

On 2023-09-09, briangpowell wrote: > I've turned OrgMode files into audio desktops > > It was pretty simple > > Just find the code that reveals what an icon is when you hover over it & > pipe it to some text-to-speech engine & then on to usual routes Thank you for the reply. In my case

Suggestions for Text-To-Speech (TTS) from Org sources?

Dear all, does someone here produce audio via Text-To-Speech (TTS) from Org sources? I plan to do that in the context of emacs-reveal to generate voice-over for reveal.js presentations, with open questions [1] concerning my initial, experimental approach. Currently, I like the default model of

Re: [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link?

On 2023-09-01, Ihor Radchenko wrote: > In theory, we might change the parser to treat anything like foo:bar or > or [[foo:bar]] as a link with "foo" protocol and "bar" URI. > And introduce [[::fig:something]] to allow explicit internal links. > But, despite simplifying the parser, it will

Re: How to tell `org-html-link' to create a link with some HTML class?

On 2023-06-20, Marcin Borkowski wrote: > Dear Orgers, > > as I mentioned some time ago, I'm writing a custom exporter (actually, > a very thin wrapper around the HTML exporter). I'd like `org-html-link' > to add some class to the links it generates. Is that possible? Dear Marcin, yes, that’s

Re: Unicode problem with export of literal contents

On 2023-02-20, Bruno Barbier wrote: > Jens Lechtenboerger writes: > >> On 2023-02-20, Bruno Barbier wrote: >> >> However, if I use insert-file-contents-literally with a unicode >> file, I do *not* have to set the coding-system-for-write. This just >&g

Re: Unicode problem with export of literal contents

On 2023-02-20, Bruno Barbier wrote: > If you're always using utf-8, here is a way to force it so that > secure-hash can compute the hash. This should work: > >(with-temp-buffer > (let ((coding-system-for-write 'utf-8)) > (insert "Lechtenb\303\266rger") > (secure-hash

Re: Unicode problem with export of literal contents

On 2023-02-17, Ihor Radchenko wrote: > Jens Lechtenboerger writes: >> Also, when I call secure-hash on the literal buffer-string, no >> problem arises. > > Org is calling secure-hash on buffer. Calling on buffer-string would > require unnecessary memory allocation to c

Re: Unicode problem with export of literal contents

On 2023-02-17, Bruno Barbier wrote: > Here is a way to reproduce that doesn't use org, in case it might help > to manully fix your encoding issue: > >(with-temp-buffer > (insert "Lechtenb\303\266rger") > (let ((buffer-file-name (make-temp-file "mailtest"))) >

Re: Unicode problem with export of literal contents

On 2023-02-17, Ihor Radchenko wrote: > Jens Lechtenboerger writes: > >> With Org 9.6.1 from Emacs master, I get the following warning, and I >> am asked to select a coding system: >> >>> These default coding systems were tried to encode the following >>

Re: Unicode problem with export of literal contents

Hi Bruno, On 2023-02-17, Bruno Barbier wrote: > Hi Jens, > > Jens Lechtenboerger writes: > >> ... >> Note that I insert contents literally because I do not want >> ‘find-file-hook’, automatic uncompression, etc. (which are avoided >> according to the doc stri

Unicode problem with export of literal contents

Hi there, consider this piece code, where unicode-file.org contains umlauts (say, just the word “Lechtenbörger”): (org-export-string-as (with-temp-buffer (insert-file-contents-literally "unicode-file.org") (buffer-string)) 'html t) With Org 9.6.1 from Emacs master, I get the following

Re: Syntax question: What is BORDER in 4.17. Text Markup?

On 2022-12-07, Timothy wrote: > Hi Jens, > >> Actually, what about this? Get rid of both, BORDER and BODY, and >> specify CONTENTS as follows: >> “Either a string (when MARKER represents code or verbatim) or a >> series of objects from the standard set, not spanning more than >> three lines. In

Re: Syntax question: What is BORDER in 4.17. Text Markup?

On 2022-12-07, Jens Lechtenboerger wrote: > On 2022-12-07, Max Nikulin wrote: > >> On 07/12/2022 01:28, Jens Lechtenboerger wrote: >>> Hi there, >>> the syntax for Text Markup such as *bold* at [1] specifies >>> PRE MARKER CONTENTS MARKER POST

Re: Syntax question: What is BORDER in 4.17. Text Markup?

On 2022-12-07, Max Nikulin wrote: > On 07/12/2022 01:28, Jens Lechtenboerger wrote: >> Hi there, >> the syntax for Text Markup such as *bold* at [1] specifies >> PRE MARKER CONTENTS MARKER POST with >> CONTENTS as BORDER BODY BORDER and >> BORDER as “Any n

Syntax question: What is BORDER in 4.17. Text Markup?

Hi there, the syntax for Text Markup such as *bold* at [1] specifies PRE MARKER CONTENTS MARKER POST with CONTENTS as BORDER BODY BORDER and BORDER as “Any non-whitespace character.” What is the role of BORDER here? Does it really exist? What is BORDER if CONTENTS should be a single character,

Re: index for HTML export

On 2022-07-14, Fraga, Eric wrote: > On Thursday, 14 Jul 2022 at 08:13, Jens Lechtenboerger wrote: >> (list "index-terms" > > [...] > >> :preparation-function 'oer-reveal--add-advice-link >> :completion-function 'oer-reveal--remove-adv

Re: index for HTML export

On 2022-07-13, Fraga, Eric wrote: > Publishing works, in the sense that my org file is exported to HTML just > fine. An index file is created but is not populated with any index > links. What am I missing? The info page is less than helpful > unfortunately. Are index lines, e.g. > > #+index:

Re: Publish to HTML and LaTeX/PDF with cross-file links?

On 2022-06-16, at 09:55, Tim Cross wrote: > Jens Lechtenboerger writes: > >> [...] >> More precisely: For HTML export, a link like >> [[file:foo.org::#custom-id][elsewhere]] turns into a hyperlink to >> “foo.html#custom-id”, which is what I want. >&

Publish to HTML and LaTeX/PDF with cross-file links?

Hi all, I publish OER (https://oer.gitlab.io/) from Org sources and wonder about links to local files as documented at [1]. That page only talks about HTML export. How can I achieve similar behavior for LaTeX/PDF export? More precisely: For HTML export, a link like

Re: Cannot clone org-mode's git repository

On 2021-10-03, Colin Baxter wrote: > Hello, > > I get a strange error when I try to clone org-mode: > > redknight@jetstar:~/git$ git clone > https://git.savannah.gnu.org/git/emacs/org-mode.git > Cloning into 'org-mode'... > fatal: unable to access >

Re: modify citation links in a derived HTML backend

On 2021-07-03, Matt Price wrote: > I've added some comments in the issue you linked to, but in the meantime > I've also come up with what seems to be at least a semi-viable hack for > adding native CSL citation support to org-re-reveal. It involves creating > two new variables and then

Re: modify citation links in a derived HTML backend

On 2021-07-02, Matt Price wrote: > Hi, > > (cc:ing Jens L. in case this is relevant for his dev work on org-re-reveal). Hi Matt, just a quick reply: Yes, that is certainly relevant for me, but I do not have the time to investigate this at the moment. Note that I use references with org-ref and

Re: ox-html Incorrectly (?) Puts HTML Into the `` Tag

On 2021-04-20, Tim Visher wrote: > I guess regardless it sounds like if I were to go to the trouble of making > a patch for this it would be good to make sure that it was behind an option > and probably defaulting to the current HEAD behavior of including the ASCII > markup with an option to

Re: ox-html Incorrectly (?) Puts HTML Into the `` Tag

On 2021-04-19, Kyle Meyer wrote: > Tim Visher writes: > >> Unfortunately, the title now is essentially the exact text of the org >> heading, which is awkward in terms of readability for a general audience >> (and probably for SEO etc.). I know I said in my original message that I >> think

Re: [PATCH] tweaks to ox-html style

On 2021-02-13, Timothy wrote: > Jens Lechtenboerger writes: > >> On 2021-02-12, Jens Lechtenboerger wrote: >> >>> I do not know why the CDATA lines exist. I don’t see a reason to >>> keep them (patch 0001), but that might be a lack of understanding on >

Re: [PATCH] tweaks to ox-html style

On 2021-02-12, Jens Lechtenboerger wrote: > I do not know why the CDATA lines exist. I don’t see a reason to > keep them (patch 0001), but that might be a lack of understanding on > my part. OK, that is probably for XHTML, where < and & are only allowed inside CDATA sections.

Re: [PATCH] tweaks to ox-html style

On 2021-02-12, Kyle Meyer wrote: > TEC writes: > >> Hi All, >> >> This is just some tweaks to the styling in ox-html that I think may >> appeal (and prevent ridiculously long lines on non-small displays, which >> are an issue for legibility). >> >> I also took the opportunity to remove the

Re: [PATCH] Enhance org-html--build-meta-info

On 2021-01-14, TEC wrote: > TEC writes: > >>> Sorry, I still see the flycheck warning and "amp;" for "&". >> Maybe I accidently sent you the old patches? I'll check tomorrow. > > Hah, I check and guess what I see? The changes were unstaged . > > Sorry about that, here's an actual revision.

Re: [PATCH] Enhance org-html--build-meta-info

On 2021-01-10, TEC wrote: > Jens Lechtenboerger writes: > >> On line 1432 I get this suggestion from flycheck: >> There should be two spaces after a period (emacs-lisp-checkdoc) >> >> More importantly, I just realized that for author information, >> org-html-

Re: [PATCH] Enhance org-html--build-meta-info

On 2021-01-04, TEC wrote: > Jens Lechtenboerger writes: > >> org-html--build-meta-entry and org-html--build-meta-info include some long >> lines. > > Hehe. We've had a lot of back-and-forth haven't we. > At least it feels like it's coming to a close now. On line 1432

Re: [PATCH] Enhance org-html--build-meta-info

On 2021-01-03, TEC wrote: > Jens Lechtenboerger writes: > >> The doc strings of org-html-meta-tags and org-html-meta-tags-default >> need to be updated, they still mention author and title. > > Ah, yep. Fixed. > >> Also, please try checkdoc ;) > > Ahh

Re: [PATCH] Enhance org-html--build-meta-info

On 2021-01-03, TEC wrote: > After considering the information passed to a meta info generation > function, I'm now in agreement with you that just passing `info' is the > most sensible way forward. Hi Timothy, great, thanks :-) > Attached is a (final?) set of patches, which is as described.

Re: [PATCH] Enhance org-html--build-meta-info

On 2020-12-20, TEC wrote: > Jens Lechtenboerger writes: > >>> For people who want to customise this to add metadata, the page title is >>> something they're probably interested in. >> >> What metadata would you derive from the title? > > In my earlier

Re: [PATCH] Enhance org-html--build-meta-info

On 2020-12-16, TEC wrote: > Jens Lechtenboerger writes: >>> Maybe it should be applied to the rest (in ~org-html--build-meta-info~)? >>> I'm not sure. >> >> I’m not sure either. Maybe people expect their typed characters, >> maybe not. This might c

Re: [PATCH] Enhance org-html--build-meta-info

Hello everyone, On 2020-12-15, TEC wrote: > Jens Lechtenboerger writes: > >> [title export being dodgy, how about treating like author?] > > Yep, ~org-element-interpret-data~ is necessary. I found that wrapping it > in ~org-html-plain-text~ seems better again though, as

Re: [PATCH] Enhance org-html--build-meta-info

Hi everybody, On 2020-12-14, Bastien wrote: > Hi Timothy, > > TEC writes: > >> Thanks for testing this :) I haven't forgotten about this. > > Let's wait for Jens feedback on this patch, since he took care of > testing it so far. I exported this: #+begin_src org ,#+TITLE: A title with *bold*

Re: Reply-All noise

On 2020-10-09, to...@tuxteam.de wrote: > On Fri, Oct 09, 2020 at 10:10:41PM +0200, to...@tuxteam.de wrote: >> On Fri, Oct 09, 2020 at 09:24:34PM +0200, c.bu...@posteo.jp wrote: >> > Hi, > > [...] > >> There is no clear-cut answer to that [...] > > You might also want to experiment with setting

Re: [PATCH] Enhance org-html--build-meta-info

On 2020-09-28, TEC wrote: > Jens Lechtenboerger writes: > >> On 2020-09-28, TEC wrote: >> >>> Jens Lechtenboerger writes: >>>> Also, in org-html--build-meta-info you call >>>> org-html-encode-plain-text with two arguments, but it just accep

Re: [PATCH] Enhance org-html--build-meta-info

On 2020-09-28, TEC wrote: > Jens Lechtenboerger writes: >> Also, in org-html--build-meta-info you call >> org-html-encode-plain-text with two arguments, but it just accepts >> one. > > ? No I don't. Your patch contains this: + (let* ((title (org-html-encode-plain-

Re: [PATCH] Enhance org-html--build-meta-info

On 2020-09-26, TEC wrote: > @Maintainers I think this is ready for a review. > > Jens Lechtenboerger writes: > >> My suggestion would be to go with the handling of description in all >> cases, including the title. > > Currently the only element handled different

Re: [PATCH] Enhance org-html--build-meta-info

On 2020-09-18, TEC wrote: > Jens Lechtenboerger writes: > [...] > I was not aware of org-element-interpret-data, and I can't say I can > really tell what it does. If you'd care to elaborate that would be > helpful. Hi Timothy, I don’t know why that is used. For this test cas

Re: [PATCH] Enhance org-html--build-meta-info

On 2020-09-17, TEC wrote: > Hi All, > > This just replaces the current `org-html--build-meta-info' with a > cleaner, more extensible (I also added a new variable) > version. Please give it a look and let me know what you think! Hi Timothy, yes, I agree that org-html--build-meta-info needs work,

Re: pcase failure with Emacs 24 (was Emacs version for Org 9.4?)

On 2020-09-15, Kyle Meyer wrote: > It is pretty tricky to debug, but the failure starts with 4a27b67fd > (org-element: Fix property drawers parsing, 2020-04-22). As far as I > can see, the pattern introduced there is perfectly valid and should be > compatible with Emacs 24. I'd _guess_ this is

Re: Emacs version for Org 9.4?

On 2020-09-15, Jeremie Juste wrote: > Hello Jens, > > I'm afraid I cannot test your issue. I don't have the ability to switch > emacs version yet. > > What I can tell you is that org-9.4 is working fine on GNU Emacs 27.1, > and on Emacs 28.0.50. Hello Jeremie, thanks for your reply. Yes, I’m

Emacs version for Org 9.4?

Hi there, if I open an Org file on “GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.11) of 2017-09-12 on hullmann, modified by Debian” I get this error (which I don’t know how to debug): Eager macro-expansion failure: (wrong-type-argument listp :pcase--succeed) Recipe: touch empty.org

Re: ox-* vs org-* naming convention?

On 2020-06-07, Diego Zamboni wrote: > Hi, > > I am working on submitting a new set of exporters I've been working on > (https://gitlab.com/zzamboni/ox-leanpub) to MELPA, and I received > feedback [1] about the discrepancy between the package names > (ox-leanpub-*) and the functions they define

Re: emacs + org-mode in virtual machine/docker/...

On 2020-05-23, Olivier Berger wrote: > Hi. > > This looks quite similar to my approach to producing course material, > which is documented here : https://olberger.gitlab.io/org-teaching > including the use of Docker (see > https://gitlab.com/olberger/docker-org-teaching-export/ ) Indeed, the

Re: emacs + org-mode in virtual machine/docker/...

On 2020-05-21, John Kitchin wrote: > What do you do with this image? I would be happy to continue this off-list > if it seems better. I generate self-study HTML presentations with audio as OER based on reveal.js. See there for a course about to start in two weeks: https://oer.gitlab.io/OS/

Re: emacs + org-mode in virtual machine/docker/...

On 2020-05-21, John Kitchin wrote: > Has anyone had any success in creating or using any kind of virtual machine > that can work across platforms to run emacs+org-mode? I maintain Docker images, emacs-reveal includes org-ref. It is large, though:

Re: ox-html: Bug or feature for export of title and meta information?

Hi there! On 2020-02-17, at 10:47, Nicolas Goaziou wrote: > Jens Lechtenboerger writes: >> Which “non exportable objects” can be skipped by that function (as >> mentioned in a comment in org-html--build-meta-info)? Should they also >> be skipped for description o

Re: ox-html: Bug or feature for export of title and meta information?

Hi there! On 2020-02-15, at 15:02, Nicolas Goaziou wrote: > Jens Lechtenboerger writes: > >> the W3C Markup Validator [1] disagrees with this output from >> ox-html (which I reduced to the essential parts): > > OK. I was talking about the Org syntax. I misread your ini

Re: ox-html: Bug or feature for export of title and meta information?

On 2020-02-14, at 20:31, Nicolas Goaziou wrote: > Hello, > > Jens Lechtenboerger writes: > >> 1. Export to HTML when the title contains markup, say this one: >> >> #+TITLE: This does *not* work > > What does not work? > >> The HTML title element con

Re: ox-html: add option to restore old src block behaviour?

On 2020-02-11, at 16:40, Bastien wrote: > Matt Price writes: > >> However, at least one very common syntax highlighter, https:// >> highlinghtjs.org, expects just a single tag, as do other >> common CSS frameworks. These often leave odd borders or background >> color disruptions which somewhat

Re: ox-html: Bug or feature for export of title and meta information?

On 2020-02-11, at 09:16, Bastien wrote: > Hi Jens, > > it is difficult to justify existing code, it is easier to answer to > bug reports. If you think there is a bug in this aread, can you tell > what it is? Hi Bastien, many thanks for following up on this! I see two or more bugs: 1. Export

Re: [PATCH] Derive non-default start value for ordered list

On 2019-12-02, at 08:23, Nicolas Goaziou wrote: > Jens Lechtenboerger writes: > >> [...] >> What do you think about the attached patch that allows to omit the >> @-syntax? Controlled by the new variable >> org-list-use-first-bullet-as-non-standard-counter, the c

Re: [PATCH] Derive non-default start value for ordered list

On 2019-12-01, at 14:13, Samuel Wales wrote: > i think it might be partlly a question of whether these numbers are > fixed things that refer to fixed items [like referring to sections in > a law that is not in the document] vs. being used to continue lists. > > they are both legitimate uses. in

[PATCH] Derive non-default start value for ordered list

rom 2eea43d84687259633f847bd17883e5fe578b6bc Mon Sep 17 00:00:00 2001 From: Jens Lechtenboerger Date: Sun, 1 Dec 2019 21:17:43 +0100 Subject: [PATCH] Use bullet as non-standard counter * lisp/org-list.el: New variable org-list-use-first-bullet-as-non-standard-counter and new function org-list-struct-maybe-

Re: [O] [PATCH] ox-html: add option to restore old src block behaviour?

On 2019-10-13, at 09:30, Nicolas Goaziou wrote: > Jens Lechtenboerger writes: > >> Subject: [PATCH] ox-html: Control wrapping of source lines >> >> * lisp/ox-html.el (org-html-format-code, org-html-do-format-code): >> Use new export option :html-wrap-src-lines wi

Re: [O] [PATCH] ox-html: add option to restore old src block behaviour?

On 2019-10-08, at 11:31, Nicolas Goaziou wrote: > Jens Lechtenboerger writes: > >> The attached patch adds a new variable org-html-wrap-src-lines to >> control whether code tags should be added or not. > > Thank you. > > However, the patch is not right. Exporters do

[O] ox-html: Bug or feature for export of title and meta information?

Hi there, I wonder about the treatment of different pieces of HTML header information in org-html--build-meta-info: Contents for the title element are computed by org-export-data. This interprets Org markup such as italics or hyperlinks although title elements are not allowed to contain the

[O] [PATCH] ox-html: add option to restore old src block behaviour?

On 2019-09-19, Matt Price wrote: > Over the summer, commit ded3d27b1468b878197e5fe55a70c5e13350ea27 > by Nik Clayton was merged to master. It's a one-line change that > adds new ~~ tags around each lin of code in html export of > source blocks. It's useful because it allows individual lines to >

Re: [O] Two bibliography slides using org-reveal

Johannes Brauer writes: > GET > file:///Users/jb/Downloads/org-re-reveal-ref-master/reveal.js/lib/js/head.min.js > net::ERR_FILE_NOT_FOUND README.html:173 > > Is this a relevant message? Hi Johannes, that message appears for newer versions of reveal.js (but does not hurt). You can avoid

Re: [O] Two bibliography slides using org-reveal

Johannes Brauer writes: > I downloaded [1] but when I try M-x load-library followed by > org-re-reveal-ref I get > "Cannot open load file: No such file or directory, org-re-reveal" > although I’ve org-ref installed. What is going wrong? Hi Johannes, you also need to install org-re-reveal,

Re: [O] Two bibliography slides using org-reveal

I created org-re-reveal-ref [1] based on my fork org-re-reveal for bibliographies with org-ref. I only use it for export to reveal.js and PDF, but HTML seems fine as well. That package is part of emacs-reveal [2]. Best wishes Jens [1] https://gitlab.com/oer/org-re-reveal-ref [2]

Re: [O] [RFC] Fixing link encoding once and for all

On 2019-03-01, Nicolas Goaziou wrote: > Jens Lechtenboerger writes: > >> On 2019-03-01, Nicolas Goaziou wrote: >> >>> 3. There will be some backward compatibility issues. We can add >>>a checker in Org Lint to catch most of those. For example, we could &g

Re: [O] [RFC] Fixing link encoding once and for all

Hi there, I like this proposal. On 2019-03-01, Nicolas Goaziou wrote: > 3. There will be some backward compatibility issues. We can add >a checker in Org Lint to catch most of those. For example, we could >look at URI where every percent is followed only by 25, 5B, and 5D. I do not

Re: [O] [RFC] Fixing link encoding once and for all

On 2019-02-27, Nicolas Goaziou wrote: > Hello, > > Jens Lechtenboerger writes: > >> When exporting the following link to LaTeX, the decoding fails. >> >> --8<---cut here---start->8--- >> [[https://en.wikipedia.org/wi

Re: [O] [RFC] Fixing link encoding once and for all

On 2019-02-24, Nicolas Goaziou wrote: > Recently[1], issues about link escaping have resurfaced. I'd like to > solve this once and for all. Good morning, I updated to Org mode version 9.2.1 (9.2.1-33-g029cf6-elpa @ /home/user/.emacs.d/elpa/org-20190225/). When exporting the following link to

Re: [O] Key bindings for Org export back-ends?

On 2019-02-08, at 22:03, Jens Lechtenboerger wrote: > On 2019-02-08, at 10:54, Kaushal Modi wrote: > >> On Fri, Feb 8, 2019 at 10:48 AM Thomas S. Dye wrote: >> >>> One place for the list of key bindings might be here: >>> https://orgmode.org/worg/exporters

Re: [O] Key bindings for Org export back-ends?

On 2019-02-08, at 10:54, Kaushal Modi wrote: > On Fri, Feb 8, 2019 at 10:48 AM Thomas S. Dye wrote: > >> One place for the list of key bindings might be here: >> https://orgmode.org/worg/exporters/index.html >> > > That's a great idea! How about creating a single Org table with columns > like

Re: [O] Key bindings for Org export back-ends?

On 2019-02-08, at 06:51, Kaushal Modi wrote: > On Fri, Feb 8, 2019, 3:28 AM Jens Lechtenboerger wrote: > >> - org-reveal [3]: R >> - org-re-reveal [4]: r (conflict with RSS) > > I see that org-re-reveal is based off org-reveal. So do you see a use case > where peop

Re: [O] Key bindings for Org export back-ends?

On 2019-02-08, at 06:51, Kaushal Modi wrote: > On Fri, Feb 8, 2019, 3:28 AM Jens Lechtenboerger wrote: > >> - org-reveal [3]: R >> - org-re-reveal [4]: r (conflict with RSS) > > I see that org-re-reveal is based off org-reveal. So do you see a use case > where peop

[O] Key bindings for Org export back-ends?

Hi there, I need to assign a key to an Org export back-end. My first attempt ended in a conflict, so I’d like to collect a (full?) list. Built-in - iCalendar: c - HTML: h - Texinfo: i - LaTeX and Beamer: l - Man: M - Markdown: m - ODT: o - Org: O - Publish: P - Plain text: t Contrib

Re: [O] Bug: LaTeX export of table with caption broken

On 2019-01-19, at 16:06, Nicolas Goaziou wrote: > Jens Lechtenboerger writes: > >> when exporting a table with caption to LaTeX on the master branch, >> invalid code is generated. > > Fixed. Thank you. Wow, that was lightning fast. Many thanks! Jens

[O] Bug: LaTeX export of table with caption broken

Hi there, when exporting a table with caption to LaTeX on the master branch, invalid code is generated. Example Org file: #+CAPTION: Some text | Col1 | Col2 | |--+--| | foo | bar | The resulting tex file contains this, without table environment, which is necessary for the use of

[O] License information for figures in Org mode?

Hi there, I’ve written code based on Org mode to generate Open Educational Resources (OER, learning material under free licenses, typically variants of Creative Commons), which include figures with proper license attribution (source, author, license) [1]. If you ever wanted to publish OER

[O] Quoting of macros with eval

Hi there, given a macro like #+MACRO: foo (eval (message "%s" $1)) I need to call {{{foo("text")}}} with Org mode 9.1.14-9-g131531-elpa. On the master branch, that call will include the quotation marks as part of the string, so I need to call {{{foo(text)}}} (documented in the manual, but I

Re: [O] [PATCH] ox.el: Define subtitle macro

Hi there, On 2017-11-21, Nicolas Goaziou wrote: > For the record, I implemented a "keyword" macro (master branch). That has been in master for over a year now. Are there plans for inclusion in a release? (Or did I overlook that?) Best wishes Jens

[O] PATCH: Extract HTML attributes from link if present

789 Mon Sep 17 00:00:00 2001 From: Jens Lechtenboerger Date: Sat, 8 Dec 2018 16:44:06 +0100 Subject: [PATCH] ox-html.el: Export attributes specified with :attr_html for links * lisp/ox-html.el (org-html-link): Export :attr_html from link --- lisp/ox-html.el | 30 ++

Re: [O] PATCH: Allow class attribute for headline in HTML export

Hello! On 2018-12-08, at 12:46, Nicolas Goaziou wrote: > Jens Lechtenboerger writes: > >> Function org-reveal-headline calls org-html-headline to generate >> h-elements. Of course, I could parse the generated HTML in >> ox-reveal and add a class attribute based on org

Re: [O] PATCH: Allow class attribute for headline in HTML export

Hello, On 2018-12-04, Nicolas Goaziou wrote: > Jens Lechtenboerger writes: > >> I plan to use that for a table-of-contents plugin [1] of reveal.js, >> which looks for class attributes inside h-elements to exclude them >> selectively. > > Then I suggest to sub

Re: [O] PATCH: Allow class attribute for headline in HTML export

On 2018-12-02, Nicolas Goaziou wrote: > Jens Lechtenboerger writes: > >> From 068fb45f5276d61e86271988efbcf6c29e08c411 Mon Sep 17 00:00:00 2001 >> From: Jens Lechtenboerger >> Date: Sun, 2 Dec 2018 20:25:38 +0100 >> Subject: [PATCH] ox-html.el: New property

Re: [O] PATCH: Allow class attribute for headline in HTML export

On 2018-12-02, at 19:25, Jens Lechtenboerger wrote: > Dear all, > > the attached patch allows to add a class attribute to headline > elements in HTML export. Is that acceptable for inclusion? In that patch, "when" should have been "if", sorry. Fixed version at

[O] PATCH: Allow class attribute for headline in HTML export

001 From: Jens Lechtenboerger Date: Sun, 2 Dec 2018 19:05:55 +0100 Subject: [PATCH] ox-html.el: New property HTML_HEADLINE_CLASS for class of headline * lisp/ox-html.el (org-html-headline): Add new property HTML_HEADLINE_CLASS to assign class attribute to headline. * doc/org-manual.org: Document

Re: [O] Help with sharing emacs-org presentation

On 2018-10-25, Feiming Chen wrote: > I gave a talk on emacs-org in a local workshop (Government Advances > in Statistical Programming) in Washington D.C. yesterday. I'd like to > share the slides and org source file with the community (see attached). Thanks for sharing! I wonder why you stress

Re: [O] org-crypt broken on Ubuntu 18.04

On 2018-06-14, Óscar Fuentes wrote: > While trying to create a demo file I noticed that decryption works fine > as long as the content was relatively new, while it fails for content > that was encrypted years ago. > > I tried setting epg-gpg-program to "gpg" (it is "gpg2" by default) for >

Re: [O] org-reveal: content side by side

On 2018-02-13, Michael Welle wrote: > That jumping of the headings is one of my main issues, I think it's not > acceptable. I see. I don’t know how to fix the headings at the top and have the contents vertically centered. Best wishes Jens

Re: [O] org-reveal: content side by side

On 2018-02-11, Michael Welle wrote: > Looks easy, eh? A header at the top, a footer at the bottom and a lot > of space in between. In some cases, like in [1], I wanted content (e.g. > Ich...OS/2 Warp 4) to be centered horizontally and > vertically between the footer and the header. I created

Re: [O] [PATCH] ox.el: Define subtitle macro

On 2017-11-21, Nicolas Goaziou wrote: > For the record, I implemented a "keyword" macro (master branch). Excellent, that works for me. Many thanks Jens

Re: [O] [PATCH] ox.el: Define subtitle macro

On 2017-11-17, Nicolas Goaziou wrote: > SUBTITLE keyword may not be supported in every back-end. As > a consequence, supporting a global {{{subtitle}}} macro sounds > presumptuous. > > Anyway, it begs for generalisation. The same problem is going to arise > for CREATOR, KEYWORDS, and WHATNOT.

Re: [O] [PATCH] ox.el: Define subtitle macro

On 2017-11-17, Rasmus wrote: > Jens Lechtenboerger <lech...@wi.uni-muenster.de> writes: > >> the attached patch adds a subtitle macro with documentation. > > AFAIK it’s already added to the backends where it makes sense. It’s not a > basic keyword like "#+author&

[O] [PATCH] ox.el: Define subtitle macro

Hi there, the attached patch adds a subtitle macro with documentation. Best wishes Jens >From 3f54f515847f1f3034274d79fff6cfd1f92c72a9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jens=20Lechtenb=C3=B6rger?= Date: Thu, 16 Nov 2017 15:03:33 +0100 Subject: [PATCH]

[O] [PATCH] ox-publish.el: Fix regexp `match' to be non-nil

Hi there, recursive publishing fails with base-extension any because a nil regexp is passed. The attached patch fixes this. Best wishes Jens P.S. I did the necessary paperwork (copyright assignment) for Emacs. >From 6584a78c350016e39c199bb61d203bc12c0c4c53 Mon Sep 17 00:00:00 2001 From:

[O] Announce: Audio presentations with reveal.js from Org mode

Hi there, you may be aware of Org-Reveal [1] to generate reveal.js [2] presentations, which are HTML presentations, from Org mode. I extended Org-Reveal to generate presentations with embedded audio and bundled that along with some reveal.js plugins and necessary configuration in the GitLab

  1   2   >