Re: [O] [bug] ox-taskjuggler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2015-01-23 09:59, Christian Egli wrote: Søren Mikkelsen so...@aamikkelsen.dk writes: It works, but only for tasks that aren't having a start attribute. It is possible to give a warning if the start attribute already exists and make the default one, the one specified in the attributes (drawer)? What exactly doesn't work? Are there two start entries in the task? One because of the SCHEDULED property and one because of the the start property? Then you might have to remove the start property from org-taskjuggler-valid-task-attributes before adding the other valid attributes i.e. ;; Add other valid attributes. (org-taskjuggler--indent-string (org-taskjuggler--build-attributes task org-taskjuggler-valid-task-attributes)) Might have to become (untested) ;; Add other valid attributes. (org-taskjuggler--indent-string (org-taskjuggler--build-attributes task (remq 'start org-taskjuggler-valid-task-attributes))) HTH Christian The problem by removing the start attribute is that it destroys the backward compatibility. I want ox-taskjuggler to accept both methods, where the start property attribute overrules the scheduled attribute, if this is present. - -- Best regards, Søren Mikkelsen -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUwjEEAAoJECUE7rt2jWDw5WQH/AhkKBjfWZLryYG+Zqj1D5Re +JXahe52HYf5oBXeSJHF250wKxF4KSme6JXHBfO5lfT5IZY+YwZTeUxm0a2KXod3 y9bxrWKqNglkqLLHxpwsZMpTGfcy4LOGJwxqL+brcRSJzftf17bpKnD1pcj62/uT UxLQlWbmmj0WqP4f0xLMtyvkRc5OWDz6T/mylxM0/26cK2xIhdigV42dTXvwFu13 NZdfhL5lUgORHOYseSfV23e/89pnw3V9PIO/4QA/6HEBP7icsSlMb4qiAOMf6wdE JbPVf4hkYfDmBKcFuWeWKAdz94I/Xcov2/0XoCc/qOFEhhlAvxrFm+KzI/Xjr30= =EpK7 -END PGP SIGNATURE-
Re: [O] [bug] ox-taskjuggler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2015-01-22 11:21, Christian Egli wrote: Søren Mikkelsen so...@aamikkelsen.dk writes: It would, however, make sense to be able to scheduled tasks where interpreted as the start time, if the org-file is used for more than just generating the report. I agree that it would make sense to use the scheduled date as the start time. The same is probably true for DEADLINES as well. IIRC there was a patch once for deadlines which I never managed to integrate. Anyway what you would like doesn't seem very hard to implement: Just add another statement to the (let*) of org-taskjuggler--build-task where you get the start time using the org-taskjuggler-get-start function. Then just insert the start time in the (concat) statement maybe right after (and priority (format priority %s\n priority)) Let me know if you need any help Thanks Christian Thanks for suggestions. Well, even though I used emacs for quite some time my elisp programmering skills are on a very basic level, so I'll need some help. I've added (starttime (org-taskjuggler-get-start task)) in the let* and (and starttime (format start %s\n starttime)) after priority. It works, but only for tasks that aren't having a start attribute. It is possible to give a warning if the start attribute already exists and make the default one, the one specified in the attributes (drawer)? - -- Best regards, Søren Mikkelsen -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUwOVBAAoJECUE7rt2jWDwmKIH/RxqtwTf3WyMelI6BonAIraf BMF+Y7l+BBXbHDrYiKSW2SDCLuGFrbTaZn95tmom3YXfXAruJQlfe6orOeqPqiBM 0bt1ryvKq5ZdOzeHHFxyJilgHcuCeEtN6LTs1+URvTS4+8N5mnplnzCIGDbTKjiX M43spWsVWg39vrqQAqQUADQBHiNR/wq5WjRUiFW9cDpAOiDRkz1kwWb/QFkpjjjl KCa7EP5nQOySBpLjuPwPFUXuKWs7jP3NIxD4Wmsc3huQnCqJcCuTZKTcuLwPa+Co PGsYwIyoNQM5k/pctCw5XVTkQrK8eFEW/YtEPAqqRp8jmkIaZYXLevLceIWMOqo= =xdd0 -END PGP SIGNATURE-
Re: [O] [bug] ox-taskjuggler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2015-01-21 14:31, John Hendy wrote: On Jan 21, 2015 7:09 AM, Søren Mikkelsen so...@aamikkelsen.dk mailto:so...@aamikkelsen.dk wrote: On 2015-01-20 22:00, Nicolas Goaziou wrote: Hello, Søren Mikkelsen s...@iha.dk mailto:s...@iha.dk writes: I'm trying to use the taskjuggler exporter for getting an overview of my project, and it seems to be straight forward if you know a bit about Taskjuggler. However, tasks that are scheduled org-mode like, i.e., *** TODO My task SCHEDULED: 2015-01-27 Tue don't appear in the report. But, if I add a START property it will appear. *** TODO My task 2 :PROPERTIES: :start:2015-03-01 :END: I suspect it has something to do with l462-470: (defun org-taskjuggler-get-start (item) Return start date for task or resource ITEM. ITEM is a headline. Return value is a string or nil if ITEM doesn't have any start date defined. (let ((scheduled (org-element-property :scheduled item))) (or (and scheduled (org-timestamp-format scheduled %Y-%02m-%02d)) (and (memq 'start org-taskjuggler-valid-task-attributes) (org-element-property :START item) I'm not that experienced in elisp, so I hope someone can help me. There is no bug in the snippet shown. ox-taskjuggler just doesn't use SCHEDULED to set start property for tasks. However, it will use SCHEDULED to set the start date for the project. Note that I don't use Taskjuggler, so I don't know if this is the right behaviour or not. Regards, According to the org mode docs, assigning the start of a task should be possible both ways: http://orgmode.org/worg/exporters/taskjuggler/ox-taskjuggler.html#sec-5 Or am I misinterpreting the docs? Well, I wrote that , so you may be correctly interpreting docs written by someone who misunderstood! Perhaps the SCHUDULED property is just for the main project container. I don't see it actually used in any examples? No, not other than the task example I was referring to. Sorry if the confusion was my fault! John -- Best regards, Søren Mikkelsen It would, however, make sense to be able to scheduled tasks where interpreted as the start time, if the org-file is used for more than just generating the report. - -- Best regards, Søren Mikkelsen -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUwKYOAAoJECUE7rt2jWDwZisH/RgMvuzGu8gef7Yw3474yjkV CIVf1D+DNXQKPv0R596hYhf8GrvSWw87+OvYtsDdcXJ+ueDxycPgrNy+rQbnGBvO UUjla1QMNtIXMHvRB232cZ91hL50CCI5Mgx5k67PRU9shvfJIA/b0KouZmrmyMna uUm16IaH3vWVNm/BrQJJi86jhz6uBqF9NBmaefoZxIYd8HAJLg1iQGMaDCxvhwLq xzQtfQAlUxkVi+rzOwOuYk9U11ixMPzm8h8XFTNo+Uvj8GyVMIs4+ZFRqwQJG7nk PC/9K4SXcOuBprZZTXX4Y4YKJiSJ6qRH+omjB7TXKtDYK6Atlh4egkw33hyxoak= =qAfS -END PGP SIGNATURE-
Re: [O] [bug] ox-taskjuggler
On 2015-01-20 22:00, Nicolas Goaziou wrote: Hello, Søren Mikkelsen s...@iha.dk writes: I'm trying to use the taskjuggler exporter for getting an overview of my project, and it seems to be straight forward if you know a bit about Taskjuggler. However, tasks that are scheduled org-mode like, i.e., *** TODO My task SCHEDULED: 2015-01-27 Tue don't appear in the report. But, if I add a START property it will appear. *** TODO My task 2 :PROPERTIES: :start:2015-03-01 :END: I suspect it has something to do with l462-470: (defun org-taskjuggler-get-start (item) Return start date for task or resource ITEM. ITEM is a headline. Return value is a string or nil if ITEM doesn't have any start date defined. (let ((scheduled (org-element-property :scheduled item))) (or (and scheduled (org-timestamp-format scheduled %Y-%02m-%02d)) (and (memq 'start org-taskjuggler-valid-task-attributes) (org-element-property :START item) I'm not that experienced in elisp, so I hope someone can help me. There is no bug in the snippet shown. ox-taskjuggler just doesn't use SCHEDULED to set start property for tasks. However, it will use SCHEDULED to set the start date for the project. Note that I don't use Taskjuggler, so I don't know if this is the right behaviour or not. Regards, According to the org mode docs, assigning the start of a task should be possible both ways: http://orgmode.org/worg/exporters/taskjuggler/ox-taskjuggler.html#sec-5 Or am I misinterpreting the docs? -- Best regards, Søren Mikkelsen
[O] [bug] ox-taskjuggler
I'm trying to use the taskjuggler exporter for getting an overview of my project, and it seems to be straight forward if you know a bit about Taskjuggler. However, tasks that are scheduled org-mode like, i.e., *** TODO My task SCHEDULED: 2015-01-27 Tue don't appear in the report. But, if I add a START property it will appear. *** TODO My task 2 :PROPERTIES: :start:2015-03-01 :END: I suspect it has something to do with l462-470: (defun org-taskjuggler-get-start (item) Return start date for task or resource ITEM. ITEM is a headline. Return value is a string or nil if ITEM doesn't have any start date defined. (let ((scheduled (org-element-property :scheduled item))) (or (and scheduled (org-timestamp-format scheduled %Y-%02m-%02d)) (and (memq 'start org-taskjuggler-valid-task-attributes) (org-element-property :START item) I'm not that experienced in elisp, so I hope someone can help me. Best regards, Søren
[O] Break a line in org-mode
I usually have some #+LaTeX_HEADER: entries in my org-mode files where some of them are macros. These lines can be rather long so I have to type in #+LaTeX_HEADER: multiple times for breaking the line to a decent level. Is there a way of breaking a line when it is export options (or a regular comment in org-mode)? -- Søren Mikkelsen
Re: [O] Break a line in org-mode
On 2013-07-03 10:21, Nick Dokos wrote:
Søren Mikkelsen s...@iha.dk writes:
I usually have some #+LaTeX_HEADER: entries in my org-mode files where
some of them are macros. These lines can be rather long so I have to
type in #+LaTeX_HEADER: multiple times for breaking the line to a decent
level.
Is there a way of breaking a line when it is export options (or a
regular comment in org-mode)?
Wouldn't it be better to put the macros in a separate file (say
mymacros.sty) and use
#+LATEX_HEADER: \usepackage{mymacros}
? Less clutter in the org file and if the macros are more generally useful,
you can make it available, say by moving it to your personal texmf
directory (mine is at ~/.texmf-var/tex/latex but ymmv) and running texhash.
Well, I would like it to be in one file. If I, for instance, want to
have long author list, it is not possible to do without having all the
names on one line.
I through maybe that there was a newline symbol, like in python or matlab.
--
Søren
Re: [O] Break a line in org-mode
On 2013-07-03 11:01, Rasmus wrote:
Søren Mikkelsen s...@iha.dk writes:
I usually have some #+LaTeX_HEADER: entries in my org-mode files where
some of them are macros. These lines can be rather long so I have to
type in #+LaTeX_HEADER: multiple times for breaking the line to a decent
level.
Is there a way of breaking a line when it is export options (or a
regular comment in org-mode)?
No. But maybe you could do
#+LATEX_HEADER: \input{pre}
#+BEGIN_SRC LATEX :tangle pre.tex
\usepackage{mypackage}
#+END_SRC
Or you could make a new Org-Latex, see the variable org-latex-classes
if you have the same problem often.
Some people entertained the idea of writing sty and/or cls files
recently on this list. If you use the same macros all over perhaps
you should pack them as a sty or the very least as an external tex
file, I guess.
Alternatively, use the function string-rectangle. In the following
example, place your mark at the first `|', click C-Space, move to the
second `|' click C-x r t LATEX_HEADER RET.
|\usepackage{pac1}
\usepackage{pac1}
|\usepackage{pac1}.
Hope it helps.
–Rasmus
Okay, just thought that there might be a symbol for that. That could
have been nice.
But thanks for the suggestions.
--
Søren
Re: [O] XeLaTeX and the new exporter
Hi Chris I asked the question a couple of weeks ago. Take a look at the hook: org-export-before-parsing-hook It worked for me. Best regards Søren On 2013-05-07 17:42, Christopher Witte wrote: Hi all, I had export working using XeLaTeX using the instructions from the FAQ http://orgmode.org/worg/org-faq.html#using-xelatex-for-pdf-export (with some slight modifications), but after upgrading to the new export it isn't working. It appears the hook org-export-latex-after-initial-vars-hook isn't defined anymore. Any advice on what I need to change to get it to work? Thanks Chris.
[O] [New Exporter] org-export-latex-after-initial-vars-hook
Hello, I have just upgraded to the Org 8.0. Nice work! :) But I have a problem with the exporter: I have modified by org-exporter to export latex-files with the xelatex compiler. The implementation uses the org-export-latex-after-initial-vars-hook-hook to reconfigure the default process, however, this hook seems to be deleted and I'm not able to find equivalent hook. Cheers, Søren
Re: [O] Export of subtree does not include header
John Hendy jw.he...@gmail.com writes: On Fri, Jan 18, 2013 at 4:35 AM, Søren Aagaard Mikkelsen so...@aamikkelsen.dk wrote: I have used orgmode for a while, but hasn't used any of its advanced features that much. I'm currently writing a minutes report and what to export a specific subtree, e.g. * Minutes from 2013-01-11 * Minutes from 2013-01-18--- Want to export this only Then I press C-c @, which marks the subtree, and then I press C-c C-e and export it as a pdf-document. The problem is that I want the top section to remain the same, i.e. Minutes from 2013-01-18 is the top section and the others to be subsection of that. Currently, it surely exports the right subtree but the top-section is not Minutes from 2013-01-18, but the bullet after that. I get the same behavior. Does it need to export it in a tree like format, or would you be okay with your top level headline (the one you want exported, but which is currently not) being the actual title of the document? Or is that what you're currently getting. This is what I'm currently getting. I want to have a document with all my minutes and my idea is, that I should be able to export one heading for each meeting, so I can prepare an agenda and afterwards fill in the outcome of the discussions. With default settings (org-export-latex-title-command \\maketitle), I get the top-most headline of the marked subtree as my document title and the next level headline as the first section. Is this what you're getting, or the top headline text isn't showing up in the document at all? Yes, I get the same result. I don't want subsections to be promoted to sections when I export the org-markup. Is that possible? If having it as the title would work, you would get: -- [centered]Minutes from 2013-01-18[centered] A bit of white space Any text directly under Minutes from 2013-01-18... [section] The first headline under Minutes from 2013-01-18 [section] text under that headline [section 2] The second headline under Minutes from 2013-01-18 [section] text under that headline -- If it's just the centered text/bit white space gap you don't like, I'm sure there's LaTeX header arguments you could put in your Org document or setupfile to left-align the title and remove the space. What do you think of that option? Also... just to save you *one* keystroke, you can put your cursor on the headline of interest and do =C-e 1 p=, which I think does the same as marking the whole subtree with =C-c @ C-e p=. John Thanks for the keystroke advice. Love a bit of emacs-hints :)
Re: [O] Org-mode using enumerate properties to export to LaTeX
On 2011-09-12 11:30, Eric S Fraga wrote:
Søren Mikkelsensorenaamikkel...@gmail.com writes:
[...]
Yes, it works perfectly when I export it into latex (and thank you for
that). Just wondering if it was possible to do something similar
within org-mode; a enumerate list with a prefix, e.g.:
R1. One
R2. Two
Ah, now I understand. The answer is no and I imagine it would be
difficult to define a regular expression to match such cases without
catching all kinds of lines that were not intended to be lists (e.g. the
last word in a sentence that happens to end up at the start of the
line...).
However, latex does allow you to manually over-ride any item
label/number by simply specifying your own in square brackets. e.g.
- [R1] one
- [R2] two
Org passes these through to the latex properly so this should do what
you want but obviously you won't have any automated procedure for
generating these labels.
This is also a latex related question, however I think it extents the
previous question. How to I make my counter of the enumeration-list
start at a specific position. Like
1. Test
2. of
Now I have something between the two enumerations
3. counters
4. in a
5. enumeration environment
In latex I would insert \setcounter{enumi}{3} after starting a
enumeration environment.
--
/aagaard
[O] Org-mode using enumerate properties to export to LaTeX
I am currently struggling with enumerating my numbered list with a
prefix. In org-mode I have
1. This
2. is
3. a
4. numbered
5. list
In my LaTeX export I like to have it look like
R1. This
R2. is
R3. a
R4. numbered
R5. list
In my latex-document I would do something like this:
\documentclass{article}
\usepackage{enumerate}
\begin{document}
\begin{enumerate}[{\bfseries R1.}]
\item This
\item is
\item a
\item numbered
\item list
\end{enumerate}
\end{document}
--
aagaard
Re: [O] Org-mode using enumerate properties to export to LaTeX
On 2011-09-11 15:18, Eric S Fraga wrote:
Søren Mikkelsensorenaamikkel...@gmail.com writes:
I am currently struggling with enumerating my numbered list with a
prefix. In org-mode I have
1. This
2. is
3. a
4. numbered
5. list
Try putting the line
#+latex: \renewcommand{\theenumi}{R\arabic{enumi}}
before the start of the list. This changes how latex outputs the first
level (i) enumeration counter. Set it back afterwards to the same thing
*without* the =R= to get the default behaviour.
This is obviously a latex issue not specific to org. For these cases,
there are some very good resources online. e.g.
https://secure.wikimedia.org/wikibooks/en/wiki/LaTeX/
and my all time favourite:
http://www.tex.ac.uk/tex-archive/info/visualFAQ/visualFAQ.pdf
one of the best things about org as a writing mode is that you still
have access to most latex (and other export target) features in a
straightforward manner!
HTH,
eric
Thanks, I thought something like renewing a command could do the job.
However it could be nice, if it was possible to export a list with a
generic prefix on the lists.
---
/aagaard
Re: [O] Org-mode using enumerate properties to export to LaTeX
On 2011-09-11 21:06, Eric S Fraga wrote:
Søren Mikkelsensorenaamikkel...@gmail.com writes:
On 2011-09-11 15:18, Eric S Fraga wrote:
Søren Mikkelsensorenaamikkel...@gmail.com writes:
I am currently struggling with enumerating my numbered list with a
prefix. In org-mode I have
1. This
2. is
3. a
4. numbered
5. list
Try putting the line
#+latex: \renewcommand{\theenumi}{R\arabic{enumi}}
before the start of the list. This changes how latex outputs the first
level (i) enumeration counter. Set it back afterwards to the same thing
*without* the =R= to get the default behaviour.
This is obviously a latex issue not specific to org. For these cases,
there are some very good resources online. e.g.
https://secure.wikimedia.org/wikibooks/en/wiki/LaTeX/
and my all time favourite:
http://www.tex.ac.uk/tex-archive/info/visualFAQ/visualFAQ.pdf
one of the best things about org as a writing mode is that you still
have access to most latex (and other export target) features in a
straightforward manner!
HTH,
eric
Thanks, I thought something like renewing a command could do the
job. However it could be nice, if it was possible to export a list
with a generic prefix on the lists.
---
/aagaard
I'm not sure what you mean? Doesn't what I posted above do the job?
This is the standard latex means of doing this, at least with the
default latex enumeration environment.
You may wish to check out other list environments; there are a few out
there, e.g. paralist. However, I am not sure how the latex exporter
could be configured to pass the extra information that some of these
need to achieve what you want.
HTH,
eric
Yes, it works perfectly when I export it into latex (and thank you for
that). Just wondering if it was possible to do something similar within
org-mode; a enumerate list with a prefix, e.g.:
R1. One
R2. Two
--
---
Søren Mikkelsen
