export TODO keyword

export TODO keyword

[Rares Pop]

[-- Attachment #1.1: Type: text/plain, Size: 377 bytes --]

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 beginning and the end of
the TODO keyword.


Thank you very much for the help,
Rares

[-- Attachment #1.2: Type: text/html, Size: 1773 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: export TODO keyword

[Carsten Dominik]

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 to have those curly brackets at the beginning and the  
> end of the TODO keyword.

Hi Rares,

how about you post an example file for people to reproduce the issue?
And then say exactly how you exported it, with what setup?

- Carsten

Re: export TODO keyword

[Rares Pop]

[-- Attachment #1.1: Type: text/plain, Size: 841 bytes --]

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 <carsten.dominik@gmail.com
> wrote:

>
> 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 to have those curly brackets at the beginning and the end of
>> the TODO keyword.
>>
>
> Hi Rares,
>
> how about you post an example file for people to reproduce the issue?
> And then say exactly how you exported it, with what setup?
>
> - Carsten
>
>

[-- Attachment #1.2: Type: text/html, Size: 2101 bytes --]

[-- Attachment #2: test.pdf --]
[-- Type: application/pdf, Size: 25628 bytes --]

[-- Attachment #3: test.org --]
[-- Type: application/octet-stream, Size: 88 bytes --]


* TODO Task 1
  - this task 1 is for test


* TODO Task 2
  - this task 2 is for test 

[-- Attachment #4: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: export TODO keyword

[Carsten Dominik]

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, 2010 at 11:45 AM, Carsten Dominik <carsten.dominik@gmail.com 
> > wrote:
>
> 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 to have those curly brackets at the beginning and the  
> end of the TODO keyword.
>
> Hi Rares,
>
> how about you post an example file for people to reproduce the issue?
> And then say exactly how you exported it, with what setup?
>
> - Carsten
>
>
> <test.pdf><test.org>

- Carsten

Re: export TODO keyword

[Rares Pop]

[-- Attachment #1.1: Type: text/plain, Size: 1767 bytes --]

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} Task 1})
and by exporting it to PDF it looks ok.

The value of the variable *Org Export Latex Todo Keyword Markup* is *
\textbf{%s}*
*
*
So it seems that somewhere on the road some slash signs are added without
permission.

Thanks again,
Rares



I've attached also my *.emacs* file and the tex file output from the org
file.

On Mon, Aug 16, 2010 at 1:36 PM, Carsten Dominik
<carsten.dominik@gmail.com>wrote:

> 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, 2010 at 11:45 AM, Carsten Dominik <
>> carsten.dominik@gmail.com> wrote:
>>
>> 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 to have those curly brackets at the beginning and the end of
>> the TODO keyword.
>>
>> Hi Rares,
>>
>> how about you post an example file for people to reproduce the issue?
>> And then say exactly how you exported it, with what setup?
>>
>> - Carsten
>>
>>
>> <test.pdf><test.org>
>>
>
> - Carsten
>
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 4461 bytes --]

[-- Attachment #2: test.tex --]
[-- Type: application/x-tex, Size: 817 bytes --]

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: export TODO keyword

[Noorul Islam K M]

Rares Pop <rares.pop@gmail.com> writes:

> 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

I am not able to re-produce this with the trunk version. May be bug in
the older version?

Thanks and Regards
Noorul

Re: export TODO keyword

[Simon Brown]

Hi Rares,

At Mon, 16 Aug 2010 14:27:47 +0300,
Rares Pop <rares.pop@gmail.com> 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 latex code will be something
> like this (e.g \section{\textbf{TODO} Task 1})
> and by exporting it to PDF it looks ok.
> 
> The value of the variable *Org Export Latex Todo Keyword Markup* is *
> \textbf{%s}*
> *
> *
> So it seems that somewhere on the road some slash signs are added without
> permission.

This sounds like a bug I encountered a while back:
http://article.gmane.org/gmane.emacs.orgmode/24900

Carsten fixed it a while ago (Thanks!)

I suggest you update.

Simon

Re: export TODO keyword

[Rares Pop]

[-- Attachment #1.1: Type: text/plain, Size: 970 bytes --]

Thanks,

I'll upgrade then.

Rares

On Mon, Aug 16, 2010 at 4:14 PM, Simon Brown <simon@cliffestones.demon.co.uk
> wrote:

> Hi Rares,
>
> At Mon, 16 Aug 2010 14:27:47 +0300,
> Rares Pop <rares.pop@gmail.com> 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 latex code will be something
> > like this (e.g \section{\textbf{TODO} Task 1})
> > and by exporting it to PDF it looks ok.
> >
> > The value of the variable *Org Export Latex Todo Keyword Markup* is *
> > \textbf{%s}*
> > *
> > *
> > So it seems that somewhere on the road some slash signs are added without
> > permission.
>
> This sounds like a bug I encountered a while back:
> http://article.gmane.org/gmane.emacs.orgmode/24900
>
> Carsten fixed it a while ago (Thanks!)
>
> I suggest you update.
>
> Simon
>

[-- Attachment #1.2: Type: text/html, Size: 1908 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: export TODO keyword

[Sebastian Rose]

Rares Pop <rares.pop@gmail.com> 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 this (e.g \section{\textbf{TODO} Task 1})
> and by exporting it to PDF it looks ok.


Hi Rares,


are you sure, you did not try to define a Macro the wrong way or
something like that?   I cannot reproduce this either.


   Sebastian



>
> The value of the variable *Org Export Latex Todo Keyword Markup* is *
> \textbf{%s}*
> *
> *
> So it seems that somewhere on the road some slash signs are added without
> permission.
>
> Thanks again,
> Rares
>
>
>
> I've attached also my *.emacs* file and the tex file output from the org
> file.
>
> On Mon, Aug 16, 2010 at 1:36 PM, Carsten Dominik
> <carsten.dominik@gmail.com>wrote:
>
>> 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, 2010 at 11:45 AM, Carsten Dominik <
>>> carsten.dominik@gmail.com> wrote:
>>>
>>> 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 to have those curly brackets at the beginning and the end of
>>> the TODO keyword.
>>>
>>> Hi Rares,
>>>
>>> how about you post an example file for people to reproduce the issue?
>>> And then say exactly how you exported it, with what setup?
>>>
>>> - Carsten
>>>
>>>
>>> <test.pdf><test.org>
>>>
>>
>> - Carsten

Re: export TODO keyword

[Rares Pop]

[-- Attachment #1.1: Type: text/plain, Size: 2465 bytes --]

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 <sebastian_rose@gmx.de>wrote:

> Rares Pop <rares.pop@gmail.com> 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 this (e.g \section{\textbf{TODO} Task 1})
> > and by exporting it to PDF it looks ok.
>
>
> Hi Rares,
>
>
> are you sure, you did not try to define a Macro the wrong way or
> something like that?   I cannot reproduce this either.
>
>
>   Sebastian
>
>
>
> >
> > The value of the variable *Org Export Latex Todo Keyword Markup* is *
> > \textbf{%s}*
> > *
> > *
> > So it seems that somewhere on the road some slash signs are added without
> > permission.
> >
> > Thanks again,
> > Rares
> >
> >
> >
> > I've attached also my *.emacs* file and the tex file output from the org
> > file.
> >
> > On Mon, Aug 16, 2010 at 1:36 PM, Carsten Dominik
> > <carsten.dominik@gmail.com>wrote:
> >
> >> 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, 2010 at 11:45 AM, Carsten Dominik <
> >>> carsten.dominik@gmail.com> wrote:
> >>>
> >>> 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 to have those curly brackets at the beginning and the end
> of
> >>> the TODO keyword.
> >>>
> >>> Hi Rares,
> >>>
> >>> how about you post an example file for people to reproduce the issue?
> >>> And then say exactly how you exported it, with what setup?
> >>>
> >>> - Carsten
> >>>
> >>>
> >>> <test.pdf><test.org>
> >>>
> >>
> >> - Carsten
>

[-- Attachment #1.2: Type: text/html, Size: 4283 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: export TODO keyword

[Nick Dokos]

Rares Pop <rares.pop@gmail.com> 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 <carsten.dominik@gmail.com>
| Date:   Thu May 13 08:47:26 2010 +0200
| 
|     LaTeX export: Fix TODO keyword export
| 
| diff --git a/lisp/ChangeLog b/lisp/ChangeLog
| index 45c9ec7..04c9ecb 100644
| --- a/lisp/ChangeLog
| +++ b/lisp/ChangeLog
| @@ -1,3 +1,8 @@
| +2010-05-13  Carsten Dominik  <carsten.dominik@gmail.com>
| +
| +	* org-latex.el (org-export-latex-keywords-maybe): Protect the
| +	TODO markup.
| +
|  2010-05-13  Mikael Fornius  <mfo@abc.se>
|  
|  	* org-habit.el (org-habit-build-graph): Help-echo date when
| diff --git a/lisp/org-latex.el b/lisp/org-latex.el
| index e3544bf..afa0be2 100644
| --- a/lisp/org-latex.el
| +++ b/lisp/org-latex.el
| @@ -1289,7 +1289,8 @@ links, keywords, lists, tables, fixed-width"
|  			(cdr todo-markup) (car todo-markup)))
|  		   (t (cdr (or (assoc (match-string 1) todo-markup)
|  			       (car todo-markup))))))
| -	(replace-match (format fmt (match-string 1)) t t)))
| +	(replace-match (org-export-latex-protect-string
| +			(format fmt (match-string 1))) t t)))
|      ;; convert priority string
|      (when (re-search-forward "\\[\\\\#.\\]" nil t)
|        (if (plist-get remove-list :priority)
`----

so an upgrade should fix it.

Re: export TODO keyword

[Carsten Dominik]

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:37 PM, Nick Dokos wrote:

> Rares Pop <rares.pop@gmail.com> 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 <carsten.dominik@gmail.com>
> | Date:   Thu May 13 08:47:26 2010 +0200
> |
> |     LaTeX export: Fix TODO keyword export
> |
> | diff --git a/lisp/ChangeLog b/lisp/ChangeLog
> | index 45c9ec7..04c9ecb 100644
> | --- a/lisp/ChangeLog
> | +++ b/lisp/ChangeLog
> | @@ -1,3 +1,8 @@
> | +2010-05-13  Carsten Dominik  <carsten.dominik@gmail.com>
> | +
> | +	* org-latex.el (org-export-latex-keywords-maybe): Protect the
> | +	TODO markup.
> | +
> |  2010-05-13  Mikael Fornius  <mfo@abc.se>
> |
> |  	* org-habit.el (org-habit-build-graph): Help-echo date when
> | diff --git a/lisp/org-latex.el b/lisp/org-latex.el
> | index e3544bf..afa0be2 100644
> | --- a/lisp/org-latex.el
> | +++ b/lisp/org-latex.el
> | @@ -1289,7 +1289,8 @@ links, keywords, lists, tables, fixed-width"
> |  			(cdr todo-markup) (car todo-markup)))
> |  		   (t (cdr (or (assoc (match-string 1) todo-markup)
> |  			       (car todo-markup))))))
> | -	(replace-match (format fmt (match-string 1)) t t)))
> | +	(replace-match (org-export-latex-protect-string
> | +			(format fmt (match-string 1))) t t)))
> |      ;; convert priority string
> |      (when (re-search-forward "\\[\\\\#.\\]" nil t)
> |        (if (plist-get remove-list :priority)
> `----
>
> so an upgrade should fix it.

- Carsten

Re: export TODO keyword

[Puneeth]

On Mon, Aug 16, 2010 at 9:12 PM, Carsten Dominik
<carsten.dominik@gmail.com> 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 claiming
> there is a bug.

Sure! I think this should go onto org-mode site too -
http://orgmode.org/org.html#Feedback

>
> Thanks!
>
> - Carsten
>
> On Aug 16, 2010, at 5:37 PM, Nick Dokos wrote:
>
>> Rares Pop <rares.pop@gmail.com> 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 <carsten.dominik@gmail.com>
>> | Date:   Thu May 13 08:47:26 2010 +0200
>> |
>> |     LaTeX export: Fix TODO keyword export
>> |
>> | diff --git a/lisp/ChangeLog b/lisp/ChangeLog
>> | index 45c9ec7..04c9ecb 100644
>> | --- a/lisp/ChangeLog
>> | +++ b/lisp/ChangeLog
>> | @@ -1,3 +1,8 @@
>> | +2010-05-13  Carsten Dominik  <carsten.dominik@gmail.com>
>> | +
>> | +     * org-latex.el (org-export-latex-keywords-maybe): Protect the
>> | +     TODO markup.
>> | +
>> |  2010-05-13  Mikael Fornius  <mfo@abc.se>
>> |
>> |       * org-habit.el (org-habit-build-graph): Help-echo date when
>> | diff --git a/lisp/org-latex.el b/lisp/org-latex.el
>> | index e3544bf..afa0be2 100644
>> | --- a/lisp/org-latex.el
>> | +++ b/lisp/org-latex.el
>> | @@ -1289,7 +1289,8 @@ links, keywords, lists, tables, fixed-width"
>> |                       (cdr todo-markup) (car todo-markup)))
>> |                  (t (cdr (or (assoc (match-string 1) todo-markup)
>> |                              (car todo-markup))))))
>> | -     (replace-match (format fmt (match-string 1)) t t)))
>> | +     (replace-match (org-export-latex-protect-string
>> | +                     (format fmt (match-string 1))) t t)))
>> |      ;; convert priority string
>> |      (when (re-search-forward "\\[\\\\#.\\]" nil t)
>> |        (if (plist-get remove-list :priority)
>> `----
>>
>> so an upgrade should fix it.
>
> - Carsten
>
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>



-- 
Puneeth

Re: export TODO keyword

[Carsten Dominik]

On Aug 16, 2010, at 5:49 PM, Puneeth wrote:

> On Mon, Aug 16, 2010 at 9:12 PM, Carsten Dominik
> <carsten.dominik@gmail.com> 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  
>> claiming
>> there is a bug.
>
> Sure! I think this should go onto org-mode site too -
> http://orgmode.org/org.html#Feedback

I just added this to the manual - it will appear on the site with the  
next release.

Thanks.

- Carsten