On 12/03/2016 05:31 PM, Charles C. Berry wrote:
> On Sat, 3 Dec 2016, Scott Randby wrote:
>
>> On 12/03/2016 02:40 PM, Scott Otterson wrote:
>>> When an org file contains a string with more than one underscore, the
>>> orgmode export result will crash latex (example attached). On the
>>> other h
hello,
Nicolas Goaziou writes:
> Hello,
>
> Samuel Wales writes:
>
>> thanks for the explanation. the idea is that org 9 is using the
>> previously scheduled section as a complete list and that it did not
>> trigger on the first day and did on the second, and show-all nil in
>> org 9 does not
Hello,
Lambda Coder writes:
> See the attached patch file diff'd against maint.
Applied. Thank you for all that work.
Regards,
--
Nicolas Goaziou
Hello,
David Dynerman writes:
> I'd like to report a bug. It seems that setting
> org-src-preserve-indentation to true doesn't work if it's set buffer
> local.
>
> To reproduce, save the following as an org file:
>
> #+BEGIN_SRC python :tangle preserve-indent.py
> class Foo:
> bar = 5
> #+EN
Hello,
Samuel Wales writes:
> thanks for the explanation. the idea is that org 9 is using the
> previously scheduled section as a complete list and that it did not
> trigger on the first day and did on the second, and show-all nil in
> org 9 does not refer to the scheduled section but only to t
On Sat, 3 Dec 2016, Scott Randby wrote:
On 12/03/2016 02:40 PM, Scott Otterson wrote:
When an org file contains a string with more than one underscore, the
orgmode export result will crash latex (example attached). On the
other hand, the org html export does finish successfully, and while
res
Absolutely.
Thanks,
Micah
>From f7c71428981a5f7c0ff5ee44fcecf7003c340813 Mon Sep 17 00:00:00 2001
From: madhat2r
Date: Sat, 3 Dec 2016 09:33:13 -0600
Subject: [PATCH] add sqsh engine and ORG-NEWS entry
---
etc/ORG-NEWS | 17
lisp/ob-sql.el | 85 +++
On 12/03/2016 02:40 PM, Scott Otterson wrote:
> When an org file contains a string with more than one underscore, the
> orgmode export result will crash latex (example attached). On the
> other hand, the org html export does finish successfully, and while
> result is odd, it's odd in a way that m
Hello,
Scott Otterson writes:
> If a plain list has more than four levels, org-mode will produce latex that
> crashes. See attached. On the other hand, html export works fine, even
> for much deeper lists.
>
> In a large org file, this export error is pretty time consuming for a naive
> user (
Hello,
MaDhAt2r writes:
> I went ahead and set up a public branch for these changes.
>
> I added ORG-NEWS entry, and some other minor changes in the commentary
> of ob-sql.el.
Great.
> https://github.com/madhat2r/org-mode/tree/feature/babel-sqsh-engine
Would you mind sending me the patch thro
Hello,
Scott Otterson writes:
> Could you please check the .tex output you got when exported my .org file
> example (attached again)? In the .tex I get (also attached), it's clear
> that org-mode has forgotten to escape the '#' in the URL. In headlink.tex,
> if I replace '#' with ''\#', then l
you could try commenting out orcb-key too. it should be using the
bibtex-autokey settings though.
Georg W. Otto writes:
> John Kitchin writes:
>
>> That happens because of the function org-ref-title-case-article in the
>> variable org-ref-clean-bibtex-entry-hook.
>>
>> Just set org-ref-clean-bib
Nicolas Goaziou writes:
> Hello,
>
> Anthony Cowley writes:
>
>> When I hit C-c C-c on a latex src block with a :file header,
>> I ultimately get an error from org-compile-file that the expected
>> output file in a temp directory was not produced. However, the file is
>> produced in the current
When an org file contains a string with more than one underscore, the
orgmode export result will crash latex (example attached). On the other
hand, the org html export does finish successfully, and while result is
odd, it's odd in a way that makes the problem visible and easy to identify.
Many p
When I am trying to learn a new habit, I often write it in Org Mode. So I
have many entries like:
*** TODO Relax: talk, read book, shower or pray
SCHEDULED: <2016-11-28 Mon 21:30 ++1d>
:PROPERTIES:
:ID: 2ff41cfe-156f-4870-a4ef-991cc2cc986c
:CREATED: [2016-06-16 Thu 13:23]
John Kitchin writes:
> That happens because of the function org-ref-title-case-article in the
> variable org-ref-clean-bibtex-entry-hook.
>
> Just set org-ref-clean-bibtex-entry-hook to have what you want in it
> in your init files to prevent the title casing from occurring.
>
Thanks a lot for y
On Fri, 2 Dec 2016, David Dynerman wrote:
Dear list,
Is it possible to include sections of an org document while tangling.
I have in mind something like the following:
* Some section
[David's version deleted]
#+NAME: doc
#+BEGIN_SRC org :exports results :results replace
This is an introd
Hello,
I would like to put my common org config in github so that I can access it
from anywhere/any machine.
Currently I have
#+SETUPFILE: ~/org/common/config.org
I would like to do something like
#+SETUPFILE: https://cdn.rawgit.com/path/to/config.org
I can probably add an async shell executi
THanks, John, I'm sure you're right actually. So I've just written my
matching function like this:
(lambda (f) (string-match (concat "\\\(" fname "\\\)\\\([^[:alnum:]]\\\)*"
lname) f))
and if that has a nil result:
(lambda (f) (string-match (concat "\\\(" nname "\\\)\\\([^[:alnum:]]\\\)*"
lname)
If a plain list has more than four levels, org-mode will produce latex that
crashes. See attached. On the other hand, html export works fine, even
for much deeper lists.
In a large org file, this export error is pretty time consuming for a naive
user (me) to isolate, so I'd like to suggest that,
Thanks Nicolas.
I went ahead and set up a public branch for these changes.
I added ORG-NEWS entry, and some other minor changes in the commentary
of ob-sql.el.
https://github.com/madhat2r/org-mode/tree/feature/babel-sqsh-engine
-Micah
On Dec 03 at 09:08 AM, Nicolas Goaziou said thus:
> Hello,
Hi Nicolas,
Could you please check the .tex output you got when exported my .org file
example (attached again)? In the .tex I get (also attached), it's clear
that org-mode has forgotten to escape the '#' in the URL. In headlink.tex,
if I replace '#' with ''\#', then latexmk can successfully make
Hello,
MaDhAt2r writes:
> Thanks for your comments Nicolas! I hope this is better.
Thank you. This looks good.
However, I'm not able to apply it on master branch. Could you rebase
your branch against master and send that patch again?
Also, could you provide an ORG-NEWS entry about the new fea
Hello,
Eric Danan writes:
> When adding an org-bibtex entry with `org-bibtex-write' (or any
> command relying on it), the headline is the title. The patch below
> simply makes the headline customizable through a new variable.
Thank you.
> If you find it worth to incorporate this into org-bibte
24 matches
Mail list logo