Summary:
24.0.91; Emacs runtime crashes while exporting with org-latex
1. Start Emacs with -Q
2. Open the attached .org file
3. C-c C-e l (l as in latex)
4. See that Emacs crashes
I am using the Windows build downloaded from alpha.gnu.org.
I don't know how to attach debugger to the Emacs build.
Michael Hannon writes:
> Greetings. I'm having a problem compiling a C++ source-code block in
> Org-mode. The same C++ code compiles and runs in the shell.
>
> The issue seems to relate to local include files. [...snip...]
> What am I missing?
> /tmp/babel-245846_d/C-src-24584NIQ.cpp:7:26: fa
Suvayu/Rustom
suvayu ali writes:
> Hi Jambunathan,
>
> On Thu, Nov 17, 2011 at 11:06, Jambunathan K wrote:
>> Can anyone else reproduce this?
>
> I can replicate this. The odt file exported by org-odt is not accepted
> by google docs even though libreoffice opens it without problems.
> However
got it， thanks all
Nick Dokos 编写：
>markfilebat126 wrote:
>
>> Bernt Hansen writes:
>>
>> Yes, Bernt, this is exactly what I want.
>> I will dig into why my org-mode behavior is different from yours, when I
>> return home.
>>
>> ,--- my environment
>> | GNU Emacs 23.2.1 (x86_64-pc-linu
Greetings. I'm having a problem compiling a C++ source-code block in
Org-mode. The same C++ code compiles and runs in the shell.
The issue seems to relate to local include files. I.e., a program that
includes only standard files, such as:
#include
works fine. But Org-mode seems to be un
markfilebat126 wrote:
> Bernt Hansen writes:
>
> Yes, Bernt, this is exactly what I want.
> I will dig into why my org-mode behavior is different from yours, when I
> return home.
>
> ,--- my environment
> | GNU Emacs 23.2.1 (x86_64-pc-linux-gnu, GTK+ Version 2.20.1) of 2010-09-02
> o
Bernt Hansen writes:
Yes, Bernt, this is exactly what I want.
I will dig into why my org-mode behavior is different from yours, when I
return home.
,--- my environment
| GNU Emacs 23.2.1 (x86_64-pc-linux-gnu, GTK+ Version 2.20.1) of 2010-09-02 on
pluot, modified by Debian
| Org-mode ver
filebat Mark writes:
> Hi Bernt
>
> I am not sure whether I get you correctly.
>
> The behavior of [#+OPTIONS: tasks:("DONE") todo:nil] looks like (setq
> org-export-with-todo-keywords nil).
>
> My purpose is not to export entries of "TODO", "CANCELED", etc,
> instead of only strings of "TODO", "
Hi Bernt
I am not sure whether I get you correctly.
The behavior of [#+OPTIONS: tasks:("DONE") todo:nil] looks like (setq
org-export-with-todo-keywords nil).
My purpose is not to export entries of "TODO", "CANCELED", etc, instead of
only strings of "TODO", "CANCELED".
On Fri, Nov 18, 2011 at
filebat Mark writes:
> Exporting org-mode's entries to html is a fantastic way for knowledge
> sharing!
>
> Usually entries of "TODO" "HALF" "DELEGATE" "CANCELED" "DEFERRED" are
> incomplete/immature knowledge. Thus, I don't want to export
> them. Furthermore, after they are marked as "DONE", I'
hi emacsers
Exporting org-mode's entries to html is a fantastic way for knowledge sharing!
Usually entries of "TODO" "HALF" "DELEGATE" "CANCELED" "DEFERRED" are
incomplete/immature knowledge.
Thus, I don't want to export them. Furthermore, after they are marked
as "DONE", I'd like to export them.
Gez writes:
> The second issue is one I have with capture all the time; I want the
> refile to be faster. I have a few capture templates for logging that
> send to a particular headline, but most times I use capture the target
> can be anywhere in my main outlines. As it is, I'm almost always
>
Hi Jambunathan,
On Thu, Nov 17, 2011 at 11:06, Jambunathan K wrote:
> Can anyone else reproduce this?
I can replicate this. The odt file exported by org-odt is not accepted
by google docs even though libreoffice opens it without problems.
However it I open it with libreoffice and say edit and sa
"Sebastien Vauban" writes:
> Hi Eric,
>
> Eric Schulte wrote:
>> The standard-code-block-syntax branch has been merged into the master
>> branch of the git repository. This brings two much discussed changes to
>> Org-mode, first a standard set of keywords for code blocks and second
>> the abilit
"Sebastien Vauban" writes:
> Hi Eric,
>
> Eric Schulte wrote:
>> The standard-code-block-syntax branch has been merged into the master branch
>> of the git repository. [...] Additionally I've updated my collection of
>> Org-mode code block scraps [4].
>>
>> [4] http://eschulte.github.com/org-scr
Martyn Jago writes:
> Hi
>
> C-c C-c on a #+call: block() statement no longer causes the block to
> execute.
>
> This regression occurred on Nov 8th:
>
> commit a4273cbe0e0480bd02c59464cafb985951b1c5a2
> Author: Eric Schulte
> Date: Tue Nov 8 19:42:59 2011 -0700
> call lines are more careful a
I have a list of "niggles" which are not on an active todo list
because they only occur to me from time to time, but I wanted to be
able to quickly note each time one of them bothers me, so that the
most annoying ones, the ones I would want to add to my todo list
first, might start to "rise to the
Hi Eric,
Eric Schulte wrote:
> The standard-code-block-syntax branch has been merged into the master branch
> of the git repository. [...] Additionally I've updated my collection of
> Org-mode code block scraps [4].
>
> [4] http://eschulte.github.com/org-scraps/
I just looked at a couple of them
[problem with org-mobile-push from commit
dc62cdcdf11f305149281d16ef2200e18c7abd43
]
I've recently pushed a patch around that area. Does the problem persist
with the latest git ?
Thanks. I updated (to 7c21098323bf0097c7903b014564cd6056bda374) and now
all is well.
pgp3WO1QFGRo
Hello,
Greg Troxel writes:
> I recently updated to the latest git, and found that while everything
> else I tried was ok, I got a backtrace when doing org-mobile-push.
> Bisecting, I found that the problem commit is:
>
> commit dc62cdcdf11f305149281d16ef2200e18c7abd43
> Author: Nicolas Goaziou
Hi
C-c C-c on a #+call: block() statement no longer causes the block to
execute.
This regression occurred on Nov 8th:
commit a4273cbe0e0480bd02c59464cafb985951b1c5a2
Author: Eric Schulte
Date: Tue Nov 8 19:42:59 2011 -0700
call lines are more careful about being in example or verbatim blocks
Hi Eric,
Eric Schulte wrote:
> The standard-code-block-syntax branch has been merged into the master
> branch of the git repository. This brings two much discussed changes to
> Org-mode, first a standard set of keywords for code blocks and second
> the ability to accumulate properties by appendin
Rustom Mody writes:
> Here is a small file for org mode
>
> #+OPTIONS: toc:nil
> #+TITLE: Report
> * Tue 8th
> - http://www.haskell.org/
> * hello
>
> If I export to odt and then upload the odt to google docs,
> google-docs says the file is corrupt.
On my loca
Rustom
Can you send me this odt file either on or off the list?
Please make sure that the document is not resaved from Libreoffice -
this is because LibreOffice rewrites XML if resaved. So send the file as
soon as it is exported out of org-odt.
What is the org-version? Are you exporting with a
Here is a small file for org mode
#+OPTIONS: toc:nil
#+TITLE: Report
* Tue 8th
- http://www.haskell.org/
* hello
If I export to odt and then upload the odt to google docs, google-docs says
the file is corrupt.
It seems to make a difference whether the EOF is imm
Hi Nick,
Nick Dokos wrote:
> Sebastien Vauban wrote:
>> Michael Hannon wrote:
>> >>> (2) I typically use the following BABEL line:
>> >>>
>> >>> #+BABEL: :session *R* :cache yes :results output verbatim :exports both
>> >>> :tangle
>> >>>
>> >>> How would I express that using the PROPERTY syntax?
26 matches
Mail list logo
