On Aug 16, 2010, at 5:49 PM, Puneeth wrote:
On Mon, Aug 16, 2010 at 9:12 PM, Carsten Dominik
wrote:
Hi everyone,
this has now been a 10-message thread about a bug that was fixed a
while
ago.
Please, if you submit a bug report, one part of your required
homework
is to try with the latest
Hi everyone,
this has now been a 10-message thread about a bug that was fixed a
while ago.
Please, if you submit a bug report, one part of your required homework
is to try with the latest version of Org-mode available before claiming
there is a bug.
Thanks!
- Carsten
On Aug 16, 2010, at 5:3
On Mon, Aug 16, 2010 at 9:12 PM, Carsten Dominik
wrote:
> Hi everyone,
>
> this has now been a 10-message thread about a bug that was fixed a while
> ago.
> Please, if you submit a bug report, one part of your required homework
> is to try with the latest version of Org-mode available before claim
Rares Pop wrote:
> From what I found so far there are no macros involved here.
>
> I'll perform the upgrade to the latest version and see how if it's fixed.
>
It *was* a bug: it was fixed by this commit:
,
|
| commit be232c4c212283ca6311cfe35c0bae7719146e55
| Author: Carsten Dominik
| D
>From what I found so far there are no macros involved here.
I'll perform the upgrade to the latest version and see how if it's fixed.
Thanks to all,
Rares
On Mon, Aug 16, 2010 at 5:08 PM, Sebastian Rose wrote:
> Rares Pop writes:
> > Carsten,
> >
> > I've found part of the problem but I don't
Rares Pop writes:
> Carsten,
>
> I've found part of the problem but I don't know the cause.
> The *.tex file was generated with curly brackets
> (e.g. \section{\textbf\{TODO\} Task 1}) - i've attached the *.tex file
> And if I remove the slashes(*\ \)* signs the latex code will be something
> like
Thanks,
I'll upgrade then.
Rares
On Mon, Aug 16, 2010 at 4:14 PM, Simon Brown wrote:
> Hi Rares,
>
> At Mon, 16 Aug 2010 14:27:47 +0300,
> Rares Pop wrote:
> > I've found part of the problem but I don't know the cause.
> > The *.tex file was generated with curly brackets
> > (e.g. \section{\t
Hi Rares,
At Mon, 16 Aug 2010 14:27:47 +0300,
Rares Pop wrote:
> I've found part of the problem but I don't know the cause.
> The *.tex file was generated with curly brackets
> (e.g. \section{\textbf\{TODO\} Task 1}) - i've attached the *.tex file
> And if I remove the slashes(*\ \)* signs the la
Carsten,
I've found part of the problem but I don't know the cause.
The *.tex file was generated with curly brackets
(e.g. \section{\textbf\{TODO\} Task 1}) - i've attached the *.tex file
And if I remove the slashes(*\ \)* signs the latex code will be something
like this (e.g \section{\textbf{TODO
Hi,
I cannot reproduce this problem.
Best wishes
- Carsten
On Aug 16, 2010, at 11:06 AM, Rares Pop wrote:
Hi Carsten,
I've attached the org file and the exported PDF file.
I'm using org-6.35i and export settings are the default ones.
Thanks again for trying to help,
Rares
On Mon, Aug 16,
Hi Carsten,
I've attached the org file and the exported PDF file.
I'm using org-6.35i and export settings are the default ones.
Thanks again for trying to help,
Rares
On Mon, Aug 16, 2010 at 11:45 AM, Carsten Dominik wrote:
>
> On Aug 16, 2010, at 10:39 AM, Rares Pop wrote:
>
> Hello,
>>
>>
On Aug 16, 2010, at 10:39 AM, Rares Pop wrote:
Hello,
sorry for the beautifier question.
I'm trying to export an org document with some TODO tasks to a PDF
file.
And I get the output in the PDF file for the TODO keyword like this:
{TODO}
But i want it simple
TODO or [TODO].
I don't want
Hello,
sorry for the beautifier question.
I'm trying to export an org document with some TODO tasks to a PDF file.
And I get the output in the PDF file for the TODO keyword like this:
*{TODO}*
*
*
But i want it simple
*TODO or [TODO].*
*
*
I don't want to have those curly brackets at the beginni
13 matches
Mail list logo
