[O] ob-lisp.el patch to choose to use SLIME or SLY

I original created an package ob-lisp on here: https://github.com/stardiviner/ob-lisp and add it to MELPA recipe. https://github.com/melpa/melpa/pull/3682 The author suggest me to merge this change to Org-mode. I attached patch in attachment file. Hope someone can merge this patch.

Re: [O] first #+LATEX_HEADER: in SETUPFILE not correctly exported and causes Missing \begin{document} error

On 03/26/2016 01:14 PM, Eric S Fraga wrote: On Saturday, 26 Mar 2016 at 10:15, Charles Millar wrote: [...] I was not clear - I ran the exports after I made the correction to "mysetup", i.e. \newcommand{\\foo}{bar} but I am confused: why the \\ for foo but \ for newcommand? My typo. Just in

Re: [O] external/central ``macro'' definitions (for instance link abbrev's)?

On Saturday, 26 Mar 2016 at 13:53, Martin Steffen wrote: [...] > I realize that my original post was perhaps unprecise. What I was looking > after is this ``awareness'' of those definitions (using the #+INCLUDE > mechanism) /not just/ for export. I was missing it Ah, I see. Yes, I believe

Re: [O] first #+LATEX_HEADER: in SETUPFILE not correctly exported and causes Missing \begin{document} error

On Saturday, 26 Mar 2016 at 10:15, Charles Millar wrote: [...] > I was not clear - I ran the exports after I made the correction to > "mysetup", i.e. \newcommand{\\foo}{bar} but I am confused: why the \\ for foo but \ for newcommand? What is the actual result in the output.tex file? > I do

Re: [O] [PATCH] org-babel C math.h issue

Done. Le 26/03/2016 00:42, Nicolas Goaziou a écrit : > Applied. Thank you. > > Would you (or the OP) mind documenting the feature at > ? >

[O] task management integration with web-hosted git repos

Dear all, while struggling to get a working gtd orgmode-based workflow, I realized I may just limit myself to a github/gitlab/gogs environment. Specifically, I'm thinking about this parallelism: each project is a repo, each subproject is a milestone, each task is an issue w/ milestone, and

Re: [O] first #+LATEX_HEADER: in SETUPFILE not correctly exported and causes Missing \begin{document} error

Eric, On 03/26/2016 08:51 AM, Eric S Fraga wrote: On Saturday, 26 Mar 2016 at 07:52, Charles Millar wrote: [...] Thanks for the correction. I escaped the \foo otherwise I had a spurious "oobar" at the beginning of the exported document so that my latex class has \newcommand{\\foo}{bar} I

Re: [O] external/central ``macro'' definitions (for instance link abbrev's)?

Eric S Fraga ucl.ac.uk> writes: > > On Saturday, 26 Mar 2016 at 11:43, Martin Steffen wrote: > > [...] > > > Now, the #+LINK mechanism works fine as such. But I want that it works > > for all used *.org files that constituted the overall document /without/ > > repeating the definition.

Re: [O] Exporting usenet links

On Saturday, 26 Mar 2016 at 13:12, Eric S Fraga wrote: > On Saturday, 26 Mar 2016 at 13:55, Michael Welle wrote: >> Hello, >> > >> exporting usenet links to html seems to be broken: >> >> [[news:de.sci.electronics][dse]] > > Not broken per se in that the default behaviour is to treat news: the >

Re: [O] Exporting usenet links

On Saturday, 26 Mar 2016 at 13:55, Michael Welle wrote: > Hello, > > exporting usenet links to html seems to be broken: > > [[news:de.sci.electronics][dse]] Not broken per se in that the default behaviour is to treat news: the same as http: on export. If that's not what you want, you can

Re: [O] first #+LATEX_HEADER: in SETUPFILE not correctly exported and causes Missing \begin{document} error

On Saturday, 26 Mar 2016 at 07:52, Charles Millar wrote: [...] > Thanks for the correction. I escaped the \foo otherwise I had a > spurious "oobar" at the beginning of the exported document so that my > latex class has > > \newcommand{\\foo}{bar} > > I suspect that this problem may be file

Re: [O] external/central ``macro'' definitions (for instance link abbrev's)?

On Saturday, 26 Mar 2016 at 11:43, Martin Steffen wrote: [...] > Now, the #+LINK mechanism works fine as such. But I want that it works > for all used *.org files that constituted the overall document /without/ > repeating the definition. Something like > > #+INCLUDE "definitions.org" > > at

Re: [O] Multipart/Alternative reply to email?

Uwe Brauer writes: "Thorsten" == Thorsten Jolitz writes: >> Peter Davis writes: >>> I realize this would require somehow converting the original message >>> to org-mode markup, and that seems very tricky. I just wondered

Re: [O] Multipart/Alternative reply to email?

>>> "Thorsten" == Thorsten Jolitz writes: > Peter Davis writes: >> I realize this would require somehow converting the original message >> to org-mode markup, and that seems very tricky. I just wondered >> if anyone had taken a stab at building

Re: [O] first #+LATEX_HEADER: in SETUPFILE not correctly exported and causes Missing \begin{document} error

Hi Eric On 03/26/2016 05:36 AM, Eric S Fraga wrote: On Friday, 25 Mar 2016 at 20:56, Charles Millar wrote: [...] \newcommand\foo{bar} The problem is this line. The proper syntax is \newcommand{\foo}{bar} Thanks for the correction. I escaped the \foo otherwise I had a spurious "oobar" at

[O] external/central ``macro'' definitions (for instance link abbrev's)?

Hi, I like to achieve the following. I do a org-document which I separate into different files (one per chapter or similar). They are all included into some "main.org". In that setup, I'd like to use some centrally defined links, like #+LINK: toollib ../../src/lib or similar, as an abbrev

Re: [O] first #+LATEX_HEADER: in SETUPFILE not correctly exported and causes Missing \begin{document} error

On Friday, 25 Mar 2016 at 20:56, Charles Millar wrote: [...] > \newcommand\foo{bar} The problem is this line. The proper syntax is \newcommand{\foo}{bar} HTH, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-668-g809a83