[O] Buffer-local override of org-latex-title-command?
Hi,
I've decided to write my next research article using org's LaTeX
export. The first problem: the journal mandates one column for the
title/author heading and the abstract, while the remainder of the text
should be in two columns.
TeX FAQ recommends the following [1]:
\documentclass[twocolumn]{article}
...
\begin{document}
... % \author, etc
\twocolumn[
\begin{@twocolumnfalse}
\maketitle
\begin{abstract}
...
\end{abstract}
\end{@twocolumnfalse}
]
I can get very near to that this way:
#+LaTeX: \twocolumn[ \begin{@twocolumnfalse} \maketitle
#+BEGIN_abstract
This is my abstract. This is my abstract.
This is my abstract. This is my abstract.
#+END_abstract
#+LaTeX: \end{@twocolumnfalse} ]
... followed by outline headings marking sections.
The problem is that the org-latex-title-command variable places
\maketitle before the \twocolumn[...] bit. I realize I can customize
the variable and make it an empty string, but I'm not sure I want this
to take effect for every document I export to LaTeX.
Is there a way to clear this variable that is local to the buffer?
hjh
[1] http://www.tex.ac.uk/cgi-bin/texfaq2html?label=onecolabs
[O] Exporting an article to a (very) specific formatting template
Actually, let me take a few steps back from my specific question about the title command. There are some other workflow questions that might make that question redundant. This journal (for some reason unknown to me) has designed the publication format in MS Word, and there are some specific requirements. So I have a couple of choices: - Export to LaTeX, and try to reproduce their layout (likely with a new document class based on article). That's a chunk of work, but they also confirmed that I could send PDF as long as it follows the style guidelines. - Export to ODT. This is probably simpler for setup -- I'd probably just need to change some of the names of paragraph or character styles in their template so that org can find them for section headings, abstract etc. But... there is more risk of the formatting breaking. If I send .odt, MS Word might choke on it, or similar if I resave my .odt as .docx. (The word online is that LibreOffice does not do well saving docx.) Or, export to ODT and let LibreOffice turn that into a PDF. I hesitate to do this, when LaTeX is a far superior typesetter. (But, tweaking all the formatting details in LaTeX is quite likely to give me some more gray hairs...) Advice? Thanks -- hjh
Re: [O] [Worg] [New Exporter] invalid time specification
Hello, Jay Kerns gjkerns...@gmail.com writes: I've noticed people mentioning on the list that there is a problem with Worg not publishing, something about an invalid time specification. Having been publishing Worg locally myself, I noticed that I was getting a similar error when it came time to construct the sitemap.org. This should be fixed. Thanks for reporting it. Regards, -- Nicolas Goaziou
Re: [O] [PATCH] export to various flavors of (X)HTML
Hello, Eric Abrahamsen e...@ericabrahamsen.net writes: Tangential coding question: I've noticed that setting HTML_HTML5_FANCY to nil at the top of the export file results in `(plist-get info :html-html5-fancy)' returning the string nil, ie true. Not right, obviously, and it makes it impossible to set it to 'nil per-file if the global value is 't. Am I handling this wrong? Value for regular keywords is always a string. You can check for the empty string instead. You can also add an item in OPTIONS, since those are read and, thus, can have a symbol as value. Regards, -- Nicolas Goaziou
[O] Bug: org-archive-subtree should not include statitics counters for :ARCHIVE_OLPATH: [8.0.1 (release_8.0.1-10676-gd887b9 @ /home/mrb/dev/emacs/packages/org-mode/lisp/)]
When using org-archive-subtree, any statistic counters present in the header will be copied to the :ARCHIVE_OLPATH: property. Example: The property is set to: ':ARCHIVE_OLPATH: Development [22%] [82/358]/Openobject tasks/OpenERP 7.x Interne HSD implementatie [31%] [35/112]' when the hierarchy is * Development [22%] [82/358] ** Openobject tasks *** OpenERP 7.x Interne HSD implementatie [31%] [35/112]' These statistics should not be copied to the property. Emacs : GNU Emacs 24.3.4 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.0) of 2013-03-30 on mrb Package: Org-mode version 8.0.1 (release_8.0.1-10676-gd887b9 @ /home/mrb/dev/emacs/packages/org-mode/lisp/) -- Marcel van der Boom -- http://hsdev.com/mvdb.vcf HS-Development BV-- http://www.hsdev.com We use bitcoin! -- http://bitcoin.org
[O] Problems with agenda search and restiction enabled
Hello, I want to perform an agenda search with a restriction to a subtree. - C-c C-x on the subtree - org-agenda s word I get the follwing backtrace Debugger entered--Lisp error: (args-out-of-range 85127 226827) narrow-to-region(#marker at 85127 in EmacsNotes.org #marker at 226827 in EmacsNotes.org) (if org-agenda-restrict (narrow-to-region org-agenda-restrict-begin org-agenda-restrict-end) (widen)) ... rest snipped ... The values in args out of range are valid for point in the file EmacsNotes.org. When I start emacs -Q and minmal setup for org the error does not occur. I did a little debugging with emacs -Q and found out that the error occurs when I set the variable =org-agenda-text-search-extra-files= to some files. Now not all files in this variable trigger the error. My elisp is limited as are my debugging skills. Can someone direct my how to proceed further. This is on Win7 with emacs 24.2 and Org-mode version 8.0.1 (release_8.0.1-4-g148f95 @ c:/daten/users/DE_hts2fe/git/org-mode/lisp/) Thanks a lot. -- Mit freundlichen Grüßen / Best regards Thomas Holst DGS-EC/ESE4 Tel. +49 (711) 811-40681 PC-Fax +49 (711) 811-5182208
Re: [O] [Worg] [New Exporter] invalid time specification
On Mon, Apr 29, 2013 at 3:41 AM, Nicolas Goaziou n.goaz...@gmail.com wrote: This should be fixed. Thanks for reporting it. Confirmed - thank you. -- Jay
Re: [O] Buffer-local override of org-latex-title-command?
Aloha James, James Harkins jamshar...@gmail.com writes: The problem is that the org-latex-title-command variable places \maketitle before the \twocolumn[...] bit. I realize I can customize the variable and make it an empty string, but I'm not sure I want this to take effect for every document I export to LaTeX. Does an empty #+TITLE: do what you want? hth, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Buffer-local override of org-latex-title-command?
On Apr 29, 2013 8:23 PM, Thomas S. Dye t...@tsdye.com wrote: James Harkins jamshar...@gmail.com writes: The problem is that the org-latex-title-command variable places \maketitle before the \twocolumn[...] bit. I realize I can customize the variable and make it an empty string, but I'm not sure I want this to take effect for every document I export to LaTeX. Does an empty #+TITLE: do what you want? No, because I do need the title, but inside the \twocolumn part. I wouldn't be able to submit the manuscript with no title. hjh
Re: [O] Buffer-local override of org-latex-title-command?
Aloha James, James Harkins jamshar...@gmail.com writes: On Apr 29, 2013 8:23 PM, Thomas S. Dye t...@tsdye.com wrote: James Harkins jamshar...@gmail.com writes: The problem is that the org-latex-title-command variable places \maketitle before the \twocolumn[...] bit. I realize I can customize the variable and make it an empty string, but I'm not sure I want this to take effect for every document I export to LaTeX. Does an empty #+TITLE: do what you want? No, because I do need the title, but inside the \twocolumn part. I wouldn't be able to submit the manuscript with no title. If you use asynchronous export you can put this in the init.el initialization file: (setq org-latex-title-command ) hth, Tom -- T.S. Dye Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
[O] Repeating tasks
Hi there, Does anybody knows how to setup org to schedule repeated task between a specified range of dates. For example, suppose I plan to work on a grant proposal between 10 am - 1 pm every other day from May 1 to June 1, how would I do this ? My current practice is specify the start date with a repeater (in this case +2d), and then delete task when the deadline has passed. It though it would be more efficient I could assign a date range rather than just the start date. Cheers, M
Re: [O] Buffer-local override of org-latex-title-command?
Hello, James Harkins jamshar...@gmail.com writes: On Apr 29, 2013 8:23 PM, Thomas S. Dye t...@tsdye.com wrote: James Harkins jamshar...@gmail.com writes: The problem is that the org-latex-title-command variable places \maketitle before the \twocolumn[...] bit. I realize I can customize the variable and make it an empty string, but I'm not sure I want this to take effect for every document I export to LaTeX. Does an empty #+TITLE: do what you want? No, because I do need the title, but inside the \twocolumn part. I wouldn't be able to submit the manuscript with no title. Try: #+BIND: org-latex-title-command This assumes `org-export-allow-bind-keywords' is non-nil. Regards, -- Nicolas Goaziou
Re: [O] Call for volunteer -- managing the publication setup wrt orgmode.org/worg and orgmode.org
Hi Marc, that's great. Jay is also okay to help here. It's better to have one person in charge and another one as a backup, so I suggest to announce you will take this in charge and have Jay to help you in case. Does it sound good to you? Thanks! -- Bastien
Re: [O] runaway argument exporting: * _is_?
Nicolas,
Isn't it a LaTeX limitation? What would the correct LaTeX code be in
that case?
this seems to be something in beamer rather than inside vanilla latex.
for example, the following foo.tex file fails:
\documentclass{beamer}
\begin{document}
\section{\underline{is}?}
\end{document}
but, changing to \documentclass{article} makes things work.
i'm not a beamer expert, so i can't say what is going on.
cheers, Greg
Re: [O] Exporting an article to a (very) specific formatting template
James Harkins jamshark70 at gmail.com writes: Actually, let me take a few steps back from my specific question about the title command. There are some other workflow questions that might make that question redundant. This journal (for some reason unknown to me) has designed the publication format in MS Word, and there are some specific requirements. So I have a couple of choices: - Export to LaTeX, and try to reproduce their layout (likely with a new document class based on article). That's a chunk of work, but they also confirmed that I could send PDF as long as it follows the style guidelines. - Export to ODT. This is probably simpler for setup -- I'd probably just need to change some of the names of paragraph or character styles in their template so that org can find them for section headings, abstract etc. But... there is more risk of the formatting breaking. If I send .odt, MS Word might choke on it, or similar if I resave my .odt as .docx. (The word online is that LibreOffice does not do well saving docx.) Or, export to ODT and let LibreOffice turn that into a PDF. I hesitate to do this, when LaTeX is a far superior typesetter. (But, tweaking all the formatting details in LaTeX is quite likely to give me some more gray hairs...) Advice? Thanks -- hjh I used both aproaches : - Usually I customize the org options (latex templates) to meet the requirements of the final document. It is convenient for me to stay in emacs. For the gray hairs, you do it once and thus you have minor modifications. - But sometimes when I work with other colleagues I need to have something more common, odt seems fine but as you mentioned you may have to add a final manual toutch to be sure your document can be modified by the others. Regards,
[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] Exporting large documents
Carsten Dominik wrote: Hi Achim, this is an interesting experiment, thank you! I think it would also be interesting to use elp to see which function are taking up the non-linear time. I did a bit of digging and here are the results. No potential fixes though. Taking the Introduction section of orgmanual.org and doubling it up so the buffer is 16x, 32x, 64x and 128x copies of the introduction and then running latex export having elp-instrumented the org package shows the following. There are a few instances of quadratic behaviour that contribute to the slowdown. Main culprit: Name times-called cumulative-time time-per-call org-export-data 10132 29.364160173 0.0028981603 org-export-data 20180 90.198301053 0.0044696878 org-export-data 40276 316.37200089 0.0078550998 org-export-data 80468 1155.4851323 0.0143595607 Less important but still a noticeable total runtime: org-element-map 1133 2.6814707420 0.0023666996 org-element-map 2285 10.799367732 0.0047262003 org-element-map 4589 43.787327887 0.0095418016 org-element-map 9197 173.27839595 0.0188407519 org-export-resolve-fuzzy-link 48 2.6659073480 0.0555397364 org-export-resolve-fuzzy-link 96 10.766515020 0.1121511981 org-export-resolve-fuzzy-link 192 43.725658059 0.2277378023 org-export-resolve-fuzzy-link 384 173.15348462 0.4509205328 org-latex-link 144 2.6730487589 0.0185628386 org-latex-link 288 10.783675007 0.0374433159 org-latex-link 576 43.768676906 0.0759872862 org-latex-link 1152 173.27176368 0.1504095170 Unimportant but still quadratic: org-export-get-headline-number 176 0.0036720380 2.086...e-05 org-export-get-headline-number 352 0.0154215390 4.381...e-05 org-export-get-headline-number 704 0.0636496679 9.041...e-05 org-export-get-headline-number 1408 0.2382477599 0.0001692100 org-babel-get-inline-src-block-matches 112 0.0174396369 0.0001557110 org-babel-get-inline-src-block-matches 224 0.0521645539 0.0002328774 org-babel-get-inline-src-block-matches 448 0.182069907 0.0004064060 org-babel-get-inline-src-block-matches 896 0.66889546 0.0007465351 org-babel-remove-result 112 0.0332858050 0.0002971946 org-babel-remove-result 224 0.0837776260 0.0003740072 org-babel-remove-result 448 0.2475016210 0.0005524589 org-babel-remove-result 896 0.8013491290 0.0008943628 org-babel-where-is-src-block-result 112 0.0320815769 0.0002864426 org-babel-where-is-src-block-result 224 0.081381881 0.0003633119 org-babel-where-is-src-block-result 448 0.2425831529 0.0005414802 org-babel-where-is-src-block-result 896 0.7915090309 0.0008833806 Cheers, Lawrence
Re: [O] Repeating tasks
Hi Marvin, Marvin Doyley marvin...@gmail.com writes: Hi there, Does anybody knows how to setup org to schedule repeated task between a specified range of dates. For example, suppose I plan to work on a grant proposal between 10 am - 1 pm every other day from May 1 to June 1, how would I do this ? My current practice is specify the start date with a repeater (in this case +2d), and then delete task when the deadline has passed. It though it would be more efficient I could assign a date range rather than just the start date. Cheers, M If I understand your situation correctly, you might take a look at Habits. If you mark them done, they will be rescheduled to the next date you specified. Roughly it should look like this: * TODO Work on proposal :SCHEDULED: 2013-05-01 Wed 22:00 .+2d :PROPERTIES: :STYLE: habit :END: But your are probably better off looking at the part of the manual regarding habits. Regards, Alex
Re: [O] Problems with agenda search and restiction enabled
Hi Thomas, Thomas Holst thomas.ho...@de.bosch.com writes: I want to perform an agenda search with a restriction to a subtree. - C-c C-x on the subtree - org-agenda s word I get the follwing backtrace Debugger entered--Lisp error: (args-out-of-range 85127 226827) narrow-to-region(#marker at 85127 in EmacsNotes.org #marker at 226827 in EmacsNotes.org) (if org-agenda-restrict (narrow-to-region org-agenda-restrict-begin org-agenda-restrict-end) (widen)) ... rest snipped ... This is now fixed in the maint branch of the Git repository. Thanks for reporting this! -- Bastien
Re: [O] Buffer-local override of org-latex-title-command?
Aloha Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Try: #+BIND: org-latex-title-command This assumes `org-export-allow-bind-keywords' is non-nil. I couldn't find a reference to this variable in the manual. I'd suggest replacing the word `Eventually' with the clause before the first comma in the paragraph below, or something like it. If the variable `org-export-allow-bind-keywords' is non-nil, Emacs variables can become buffer-local during export by using the BIND keyword. Its syntax is `#+BIND: variable value'. This is particularly useful for in-buffer settings that cannot be changed using specific keywords. All the best, Tom -- T.S. Dye Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
Re: [O] Buffer-local override of org-latex-title-command?
Hi Thomas, t...@tsdye.com (Thomas S. Dye) writes: I couldn't find a reference to this variable in the manual. I'd suggest replacing the word `Eventually' with the clause before the first comma in the paragraph below, or something like it. If the variable `org-export-allow-bind-keywords' is non-nil, Emacs variables can become buffer-local during export by using the BIND keyword. Its syntax is `#+BIND: variable value'. This is particularly useful for in-buffer settings that cannot be changed using specific keywords. Done, thanks. -- Bastien
Re: [O] Kill all items with specific tag to kill-ring.
On 2013-04-25, Bernt Hansen wrote: Oleksandr Gavenko gaven...@gmail.com writes: I want this feature in order to simplify precess of moving entries from job org-file to home org-file by marking entries with tag :HOME:... If all you want to do is move items why not use the agenda? Mark your entries with a tag, do an agenda search for that tag, mark all entries with m and move them using bulk refile with B r Great! I don't often use agenda so don't know about this feature. How can I select specific buffer/file (and only this buffer) for displaying/processing in agenda? -- Best regards!
Re: [O] [New Exporter] org-export-latex-after-initial-vars-hook
Hello, Søren Mikkelsen so...@aamikkelsen.dk writes: 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. Isn't it sufficient to customize `org-latex-pdf-process' so it uses xelatex? Regards, -- Nicolas Goaziou
Re: [O] Exporting large documents
Lawrence Mitchell writes: I did a bit of digging and here are the results. No potential fixes though. Thanks for beating me to it, that frees up quite some processor cycles on my end! :-) Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] Call for volunteer -- managing the publication setup wrt orgmode.org/worg and orgmode.org
Hi Jay, Great ! I am looking forward to work with you ! First task will probably be to see, how worgs publishing-mechanism fits together :-) best regards, Marc Am 29.04.2013 18:25, schrieb Jay Kerns: Hello there, On Mon, Apr 29, 2013 at 10:50 AM, Bastien b...@gnu.org wrote: Hi Marc, that's great. Jay is also okay to help here. It's better to have one person in charge and another one as a backup, so I suggest to announce you will take this in charge and have Jay to help you in case. Does it sound good to you? Thanks! I am writing to confirm that yes, I would be happy to serve as Marc's backup, as long as this is acceptable to him. Marc, if this is OK with you then full speed ahead! Please let me know if I may be of any assistance.
[O] org-babel-chomp: Symbol's function definition is void: org-reverse-string
Hello, I don't have full details, but some friend of mine installed Org from ELPA, and got problems. He did reinstall once again version 20130422 of Org and still gets: org-babel-chomp: Symbol's function definition is void: org-reverse-string Is it something know to anybody? Best regards, Seb -- Sebastien Vauban
[O] [new exporter] how can I export drawers?
Hello, I am going a little crazy here! I have an org document which I need to export to PDF using latex. Everything works just fine with the new exporter except for one thing: I cannot get it to export drawers. I have set org-export-with-drawers to t, I have set d:t in the OPTIONS line, I have defined org-latex-format-drawer-function as described in the documentation. None of this has made any difference. Now, having looked at the code, it almost seems that there is no such functionality? Grepping for org-export-with-drawers only brings up three lines in all of lisp/*.el, none of which does anything with this variable. Is there any way to export drawers (LOGBOOK in my case)? Many thanks, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_8.0.2-56-g09167e
Re: [O] Repeating tasks
org-habit is not what I am looking for. I would like to do something like * TODO write proposal Scheduled:2013-04-30 Tue 13:00-15:00 --2013-06-02 Mon +2d The idea is to repeat this task every other day from 2013-04-30 to 2013-06-02 (from 13:30 to 15:00) cheers M
Re: [O] org-babel-chomp: Symbol's function definition is void: org-reverse-string
Sounds like he has a mixed install running two different versions of Org-mode at once. The `org-reverse-string' functions *does* exist in the current version of Org-mode. Sebastien Vauban sva-n...@mygooglest.com writes: Hello, I don't have full details, but some friend of mine installed Org from ELPA, and got problems. He did reinstall once again version 20130422 of Org and still gets: org-babel-chomp: Symbol's function definition is void: org-reverse-string Is it something know to anybody? Best regards, Seb -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] Repeating tasks
Hi Marvin, Marvin Doyley m.doy...@rochester.edu writes: org-habit is not what I am looking for. I would like to do something like * TODO write proposal Scheduled:2013-04-30 Tue 13:00-15:00 --2013-06-02 Mon +2d The idea is to repeat this task every other day from 2013-04-30 to 2013-06-02 (from 13:30 to 15:00) cheers M Ok, then I think diary sexp should do the trick. Try the following: ** TODO 13:00-15:00 write proposal %%(and (org-block 2013 4 30 2013 6 2) (org-cyclic 2 2013 4 30)) Regards, Alex
Re: [O] [new exporter] how can I export drawers?
Eric S Fraga e.fr...@ucl.ac.uk writes: I am going a little crazy here! I have an org document which I need to export to PDF using latex. [not an answer, but rather a feature request] I would like to be able to export drawers to ASCII too, although, as Nicolas mentioned in an earlier thread, the ascii exporter currently does not handle this. IMO, every exporter should offer the option to export _all_ the info in an Org file (the backend might possibly able to digest). At the moment, when I want to share an Org-file as text with non Org-users, all I can do is save it as .txt file, which results in a complete, but rather unreadable output, expecially when there are many timestamps, tags and drawers involved. -- cheers, Thorsten
Re: [O] Collaborating with TODO lists and clocks.
Thanks for the reply Richard! Richard Lawrence richard.lawre...@berkeley.edu writes: Is there a reason you don't want any clock data to end up in the shared tasks.org? If not, one thing you could do is: 1) When claiming a task, each person uses a tag for their name (in addition to, or instead of, just changing the TODO state). Then that person owns the clock data for that task. 2) Then use the :tags option on a clock table to filter the clock data for just the tasks you personally have worked on; each person can have their own table (in tasks.org). That sounds like a good idea - thanks! I hadn't thought of using :tags on a clock table. I still worry if we'll find ourselves in a situation where more than one of us has clocked in some time on the same task. For example, often I clock into a task while I do the work of sub-dividing it into smaller tasks. And often when I'm actively working on a task, I'll create a sub-task of my current-clocked-task on the fly. It seems to me that if I continue with this sort of working practice, and attempt to collaborate with others who work similarly, then we might quickly find that it's not easy to describe a given task (or even subtask) as being owned by a single person. Again, perhaps my workflow is at fault, and I should be organising myself in a more principled way. And perhaps in practice I'll find that tasks do tend to be owned by just one person anyway. Thanks for the quick reply! Gareth. For example, suppose you have a task like: * TODO Frobnicate something You claim it by changing that to: * IN_PROGRESS Frobnicate something :gareth: Check that in, then start your clock in this tree. Somewhere else in the file, you have a clock table like: #+BEGIN: clocktable :maxlevel 3 :scope file :tags +gareth #+CAPTION: Gareth's working time on all tasks # ... #+END: which will show you the clock data for just the tasks you've worked on (i.e., are tagged in).
Re: [O] org-babel-chomp: Symbol's function definition is void: org-reverse-string
Eric, Eric Schulte wrote: I don't have full details, but some friend of mine installed Org from ELPA, and got problems. He did reinstall once again version 20130422 of Org and still gets: org-babel-chomp: Symbol's function definition is void: org-reverse-string Sounds like he has a mixed install running two different versions of Org-mode at once. The `org-reverse-string' functions *does* exist in the current version of Org-mode. I'll try to help him to remotely debug this, looking in that direction. Thanks! Best regards, Seb -- Sebastien Vauban
[O] [Taskjuggler] Status of exporter
Hi all The Taskjuggler Exporter has seen some major updates. We finally have a nice out-of-the-box experience with tj3, so please give it a spin. What's new? Thanks to Nicolas Goaziou the exporter has been ported to the new export engine. On top of that I added some features that have been requested and there are some pending issues that I'd like to get fixed, see below: Changes ═══ Process and open Previously the exporter just exported a tjp file (at least for tj3). Now there is a new command to process the exported tjp file with tj3 and open the reports in a browser. Dependency resolution against plain IDs ─── There was some discussion on the list about dependency resolution. A good way to express dependencies is to use the org-id module. This is now supported in that it resolves dependencies not only against task_id but also against the ID of a task. Default reports can use document title ── John Hendy proposed to create a possibility to integrate the document title in the default reports. This is now possible by specifying a %title in the default reports. See the doc string of `org-taskjuggler-default-reports'. Use both scheduled and start to determine project start ─── John Hendy again reported an problem that the project start was not using the scheduled info. This is now fixed. Misc bug fixes ── Nicolas Goaziou fixed a number of bugs and typos in the code. Pending ═══ Change mapping of DEADLINE property ─── The DEADLINE property is currently mapped to the end attribute in the tjp export. The end attribute gives tj3 an indication as to when a task should end. Also it has some influence on the scheduling policy (ALAP) which might not be what the user expects. IMHO this is not exactly the semantics of the DEADLINE property. A better fit would be the maxend attribute. For that reason I'd like to propose a backward incompatible change to map the DEADLINE property to the maxend attribute. Patch by Baptiste ─ This patch fixes some problems with milestones. However it depends on above change. Add the text nodes as a note It would make sense to export the text content of a headline as a tj3 note. The new export engine should make this possible. -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Exporting an article to a (very) specific formatting template
Dnia 2013-04-29, o godz. 07:22:23 James Harkins jamshar...@gmail.com napisał(a): Or, export to ODT and let LibreOffice turn that into a PDF. I hesitate to do this, when LaTeX is a far superior typesetter. (But, tweaking all the formatting details in LaTeX is quite likely to give me some more gray hairs...) What about using koma-script or memoir class? And you can always ask about some specific formatting problems on TeX.SE (they are very willing to help there provided that the asker actually made some effort himself first, like some *basic* rtfm or preparing a MWE). Advice? Thanks -- hjh hth -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Adam Mickiewicz University
[O] [org][gpg] Encrypt org-attachments?
Hi list, Is it currently possible to use gnupg to automatically encrypt/decrypt files attached using the org-attach feature? If not, would it be hard to implement? The org-crypt feature is great and I use it all the time to keep sensitive data in my reference file, but when I need to archive files (often scan of documents) I would also like to have the ability to automatically encrypt them when filing, and them decrypt them when using org-attach to open the file. Thanks, Marcelo.
Re: [O] Repeating tasks
Thanks, this is exactly what I was looking for cheers M I will give it a try cheers M On Apr 29, 2013, at 3:56 PM, Alexander Baier lexi.ba...@gmail.com wrote: Hi Marvin, Marvin Doyley m.doy...@rochester.edu writes: org-habit is not what I am looking for. I would like to do something like * TODO write proposal Scheduled:2013-04-30 Tue 13:00-15:00 --2013-06-02 Mon +2d The idea is to repeat this task every other day from 2013-04-30 to 2013-06-02 (from 13:30 to 15:00) cheers M Ok, then I think diary sexp should do the trick. Try the following: ** TODO 13:00-15:00 write proposal %%(and (org-block 2013 4 30 2013 6 2) (org-cyclic 2 2013 4 30)) Regards, Alex
[O] Orgmode 8.0.2: Possible bug in `org-insert-heading` when invoked at end of a heading with a property
Hello fellow Orgmode users, Have installed orgmode 8.0.2 last night, and loving it so far. Facing one issue (or change in behavior) though. This is on Emacs 24.3. Looks like M-RET (`org-insert-heading`), and it's equivalent M-S-RET (`org-insert-todo-heading`) are behaving a little erratically when invoked from the _end_ of a heading that has a property drawer. An example will perhaps help: With a heading _without_ any property drawer, such as: *** A Heading ^ ^ Beginning End If I invoke M-S-RET at the beginning or end of the heading, then I get the expected behavior, where I get a new item created as: *** - This is created if invoked from the _beginning_ of the line *** A Heading- The original heading *** - And this is created if invoked from the _end_ of the line However, if there is a _drawer_ on the heading, then the behavior when M-RET is invoked from the _end_ of the line is: *** A Heading with a Drawer :PROPERTIES: :CATEGORY: TEST :END: *** - The second item's outline ^^^ Note that the second item's outline got indented, and has leading spaces (indented?) This is inconsistent with the behavior in earlier versions of Orgmode. Not sure if this is a bug (since there seems to be new functionality such as C-u C-u M-RET to add a new item at end of the parent's subtree in version 8.0). Thanks, -- Anupam
Re: [O] Buffer-local override of org-latex-title-command?
On Apr 29, 2013 10:08 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: Try: #+BIND: org-latex-title-command This assumes `org-export-allow-bind-keywords' is non-nil. Oh, ok, I thought I'd tried something like that but I guess I didn't get all the moving parts in the right place. Thanks! hjh
Re: [O] Collaborating with TODO lists and clocks.
Hi Gareth, Gareth Smith g...@doc.ic.ac.uk writes: I hadn't thought of using :tags on a clock table. I still worry if we'll find ourselves in a situation where more than one of us has clocked in some time on the same task. Yes, I agree this might not be optimal, for that case in particular. One nice thing about this use of tags is that you have a representation of when more than one person is working on a task, but that makes the clock less useful, as it can no longer represent an individual's working time without some effort to separate the clocks of the different owners. For example, often I clock into a task while I do the work of sub-dividing it into smaller tasks. And often when I'm actively working on a task, I'll create a sub-task of my current-clocked-task on the fly. It seems to me that if I continue with this sort of working practice, and attempt to collaborate with others who work similarly, then we might quickly find that it's not easy to describe a given task (or even subtask) as being owned by a single person. So one problem case is where you own a task, but someone else owns one of its subtasks, e.g.: == * Clock tables #+BEGIN: clocktable :maxlevel 2 :scope file :tags +gareth #+CAPTION: Clock summary at [2013-04-29 Mon 18:25] | Headline | Time | | |++--| | *Total time* | *3:05* | | |++--| | TODO Task 1| 3:05 | | | \__ TODO Subtask 1 || 1:05 | | \__ TODO Subtask 2 || 1:00 | #+END: #+BEGIN: clocktable :maxlevel 2 :scope file :tags +john #+CAPTION: Clock summary at [2013-04-29 Mon 18:17] | Headline | Time | | |++--| | *Total time* | *1:05* | | |++--| | TODO Task 1| 1:05 | | | \__ TODO Subtask 1 || 1:05 | #+END: * TODO Task 1:gareth: CLOCK: [2013-04-29 Mon 18:15]--[2013-04-29 Mon 19:15] = 1:00 ** TODO Subtask 1 :john: CLOCK: [2013-04-29 Mon 18:15]--[2013-04-29 Mon 19:20] = 1:05 ** TODO Subtask 2:gareth: CLOCK: [2013-04-29 Mon 16:16]--[2013-04-29 Mon 17:16] = 1:00 == Notice that Gareth gets credit for John's time on Subtask 1, because Gareth owns Task 1. You can avoid this particular gotcha in (at least) two ways: 1) Remove the :gareth: tag on task 1 and move the clock time to subtask 2 (more generally, ownership tags and clock times should only appear at the lowest level of the task tree). Maybe this makes the most sense, but it slows down the worflow a bit and is hard to enforce, etc. 2) Use a tag filter like +gareth-john to build the clock table (more generally, the clock table for each person should exclude tags for all the others). This prevents double counting and is easy to enforce, but if any tasks have more than one owner, no one will get credit for their clock times. Again, perhaps my workflow is at fault, and I should be organising myself in a more principled way. And perhaps in practice I'll find that tasks do tend to be owned by just one person anyway. Yeah, it's a hard problem with no general solution that I can see. The best thing is just to figure out what constraints you're willing to put on your workflow, given what Org allows you to do. Hope that's helpful! Best, Richard
Re: [O] Exporting an article to a (very) specific formatting template
mohamed mohamed.hibti at gmail.com writes: I used both aproaches : - Usually I customize the org options (latex templates) to meet the requirements of the final document. It is convenient for me to stay in emacs. For the gray hairs, you do it once and thus you have minor modifications. - But sometimes when I work with other colleagues I need to have something more common, odt seems fine but as you mentioned you may have to add a final manual toutch to be sure your document can be modified by the others. Ok, based on this and Marcin's comments, I'll do it the LaTeX way (which was my first choice anyway). Naturally, I'm using org to keep a TODO list of the formatting details I need to match... Thanks. hjh
Re: [O] How could I configure an export directory?
On Thu, 25 Apr 2013 11:53:16 -0500 John Hendy jw.he...@gmail.com wrote: On Thu, Apr 25, 2013 at 10:51 AM, Manfred Lotz manfred.l...@arcor.de wrote: Hi there, When I export to pdf (involving LaTeX), odt or whatever I would like all those files (including temporary files) to reside in a special directory, say ~/org/exportdir Looks like this has come up before: - http://stackoverflow.com/questions/9559753/emacs-org-mode-export-to-another-directory - http://lists.gnu.org/archive/html/emacs-orgmode/2012-03/msg00264.html I tried both (for pdf and html) but to no avail. Looking into ox-latex.el it seems that this is just not possible at this point in time as pdflatex's --output-directory parameter has a value %o which is just the base directory of the file. -- Manfred
