Re: latex fragments compilation error when exporting to html

2020-08-31 Thread Jeremie Juste
9.3.7 (release_9.3.7-705-gea9463 > @ /home/nick/src/emacs/org/org-mode/lisp/). > What version are you using? Thanks for have taken the time to check. The org-version I was using was Org mode version 9.3.7 (9.3.7-13-ge62ca4-elpaplus @ /home/djj/.emacs.d/elpa/org-plus-contrib-20200713/) I updated to the latest version on melpa but the issue persists Org mode version 9.3.7 (9.3.7-24-g7b657c-elpa @ /home/djj/.emacs.d/elpa/org-20200831/) Best regards, Jeremie

Re: how to create next, previous, and up navigation links when exporting to html

2020-08-31 Thread Kyle Meyer
Christopher W. Ryan writes: > how do I create next, previous, and up navigation links when exporting > to html, like in the org mode manual: > > https://orgmode.org/manual/HTML-specific-export-settings.html I think that's created in a two-step process: using org-texinfo-export-to-texinfo to

Re: [PATCH] ob-core: Avoid table conversion warning for empty results

2020-08-31 Thread Kyle Meyer
Colin Baxter writes: > >> This patch would squelch the inappropriate warning you report > >> while not hiding other warnings. > > > Thank you. I'll apply the patch to my org-mode and report back. > > I have now applied the patch to my local org-mode git repository and it > works with

Re: latex fragments compilation error when exporting to html

2020-08-31 Thread Nick Dokos
Jeremie Juste writes: > Hello > > When I export test.org to html, the latex fragment fail to compile. > The reason is a star get added to the tabular environment. {tabular*} > (see tmpfile.tex). > > I don't know why the function insists in using the tabular* environment. > > From this point I

latex fragments compilation error when exporting to html

2020-08-31 Thread Jeremie Juste
Hello When I export test.org to html, the latex fragment fail to compile. The reason is a star get added to the tabular environment. {tabular*} (see tmpfile.tex). I don't know why the function insists in using the tabular* environment. >From this point I would have two questions: How can I

Re: [feature request] A new cookie type [!] showing the last note taken

2020-08-31 Thread Nicolas Goaziou
Hello, Ihor Radchenko writes: > Instead of linking to the function, we can define the format used by > `org-add-note' as a formal format for notes. Currently `org-add-note' > uses the following format: > > - \\ > This is not specific enough to be considered as syntax. The risk of false

org-format-outline-path fonts sizes in the minibuffer

2020-08-31 Thread CRSHCMDR
*I’m not sure If this is actually a bug so I haven’t included any backtrace/debug information.* Forgive me I am not sure the exact terminology. I have, within the last two weeks, began to transition to emacs from vim, specifically for org mode. In addition I am not a developer by trade and my

Re: new feature for consideration: other-tab for org-agenda-window-setup

2020-08-31 Thread Eric S Fraga
On Saturday, 29 Aug 2020 at 08:07, Kyle Meyer wrote: > Applied (e8ebf5d6c). Thank you. -- : Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-720-gbe5916

Re: [feature request] A new cookie type [!] showing the last note taken

2020-08-31 Thread Ihor Radchenko
> Make it easier perhaps -- once the tool has been changed to the new > syntax. But you might break current usage. And not everyone using such > tools has coding skills to make those tools work again. > Prof. Kitchin kindly gifted me with some code for a flash card learning > system. That code

Re: [PATCH] improve ol-man.el with occur searching

2020-08-31 Thread numbch...@gmail.com
Hi, Nicolas, gentle ping about this patch. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Mon, Aug 17, 2020 at

Re: [feature request] A new cookie type [!] showing the last note taken

2020-08-31 Thread Julius Müller
Am 31.08.20 um 04:26 schrieb Ihor Radchenko: > I would not call defining syntax for notes "a syntax change". Rather > addition to syntax. Since there was no formal definition of notes in the > past, introducing formal syntax for notes should not break any existing > tool. If anything, it should