Re: [O] Scientific papers related to Org-mode

2012-04-10 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/04/12 19:30, Eric Schulte wrote:
 Hi Karl,
 
 I think the Org-mode manual is also citable.

Never thought about that - good to know.

Why not put that into org? e.g. R has a function citation(), which returns the 
bibtex for citing R
or packages.

I think it would be very useful to have a similar functionality in org - 
similar to show version
in the Documentation, a Show citation entry which always prints the most 
recent citation which
can be used in publications?
I think it could give org even more publicity.

Cheers,

Rainer

 
 @book{dominik10:_org_mode_refer_manual, author =   {Carsten Dominik}, 
 title ={The
 \pkg{Org-Mode} 7 Reference Manual: Organize Your Life with GNU Emacs}, 
 publisher ={Network
 Theory}, year = 2010, address =  {UK}, note = {with 
 contributions by David
 O`Toole, Bastien Guerry, Philip Rooke, Dan Davison, Eric Schulte, and Thomas 
 Dye} }
 
 Best,
 
 Bastien b...@gnu.org writes:
 
 Hi Karl,
 
 Karl Voit devn...@karl-voit.at writes:
 
 Is there any other important paper I missed?
 
 Check: http://orgmode.org/fr/org-mode-documentation.html
 
 There are these two other publications:
 
 Schulte, E.; Davison, D.; Active Documents with Org-Mode, Computing in 
 Science  Engineering,
 Vol. 13, Issue 3, May-June 2011.
 
 Delescluse M., Franconville R., Joucla S., Lieury T. and Pouzat C., Making 
 neurophysiological
 data analysis reproducible: Why and how?, Journal of Physiology-Paris, N°0, 
 2011.
 
 HTH,
 


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys.
(Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+D53MACgkQoYgNqgF2egpXhQCeO0QDjmufKvsEpUEMC/CSvvMb
EDwAn3R45z5UU1cg/N5SFnN1ejNsKQkD
=o2ox
-END PGP SIGNATURE-



Re: [O] layout org-babel menu WAS: About org-babel menu

2012-04-10 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/04/12 23:51, Eric Schulte wrote:
 Torsten Wagner torsten.wag...@gmail.com writes:
 
 Hi,
 
 for me the biggest trouble with babel is to remember the possible keywords 
 in the header
 for different languages. There were a lot of ongoing syntax change which did 
 not make it
 easier for me to remember all this. Thus a menu which is organised by 
 languages offering all
 possible settings for each language would be very helpful. | Python || | 
  export - code -
 result - both - none || |  tangle - no - yes- filename |   | |  result - 
 value - output |
 | | ... | ...
 
 Not sure how effectual this would be in a main menu. It would be definitely 
 awesome in a
 context menu
 
 That would be (copied from worg) [*] indicates cursor position
 
 #+NAME: factorial #+BEGIN_SRC haskell [*] :results silent :exports code :var 
 n=0
 
 a context menu would appear presenting all possible header arguments for 
 haskell
 
 #+NAME: factorial #+BEGIN_SRC haskell :results [*] :exports code :var n=0
 
 a context menu presenting all possible values for the header argument 
 :results in haskell I
 guess that together with the possibility to call this menu by keyboard 
 strokes or
 alternatively show the same infos in the minibuffer would be a great win for 
 babel and it
 would make many questions here on the list unnecessary. Furthermore, any 
 change or extension
 in the syntax for a certain language would be directly reflected to the 
 end-user. E.g., If I 
 suddenly see the menu entry :exports 3dprint, I would be curious and check 
 it out on worg and
 the manual ;)
 
 Totti
 
 
 Hi,
 
 I've put together a first pass at such support for interactive header 
 argument look up.  Please
 evaluate this elisp code [1] in your *scratch* buffer, then in an Org-mode 
 buffer insert a code
 block like the following with the point at [*], and press tab.
 
 #+begin_src R :[*] :foo #+end_src
 
 You should see an auto-completion list showing which header arguments are 
 available and (for
 those with known arguments) which arguments may be specified.  This includes 
 language specific
 header arguments, i.e., the R code block above suggests about twice as many 
 possible header 
 arguments as an elisp block.  Note this expand on tab after : behavior is 
 active on
 #+headers: lines as well.
 
 This makes use of the `org-babel-common-header-args-w-values' variable which 
 holds header
 argument names and completions, as well as the 
 org-babel-header-arg-names:lang variables.
 
 Does this seem like a good interface?

That looks really good - and I already seen a few header arguments I was not 
aware of. I haven't
played a lot with it at the moment, but I would very much have it in org as 
soon as possible - any
chance of adding it so that more users can try it easily?

Thanks a lot - looks really good, and I would say that with an autocomplete 
like this, a menu
entry for header arguments (except help section) is not needed any more?

Cheers,

Rainer


 
 Is it missing any important functionality?
 
 Best,
 
 Footnotes: [1] ;; Add support for completing-read insertion of header 
 arguments after : 
 (defun org-babel-header-arg-expand () Call 
 `org-babel-enter-header-arg-w-completion' in
 appropriate contexts. (when (and (= (char-before) ?\:) 
 (org-babel-where-is-src-block-head)) 
 (org-babel-enter-header-arg-w-completion (match-string 2
 
 (defun org-babel-enter-header-arg-w-completion (optional lang) Insert 
 header argument
 appropriate for LANG with completion. (let* ((lang-headers-var (intern 
 (concat
 org-babel-header-arg-names: lang))) (lang-headers (when (boundp 
 lang-headers-var) (mapcar
 #'symbol-name (eval lang-headers-var (headers (append (mapcar 
 #'symbol-name
 org-babel-header-arg-names) lang-headers)) (header (org-completing-read 
 Header Arg: 
 headers)) (args (cdr (assoc (intern header) 
 org-babel-common-header-args-w-values))) (arg (when
 (and args (listp args)) (org-completing-read (format %s:  header) (mapcar 
 #'symbol-name (car
 args)) (insert (concat header   (or arg ))) (cons header arg)))
 
 (add-hook 'org-tab-first-hook 'org-babel-header-arg-expand)
 


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys.
(Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+D6c8ACgkQoYgNqgF2egpADACdEV42FKP0GzgsuvQmeEjHJ8d1
rWAAoImD7XHqmDlH5OCt0w9rLe0pq4K+
=ssL5
-END PGP SIGNATURE-



Re: [O] Scientific papers related to Org-mode

2012-04-10 Thread suvayu ali
On Tue, Apr 10, 2012 at 09:55, Rainer M Krug r.m.k...@gmail.com wrote:
 Why not put that into org? e.g. R has a function citation(), which returns 
 the bibtex for citing R
 or packages.

Nice idea, why not submit a patch? ;)

-- 
Suvayu

Open source is the future. It sets us free.



Re: [O] Scientific papers related to Org-mode

2012-04-10 Thread Karl Voit
* Bastien b...@gnu.org wrote:
 Bastien b...@gnu.org writes:

 Is there any other important paper I missed?

 Check: http://orgmode.org/fr/org-mode-documentation.html

 English: http://orgmode.org/org-mode-documentation.html
 Spanish: http://orgmode.org/es/org-mode-documentation.html
 Japanese: http://orgmode.org/ja/org-mode-documentation.html

Oh, cool.

Since the pages above are specific to Org-mode documentation, I do
think that the extra-Worg-page is still useful.

Maybe the documentation-pages can link the Worg-page so that there
is one central place to collect Org-mode related papers ...

-- 
Karl Voit




Re: [O] Scientific papers related to Org-mode

2012-04-10 Thread Bastien
Karl Voit devn...@karl-voit.at writes:

 * Bastien b...@gnu.org wrote:
 Bastien b...@gnu.org writes:

 Is there any other important paper I missed?

 Check: http://orgmode.org/fr/org-mode-documentation.html

 English: http://orgmode.org/org-mode-documentation.html
 Spanish: http://orgmode.org/es/org-mode-documentation.html
 Japanese: http://orgmode.org/ja/org-mode-documentation.html

 Oh, cool.

 Since the pages above are specific to Org-mode documentation, I do
 think that the extra-Worg-page is still useful.

 Maybe the documentation-pages can link the Worg-page so that there
 is one central place to collect Org-mode related papers ...

Sure.  Let's mention the most important references on orgmode.org (the
manual and the article about Babel), then list all references on Worg.

Thanks for taking care of this!

-- 
 Bastien



Re: [O] Scientific papers related to Org-mode

2012-04-10 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/04/12 10:57, suvayu ali wrote:
 On Tue, Apr 10, 2012 at 09:55, Rainer M Krug r.m.k...@gmail.com wrote:
 Why not put that into org? e.g. R has a function citation(), which returns 
 the bibtex for
 citing R or packages.
 
 Nice idea, why not submit a patch? ;)
 

Because I unfortunately have effectively no idea about elisp, only that it uses 
*many* brackets...

and I have at the moment =no time to learn it.

Cheers,

Rainer

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys.
(Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+D+RMACgkQoYgNqgF2egrDVQCfdGxjZh/nHpXBDXRxuTjhhwBF
Rx4AniO214za453eGbe+2Nb2EPGLxFvz
=GgQE
-END PGP SIGNATURE-



Re: [O] Scientific papers related to Org-mode

2012-04-10 Thread Bastien
Hi Rainer,

Rainer M Krug r.m.k...@gmail.com writes:

 On 10/04/12 10:57, suvayu ali wrote:
 On Tue, Apr 10, 2012 at 09:55, Rainer M Krug r.m.k...@gmail.com wrote:
 Why not put that into org? e.g. R has a function citation(), which returns 
 the bibtex for
 citing R or packages.
 
 Nice idea, why not submit a patch? ;)

 Because I unfortunately have effectively no idea about elisp, only
 that it uses *many* brackets...

 and I have at the moment =no time to learn it.

it's okay.  Still, could you describe a bit more precisely the function:
how does it work?  In what contexts?  What does it insert?

Thanks,

-- 
 Bastien



Re: [O] Scientific papers related to Org-mode

2012-04-10 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/04/12 11:13, Bastien wrote:
 Hi Rainer,
 
 Rainer M Krug r.m.k...@gmail.com writes:
 
 On 10/04/12 10:57, suvayu ali wrote:
 On Tue, Apr 10, 2012 at 09:55, Rainer M Krug r.m.k...@gmail.com wrote:
 Why not put that into org? e.g. R has a function citation(), which returns 
 the bibtex
 for citing R or packages.
 
 Nice idea, why not submit a patch? ;)
 
 Because I unfortunately have effectively no idea about elisp, only that it 
 uses *many*
 brackets...
 
 and I have at the moment =no time to learn it.
 
 it's okay.  Still, could you describe a bit more precisely the function: how 
 does it work?  In
 what contexts?  What does it insert?

It just returns the citation.

- From the help:

 Execute function ‘citation()’ for information on how to cite the
 base R system in publications.  If the name of a non-base package
 is given, the function either returns the information contained in
 the ‘CITATION’ file of the package or auto-generates citation
 information.  In the latter case the package ‘DESCRIPTION’ file is
 parsed, the resulting citation object may be arbitrarily bad, but
 is quite useful (at least as a starting point) in most cases.

Some examples:

This prints the citation for R:

#+begin_src R :results output
  citation()
#+end_src

#+RESULTS:
#+begin_example

To cite R in publications use:

  R Development Core Team (2012). R: A language and environment for
  statistical computing. R Foundation for Statistical Computing,
  Vienna, Austria. ISBN 3-900051-07-0, URL http://www.R-project.org/.

A BibTeX entry for LaTeX users is

  @Manual{,
title = {R: A Language and Environment for Statistical Computing},
author = {{R Development Core Team}},
organization = {R Foundation for Statistical Computing},
address = {Vienna, Austria},
year = {2012},
note = {{ISBN} 3-900051-07-0},
url = {http://www.R-project.org/},
  }

We have invested a lot of time and effort in creating R, please cite it
when using it for data analysis. See also ‘citation(pkgname)’ for
citing R packages.

#+end_example

And if a package name is given, it prints the citation info of this package:

#+begin_src R :results output
  citation(graphics)
#+end_src

#+RESULTS:
#+begin_example

The ‘graphics’ package is part of R.  To cite R in publications use:

  R Development Core Team (2012). R: A language and environment for
  statistical computing. R Foundation for Statistical Computing,
  Vienna, Austria. ISBN 3-900051-07-0, URL http://www.R-project.org/.

A BibTeX entry for LaTeX users is

  @Manual{,
title = {R: A Language and Environment for Statistical Computing},
author = {{R Development Core Team}},
organization = {R Foundation for Statistical Computing},
address = {Vienna, Austria},
year = {2012},
note = {{ISBN} 3-900051-07-0},
url = {http://www.R-project.org/},
  }

We have invested a lot of time and effort in creating R, please cite it
when using it for data analysis. See also ‘citation(pkgname)’ for
citing R packages.

#+end_example

Hope this helps,

Rainer



 
 Thanks,
 



- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys.
(Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+D/BkACgkQoYgNqgF2ego6TACdHeOC7GJcMf4BZFoXFFuho6ao
ABQAn1I2yOfUyM3FOpUjVfIXr7lvyX27
=T6rr
-END PGP SIGNATURE-



[O] Linking bibtex on Worg (was: Worg-page about Org-mode papers)

2012-04-10 Thread Karl Voit
* Karl Voit devn...@karl-voit.at wrote:

 http://orgmode.org/worg/org-papers.html

 I'd love to link bib-files with every entry. Where should I put them
 on Worg?

 Some paths I can think of:

 code/bibtex/*
 org-contrib/bibtex/*

I placed it in «org-contrib/bibtex/».

Unfortunately I can not publish it. Can someone give me a hint,
where I am failing at?

In the Org-mode file, I've liked it with
[[file:org-contrib/bibtex/Dominik2010.bib][bibtex]]
but http://orgmode.org/worg/org-contrib/bibtex/Dominik2010.bib does
not appear accessible on the server.

-- 
Karl Voit




[O] [babel] eval code only once :eval once

2012-04-10 Thread Torsten Wagner
Hi,
I started to use lisp (as well as other) code blocks more and more to
modify my work environment (emacs) for a particular (buffer-based)
task.
That is I change some variables, add some stuff etc.
A real world example is for example the section below

* Set-up  :nonexport:
#+source: setup-minted
#+begin_src emacs-lisp :exports none :results silent
(setq org-export-latex-listings 'minted)
(setq org-export-latex-custom-lang-environments
  '(
   (emacs-lisp common-lispcode)
))
(setq org-export-latex-minted-options
  '((frame lines)
(fontsize \\scriptsize)
(linenos )))
(setq org-latex-to-pdf-process
  '(pdflatex -shell-escape -interaction nonstopmode
-output-directory %o %f
pdflatex -shell-escape -interaction nonstopmode
-output-directory %o %f
pdflatex -shell-escape -interaction nonstopmode
-output-directory %o %f))
#+end_src

This are settings from worg, which I use only during my work on that
particular file/buffer e.g. to modify the export of the following
beamer presentation.
Whenever I load the buffer I jump to set-up and hit C-c C-C to execute
it once. After that exports will do what I want.
If I would change the above to :exports results and :results silent I
would be asked to execute the code block on every export.
Thanks to the new auto completion feature, I came across :eval and
wonder if it makes sense to add
:eval once
and
:eval once-query

Which would allow to execute it only once (with query) if not called
before and otherwise keeps quite.
That would make *Set-up blocks much more efficient.
Was thinking why there is no 'no-query' resp. 'always' flag which
would execute code blocks without query even if asked for it in
general but that would be somehow against safety measures ;)

Totti



Re: [O] Linking bibtex on Worg

2012-04-10 Thread Bastien
Hi Karl,

Karl Voit devn...@karl-voit.at writes:

 * Karl Voit devn...@karl-voit.at wrote:

 http://orgmode.org/worg/org-papers.html

 I'd love to link bib-files with every entry. Where should I put them
 on Worg?

 Some paths I can think of:

 code/bibtex/*
 org-contrib/bibtex/*

 I placed it in «org-contrib/bibtex/».

 Unfortunately I can not publish it. Can someone give me a hint,
 where I am failing at?

You are not failing at anything, just the website publishing config
should be updated when there is a new area with specific attachments.

 In the Org-mode file, I've liked it with
 [[file:org-contrib/bibtex/Dominik2010.bib][bibtex]]
 but http://orgmode.org/worg/org-contrib/bibtex/Dominik2010.bib does
 not appear accessible on the server.

Fixed, thanks.

-- 
 Bastien



[O] [PATCH] Re: Bug: SCHEDULED: positioning is fragile [7.8.06 (release_7.8.06.181.ga481)]

2012-04-10 Thread Jérémie Courrèges-Anglas
Bastien b...@gnu.org writes:
[snip]
 See this footnote in the section 8.3.1 Inserting deadlines or
 schedules of the manual:

(1) The `SCHEDULED' and `DEADLINE' dates are inserted on the line
 right below the headline.  Don't put any text between this line and the
 headline.

Hi. Then I guess the example in 8.3 Deadlines and scheduling should be
amended. Patch attached.

-- 
Jérémie Courrèges-Anglas
Empreinte GPG : 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
From 0644fc9f9eabc536348841550900a74f4bb5a5e0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=A9mie=20Courr=C3=A8ges-Anglas?= j...@wxcvbn.org
Date: Tue, 10 Apr 2012 14:10:03 +0200
Subject: [PATCH] Deadlines and scheduling: Fix order in DEADLINE example

* doc/org.texi (Deadlines and scheduling): fix example, the DEADLINE item
should come right after the headline.

Maybe should the footnote (in 8.3.1) documenting this requirement should come
right into the 8.3 section, after the example?
---
 doc/org.texi |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 0be6e2b..f0f6e9d 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -5721,8 +5721,8 @@ until the entry is marked DONE.  An example:
 
 @example
 *** TODO write article about the Earth for the Guide
-The editor in charge is [[bbdb:Ford Prefect]]
 DEADLINE: 2004-02-29 Sun
+The editor in charge is [[bbdb:Ford Prefect]]
 @end example
 
 You can specify a different lead time for warnings for a specific
-- 
1.7.6



pgpBskIggMI4f.pgp
Description: PGP signature


Re: [O] [PATCH] Re: Bug: SCHEDULED: positioning is fragile [7.8.06 (release_7.8.06.181.ga481)]

2012-04-10 Thread Bastien
Hi Jérémie,

jca+...@wxcvbn.org (Jérémie Courrèges-Anglas) writes:

 Bastien b...@gnu.org writes:
 [snip]
 See this footnote in the section 8.3.1 Inserting deadlines or
 schedules of the manual:

(1) The `SCHEDULED' and `DEADLINE' dates are inserted on the line
 right below the headline.  Don't put any text between this line and the
 headline.

 Hi. Then I guess the example in 8.3 Deadlines and scheduling should be
 amended. Patch attached.

Indeed.  I applied the patch.  

I added TINYCHANGE in the commit message.  Please do so for small
changes when you are not a FSF-signed contributor.

Thanks!

-- 
 Bastien



Re: [O] org-mime-htmlize: visual representation (thunderbird)

2012-04-10 Thread Uwe Brauer
 On Sun, 01 Apr 2012 12:38:12 -0400, Eric Schulte eric.schu...@gmx.com 
 wrote:


I'm not clear on how this differs from the messages produced using
org-mime-htmlize, and it has been a while since I've looked into email
mime mechanics.  However, since the emails generated using
org-mime-htmlize display correctly in Gmail and in gnus I'm inclined to
say that this is a Thunderbird issue and leave it for them to debug.

I send a bug report to the Thunderbird developer and the
answer was that *one* source of the problem is 

,
| Here, the message has a multipart/mixed structure at the top
| with cid: references to the image/png part which is inside
| that structure (the text/html part is correctly in a
| multipart/alternative but there is no multipart/related;
| both images are in the multipart/mixed context). Also, the
| images have a Content-Disposition: attachment, both
| reasons to show them as attachment as Thunderbird does it.
| 
| Now it seems that Gmail completely ignores multipart/related
| vs. mixed and simply takes the reference regardless of that
| context, which would explain what you see. Strictly
| speaking, the message is incorrectly formed. Please file a
| bug with Emacs, the latexit structure appears to be correct.
`


So how could Content-Disposition: attachment be changed to
Content-Disposition: inline in your code? I can't find the
relevant piece of code.

Thanks

Uwe 






[O] Running org-babel-tangle and/or org-export-as-pdf in Emacs batch mode

2012-04-10 Thread Bernd Weiss
Dear all,

I am not sure if this an orgmode-, an ESS- or an Emacs-related question.

I am working on an orgmode-file with embedded R code. Since I am using a
build tool called waf, I would like to call Emacs from command line like
this:

emacs --batch --load e:/config/.emacs --visit test.org --funcall
org-export-as-pdf

(or call org-babel-tangle)

However, it stops with Type C-h m for help on ESS version 12.03. If I
remove the R part (#+begin_src etc.), everything works as expected.

This is my (hopefully) minimal example, the command line output and the
orgmode related infos.

Thanks,

Bernd


---minimal example: test.org---
# Babel settings
#+PROPERTY: session *R*
#+PROPERTY: tangle test.R
#+PROPERTY: comments yes
#+PROPERTY: results output
#+PROPERTY: exports both

#+BEAMER_FRAME_LEVEL: 1

#+startup: beamer
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [bigger]
#+latex_header: %%\modebeamer{\usetheme{Madrid}}

* test heading
lsals

#+begin_src R
1+1
#+end_src
---minimal example: text.org---





---cl-output--
wmx336@fi-weiss-50 /cygdrive/e/projects/software/ps2012r_intro/test
$ emacs --batch --load e:/config/.emacs --visit test.org --funcall
org-export-as-pdf
customizing GNU Emacs
customizing GNU Emacs for Win 7
Loading e:/config/.recentf...
Cleaning up the recentf list...
Cleaning up the recentf list...done (0 removed)
Loading tex-mik...
Ido mode enabled
Source file
`d:/programme/emacs/site-lisp/org-mode/contrib/lisp/org-contacts.el'
newer than byte-compiled file
Ido mode enabled
Loading
d:/programme/emacs/site-lisp/color-theme/themes/color-theme-example.el
(source)...
Loading
d:/programme/emacs/site-lisp/color-theme/themes/color-theme-example.elc...
Loading
d:/programme/emacs/site-lisp/color-theme/themes/color-theme-library.el
(source)...
Loading
d:/programme/emacs/site-lisp/color-theme/themes/color-theme-library.elc...
Loading
d:/programme/emacs/site-lisp/color-theme/themes/color-theme-tango.el
(source)...
Loading
d:/programme/emacs/site-lisp/color-theme/themes/color-theme-tango.elc...
[yas] warning: keybinding (rinari-minor-mode-map . C-c C-c C-r)
invalid for snippet #+begin_src R...#+end_ since keymap
rinari-minor-mode-map does not (yet?) exist.
[yas] warning: keybinding (rinari-minor-mode-map . C-c C-c C-b)
invalid for snippet beamer_envargs since keymap
rinari-minor-mode-map does not (yet?) exist.
Loading d:/programme/emacs/site-lisp/graphviz-dot-mode.el (source)...
OVERVIEW
Local Ispell dictionary set to nil
Starting new Ispell process [default] ...
File mode specification error: (error
d:\\programme\\Aspell\\bin\\aspell.exe did not output version line)
Loading vc-git...
Exporting to PDF...
Exporting to LaTeX...
Local Ispell dictionary set to nil
Automatic display of crossref information was turned on
Applying style hooks...
Applying style hooks... done
Local Ispell dictionary set to nil
Local Ispell dictionary set to nil
executing R code block...
Type C-h m for help on ESS version 12.03
---cl-output--




---org-related-infos---
Emacs  : GNU Emacs 23.3.1 (i386-mingw-nt5.1.2600)
 of 2011-03-10 on 3249CTO
Package: Org-mode version 7.8.06 (release_7.8.06.180.g22bfd)

current state:
==
(setq
 org-export-preprocess-before-backend-specifics-hook
'(org-inlinetask-export-handler)
 org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
 org-export-latex-listings t
 org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
 org-agenda-custom-commands '((c conferences ((tags CONFERENCE))
((org-tags-match-list-sublevels nil))
   ((org-columns-default-format %DATE %LOCATION)))
  (d Upcoming deadlines agenda 
   ((org-agenda-time-grid nil) 
(org-deadline-warning-days 365)
(org-agenda-entry-types (quote (:deadline)
  (W Weekly Review ((agenda  
((org-agenda-ndays 14))) (todo
WRITING
 org-agenda-files '(e:/projects/habilitation/org/prHabilitation.org
e:/projects/org/agendas/2011fall.org
e:/projects/org/agendas/2011springterm.org
e:/projects/org/agendas/SynRG.org
e:/projects/org/agendas/capture.org e:/projects/org/agendas/d_2011a.org
e:/projects/org/agendas/prDAAD-ipd-ma-divorce.org
e:/projects/org/agendas/prDAAD-ma-simulation.org
e:/projects/org/agendas/privat.org
e:/projects/org/agendas/pu2012bbbook_basic_meta-analysis.org
e:/projects/org/agendas/te2012sose.org
e:/projects/org/agendas/te2012spring.org
e:/projects/org/agendas/work.org)
 org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent)
 org-src-fontify-natively t
 org-babel-load-languages '((emacs-lisp . t) (maxima . t) (R . t)
(python . t) 

Re: [O] [PATCH] Re: Bug: SCHEDULED: positioning is fragile [7.8.06 (release_7.8.06.181.ga481)]

2012-04-10 Thread Jérémie Courrèges-Anglas
Bastien b...@gnu.org writes:
[snip]
 I added TINYCHANGE in the commit message.  Please do so for small
 changes when you are not a FSF-signed contributor.

Oops, forgot that, thanks for the reminder, and thanks to the Org-mode
developers and community for such a great piece of software.

-- 
Jérémie Courrèges-Anglas
GPG fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494


pgpfUQaSigbtf.pgp
Description: PGP signature


Re: [O] [PATCH] Re: Bug: SCHEDULED: positioning is fragile [7.8.06 (release_7.8.06.181.ga481)]

2012-04-10 Thread Bastien
jca+...@wxcvbn.org (Jérémie Courrèges-Anglas) writes:

 Bastien b...@gnu.org writes:
 [snip]
 I added TINYCHANGE in the commit message.  Please do so for small
 changes when you are not a FSF-signed contributor.

 Oops, forgot that, thanks for the reminder, and thanks to the Org-mode
 developers and community for such a great piece of software.

No problem -- thanks again for the patch!

-- 
 Bastien



Re: [O] Bug: SCHEDULED: positioning is fragile [7.8.06 (release_7.8.06.181.ga481)]

2012-04-10 Thread Rainer Stengele
Am 09.04.2012 16:51, schrieb Bastien:
 Hi Dave,
 
 Dave Abrahams d...@boostpro.com writes:
 
 Sorry, but I don't want to spend the time on that.  I'm trying to get
 the rules changed so that it isn't so easy to corrupt an org file.  
 
 The current rule is Leave SCHEDULED: and DEADLINE: information where
 Org's `org-schedule' and `org-deadline' put it.
 
 Maybe I don't understand how do you want to change this rule.
 
 I'm not much interested in building a tool to undo corruption.

 FYI: Nicolas and I have been discussing about the issue you raised, and
 the integration of org-element.el will force us to be clearer about such
 cases, which is good.

 I sincerely hope that when you become clearer about such cases you pick
 a liberal set of rules that isn't so error-prone.  The ideas that I
 can't just hit return after a headline and start typing a body, and that
 I'll be nagged about misplaced SCHEDULED: lines, are both very
 unappealing.
 
 I have just added this hack:
 
   Check for misplaced SCHEDULED and DEADLINE cookies
   http://orgmode.org/worg/org-hacks.html#sec-1-2-8
 
 Here is the function:
 
 (defun org-check-misformatted-subtree ()
   Check misformatted entries in the current buffer.
   (interactive)
   (show-all)
   (org-map-entries
(lambda ()
  (move-beginning-of-line 2)
  (if (or (and (org-get-scheduled-time (point))
   (not (looking-at (concat ^.* org-scheduled-regexp
  (and (org-get-deadline-time (point))
   (not (looking-at (concat ^.* org-deadline-regexp)
  (when (y-or-n-p Fix this subtree? )
(message Call the function again when you're done fixing this 
 subtree.)
(recursive-edit))
(message All subtrees checked.)
 
 HTH,
 

Bastien,

why does the function fire in this case:


* test
** TODO task
   SCHEDULED: 2012-04-10 Di


Did I misunderstand?

Rainer




Re: [O] Bug: SCHEDULED: positioning is fragile [7.8.06 (release_7.8.06.181.ga481)]

2012-04-10 Thread Bastien
Hi Rainer,

Rainer Stengele rainer.steng...@online.de writes:

 why does the function fire in this case:

 * test
 ** TODO task
SCHEDULED: 2012-04-10 Di

Because it was buggy -- here is a better version (also updated on Worg)

(defun org-check-misformatted-subtree ()
  Check misformatted entries in the current buffer.
  (interactive)
  (show-all)
  (org-map-entries
   (lambda ()
 (when (and (move-beginning-of-line 2)
(not (looking-at org-heading-regexp)))
   (if (or (and (org-get-scheduled-time (point))
(not (looking-at (concat ^.* org-scheduled-regexp
   (and (org-get-deadline-time (point))
(not (looking-at (concat ^.* org-deadline-regexp)
   (when (y-or-n-p Fix this subtree? )
 (message Call the function again when you're done fixing this 
subtree.)
 (recursive-edit))
 (message All subtrees checked.))

Thanks for testing!

-- 
 Bastien



[O] Strange extra-space when using yasnippet for Org-mode heading

2012-04-10 Thread Karl Voit
Hi!

I do have a simple yasnippet template:

,[ ~/.emacs/yasnippets/text-mode/org-mode/test ]
| # name : test snippet
| # # --
| ** $1 $2  :$1$2:
| $0
`

When I invoke the snippet using »test« followed by the TAB key,
yasnippet correctly inserts the template. But after pressing the
first key afterwards, I get an extra space character.

So with »test« followed by TAB, »foo«, TAB, »bar«, I get this:

,[ result with extra-space after »f« ]
| ** f oo bar   :f oobar:
| Cursor
`

I am not even sure if this is an Org-mode related problem at all.
But since I do *not* end up with extra space characters when I
modify the template so that the two asterisks are missing (no
heading), I am afraid that Org-mode has a problem with yasnippet (at
least at my side).

Thanks for any pointer!


PS. current Org-mode from git; yasnippet (version 0.6.1b)

-- 
Karl Voit




Re: [O] 24.0.95; (org) outline-style cycling + outline-mode

2012-04-10 Thread Jambunathan K

Hello Bastien

Thanks for the fix and it addresses the problem I reported.  Feel free
to close this bug once you commit the changes to bzr repo.

Jambunathan K.



Re: [O] Bug: Tag Completion Not Prompting for all tags

2012-04-10 Thread Bastien
Hi Mike,

I just reverted the commits I pushed for fixing this issue.

Mike McLean mike.mcl...@pobox.com writes:

 The expected result is a completion list of tag_a and tag_b, this
 does not work and the Minibuffer prompts [No match]

I cannot do any better than to quote Matt Lundin on this:

Historically, only tags explicitly defined in org-tag-alist or via an
in-buffer heading show up in the fast tag completion window.

So, let's stick to the current behavior.

Thanks for your patience!

-- 
 Bastien



Re: [O] [PATCH] - Fix org-fast-tag-selection

2012-04-10 Thread Bastien
Hi Bernt,

Bernt Hansen be...@norang.ca writes:

 This error is gone but I see other problems.

 When completing tags with C-c C-q TAB and selecting a tag that is part
 of a group which are supposed to be mutually exclusive it doesn't
 remove other existing tags in that group.

This error was introduced by the commits I push to fix Mike's issue.  

It should be gone now.

I reverted these commits and things are now back to the previous
behavior.   

 Also my IDO completion of tags doesn't work (but I'm not sure if that
 ever did).  I can't to C-c C-q TAB home RET and get the @home tag -- I
 need to enter the @ for it to work.  Without the @ I get errors like
 this:

 Error in post-command-hook: (wrong-type-argument sequencep 104)

 when what I enter doesn't match my tag list.

This should not happen anymore too.

Best,

-- 
 Bastien



Re: [O] Possible bug in parsing / clarification of syntax

2012-04-10 Thread Bastien
Hi Simon,

Simon Thum simon.t...@gmx.de writes:

 I have found some irritating behaviour, potentially a bug. I have a block
 agenda which goes like:

 tags-todo @homeTODO=\TODO\

 and it displays a certain org line that reads

  TODO_ state triggers

Can you try the following patch (against latest hotfix HEAD) and report? 

Charles, can you let me know if this breaks anything in your usage of
`org-map-entries'? 

David's original fix want to the right direction, except that we also
want to match * TODO as a headline. 

Thanks for testing this quite heavily.

diff --git a/lisp/org.el b/lisp/org.el
index 3dd8f88..ea5ef7c 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -12824,7 +12824,7 @@ headlines matching this string.
 		  *\\((
 		 (mapconcat 'regexp-quote org-todo-keywords-1 \\|)
 		 (org-re
-		  )\\)? *\\(.*?\\)\\(:[[:alnum:]_@#%:]+:\\)?[ \t]*$)))
+		  )\\)?\\([ \t]*\\|$\\)+\\(.*?\\)\\(:[[:alnum:]_@#%:]+:\\)?[ \t]*$)))
 	 (props (list 'face 'default
 		  'done-face 'org-agenda-done
 		  'undone-face 'default

-- 
 Bastien


Re: [O] [bug] org-agenda-write does not handle date stamps without day of week

2012-04-10 Thread Bastien
Hi Carsten and all,

Carsten Dominik carsten.domi...@gmail.com writes:

 since we did make a change to Org a while ago to allow date stamps
 without the name of the day, I think it is only consequent to also do
 it for this case.  Must have slipped our attention back then.
 The only thing we must ensure is that this regexp matches fast
 as it is used a lot.

 Nick's proposal works, except for the fact that is also matches when
 the time is directly attached to day name.  Maybe it is cleaner to
 not match in this case.

 If we are going to make the day name optional, then it is better to
 include matching of the whitespace after the date into the day-name
 part of the regexp.

Agreed.

 I am attaching Nick's file again, with a third proposal for an
 updated regexp.

I tested it from reproducer.org (had to add a missing parenthesis) 
and it seems to work fine.

Carsten, please feel free to apply a patch with your new org-ts-regexp0
proposal against master HEAD.

Thanks!

-- 
 Bastien



Re: [O] Problem with dates while generating HTML

2012-04-10 Thread Bastien
Hi François,

pin...@iro.umontreal.ca (François Pinard) writes:

 I added Du  as a prefix to get going, but the ideal would be to
 directly use 2012-02-29 as the link description.  Is there a way, or is
 it a limitation (or a bug)?

I would call it a limitation.

-- 
 Bastien



Re: [O] [bug] org-agenda-write does not handle date stamps without day of week

2012-04-10 Thread Nick Dokos
Bastien b...@gnu.org wrote:

 Hi Carsten and all,
 
 Carsten Dominik carsten.domi...@gmail.com writes:
 
  since we did make a change to Org a while ago to allow date stamps
  without the name of the day, I think it is only consequent to also do
  it for this case.  Must have slipped our attention back then.
  The only thing we must ensure is that this regexp matches fast
  as it is used a lot.
 
  Nick's proposal works, except for the fact that is also matches when
  the time is directly attached to day name.  Maybe it is cleaner to
  not match in this case.
 
  If we are going to make the day name optional, then it is better to
  include matching of the whitespace after the date into the day-name
  part of the regexp.
 
 Agreed.
 
  I am attaching Nick's file again, with a third proposal for an
  updated regexp.
 
 I tested it from reproducer.org (had to add a missing parenthesis) 
 and it seems to work fine.
 
 Carsten, please feel free to apply a patch with your new org-ts-regexp0
 proposal against master HEAD.
 

I think he did already (but please check!):

commit 7d84b300f4cba8b726662113d4ce4ff40a76c5b5

Thanks,
Nick




Re: [O] Org-mode workshop: has anyone done this already?

2012-04-10 Thread Bastien
Hi Eric and all,

Eric Schulte eric.schu...@gmx.com writes:

 On March 25th in Albuquerque New Mexico at the monthly meeting of the
 Albuquerque Lisp/Scheme user group.

Please don't hesitate to store informations about Org Workshops on
Worg!  That will help other workshops to happen, and to reuse existing
content.  

Thanks,

-- 
 Bastien



Re: [O] [bug] org-agenda-write does not handle date stamps without day of week

2012-04-10 Thread Bastien
Nick Dokos nicholas.do...@hp.com writes:

 I think he did already (but please check!):

 commit 7d84b300f4cba8b726662113d4ce4ff40a76c5b5

You're right -- time to power off my computer :)

Thanks!

-- 
 Bastien



Re: [O] [babel] eval code only once :eval once

2012-04-10 Thread Thomas S. Dye
Torsten Wagner torsten.wag...@gmail.com writes:

 Hi,
 I started to use lisp (as well as other) code blocks more and more to
 modify my work environment (emacs) for a particular (buffer-based)
 task.
 That is I change some variables, add some stuff etc.
 A real world example is for example the section below

 * Set-up:nonexport:
 #+source: setup-minted
 #+begin_src emacs-lisp :exports none :results silent
 (setq org-export-latex-listings 'minted)
 (setq org-export-latex-custom-lang-environments
   '(
(emacs-lisp common-lispcode)
 ))
 (setq org-export-latex-minted-options
   '((frame lines)
 (fontsize \\scriptsize)
 (linenos )))
 (setq org-latex-to-pdf-process
   '(pdflatex -shell-escape -interaction nonstopmode
 -output-directory %o %f
 pdflatex -shell-escape -interaction nonstopmode
 -output-directory %o %f
 pdflatex -shell-escape -interaction nonstopmode
 -output-directory %o %f))
 #+end_src

 This are settings from worg, which I use only during my work on that
 particular file/buffer e.g. to modify the export of the following
 beamer presentation.
 Whenever I load the buffer I jump to set-up and hit C-c C-C to execute
 it once. After that exports will do what I want.
 If I would change the above to :exports results and :results silent I
 would be asked to execute the code block on every export.
 Thanks to the new auto completion feature, I came across :eval and
 wonder if it makes sense to add
 :eval once
 and
 :eval once-query

 Which would allow to execute it only once (with query) if not called
 before and otherwise keeps quite.
 That would make *Set-up blocks much more efficient.
 Was thinking why there is no 'no-query' resp. 'always' flag which
 would execute code blocks without query even if asked for it in
 general but that would be somehow against safety measures ;)

 Totti


Aloha Totti,

Will :cache yes do what you want?

Tom

-- 
Thomas S. Dye
http://www.tsdye.com



Re: [O] Bug: Tag Completion Not Prompting for all tags

2012-04-10 Thread Mike McLean
Interesting

The very first report I submitted (
http://comments.gmane.org/gmane.emacs.orgmode/53824 ) showed the historic
behavior correct (the two tags defined in org-tag-alist show up in the fast
tag completion window). The bug was after shifting to free tag selection
mode, the tags defined in org-tag-alist are not available for completion.

The behavior that Matt Lundin reported was/is a side effect of the fix
(implementation). I think that the idea of the fix is valid, e.g. the free
tag entry should autocomplete tags defined in org-tag-alist to match the
behavior of the fast tag completion window.

On Tuesday, April 10, 2012, Bastien wrote:

 Hi Mike,

 I just reverted the commits I pushed for fixing this issue.

 Mike McLean mike.mcl...@pobox.com javascript:; writes:

  The expected result is a completion list of tag_a and tag_b, this
  does not work and the Minibuffer prompts [No match]

 I cannot do any better than to quote Matt Lundin on this:

 Historically, only tags explicitly defined in org-tag-alist or via an
 in-buffer heading show up in the fast tag completion window.

 So, let's stick to the current behavior.

 Thanks for your patience!

 --
  Bastien



Re: [O] Bug: Tag Completion Not Prompting for all tags

2012-04-10 Thread Mike McLean
On Tuesday, March 27, 2012, Bastien wrote:


  Shouldn't free tag entry always show all possible tags, regardless of
  the setting of or use of fast tag completion?

 I think so -- thanks a lot for the detailed report.


Yes, this is the crux of the problem as first reported. Note that the fixes
were in two parts because the first patch worked without
org-completion-use-ido (part of a minimal test case) and the second attempt
was to fix it with org-completion-use-ido enabled.


Re: [O] Problem with dates while generating HTML

2012-04-10 Thread François Pinard
Bastien b...@gnu.org writes:

 Hi François,

Bonjour, Bastien!

 I added Du  as a prefix to get going, but the ideal would be to
 directly use 2012-02-29 as the link description.  Is there a way, or is
 it a limitation (or a bug)?

 I would call it a limitation.

Could it be documented somewhere appropriate?  Along with Nick's
suggestion of prefixing the date with a space to prevent the problem.

François



[O] orgweb/Changes: broken formatting of code blocks

2012-04-10 Thread Julian Gehring

Hi,

at the changes page of the orgmode website, some of the code block 
formatting seems to be broken (see http://orgmode.org/Changes.html#sec-3).


Can anyone please check if the attached patch would fix this?  With my 
local setup, this yields a proper display of the code blocks.  Or do the 
commas in front of the code lines have a meaning that I am simply missing?



Best
Julian

From 72e27909e8a01bdd44a85f05826a052e1dbe698a Mon Sep 17 00:00:00 2001
From: Julian Gehring julian.gehr...@googlemail.com
Date: Tue, 10 Apr 2012 21:44:35 +0200
Subject: [PATCH] Changes.org: fix code block formatting

---
 Changes.org |   80 +--
 1 file changed, 40 insertions(+), 40 deletions(-)

diff --git a/Changes.org b/Changes.org
index 409fa95..adc1438 100644
--- a/Changes.org
+++ b/Changes.org
@@ -241,60 +241,60 @@ combines with =visual-line-mode=.
 This results in the following behavior.
 
 #+begin_src org
-  ,#+property: var  foo=1
-  ,#+property: var+ bar=2
+  #+property: var  foo=1
+  #+property: var+ bar=2
   
-  ,#+begin_src emacs-lisp
-  ,  (+ foo bar)
-  ,#+end_src
+  #+begin_src emacs-lisp
+(+ foo bar)
+  #+end_src
   
-  ,#+results:
-  ,: 3
+  #+results:
+  : 3
   
-  ,#+begin_src emacs-lisp
-  ,  (org-entry-get (point) var t)
-  ,#+end_src
+  #+begin_src emacs-lisp
+(org-entry-get (point) var t)
+  #+end_src
   
-  ,#+results:
-  ,: foo=1 bar=2
+  #+results:
+  : foo=1 bar=2
   
-  ,* overwriting a file-wide property
-  ,  :PROPERTIES:
-  ,  :var:  foo=7
-  ,  :END:
+  * overwriting a file-wide property
+:PROPERTIES:
+:var:  foo=7
+:END:
   
-  ,#+begin_src emacs-lisp
-  ,  foo
-  ,#+end_src
+  #+begin_src emacs-lisp
+foo
+  #+end_src
   
-  ,#+results:
-  ,: 7
+  #+results:
+  : 7
   
-  ,#+begin_src emacs-lisp
-  ,  (org-entry-get (point) var t)
-  ,#+end_src
+  #+begin_src emacs-lisp
+(org-entry-get (point) var t)
+  #+end_src
   
-  ,#+results:
-  ,: foo=7
+  #+results:
+  : foo=7
   
-  ,* appending to a file-wide property
-  ,  :PROPERTIES:
-  ,  :var+:  baz=3
-  ,  :END:
+  * appending to a file-wide property
+:PROPERTIES:
+:var+:  baz=3
+:END:
   
-  ,#+begin_src emacs-lisp
-  ,  (+ foo bar baz)
-  ,#+end_src
+  #+begin_src emacs-lisp
+(+ foo bar baz)
+  #+end_src
   
-  ,#+results:
-  ,: 6
+  #+results:
+  : 6
   
-  ,#+begin_src emacs-lisp
-  ,  (org-entry-get (point) var t)
-  ,#+end_src
+  #+begin_src emacs-lisp
+(org-entry-get (point) var t)
+  #+end_src
   
-  ,#+results:
-  ,: foo=1 bar=2 baz=3
+  #+results:
+  : foo=1 bar=2 baz=3
 #+end_src
 
 *** =org-agenda-custom-commands= has a default value ([[git:b3de2dbb953dcadacafeb179899ab9df184da4ff][git]])
-- 
1.7.10




Re: [O] Scientific papers related to Org-mode

2012-04-10 Thread Bastien
Hi Rainer,

Rainer M Krug r.m.k...@gmail.com writes:

 It just returns the citation.

Okay.  I've added this to the Worg FAQ:

* Is there a bibtex entry for the Org manual?

Yes.  Please evaluate this function and run =M-x
org-insert-manual-bitex-citation-at-point RET=.

#+begin_src emacs-lisp
(defun org-insert-manual-bitex-citation-at-point ()
  Insert a Bibtex citation of the Org manual at point.
  (interactive)
  (insert
  @book{dominik10:_org_mode_refer_manual,
  author =   {Carsten Dominik},
  title ={The \pkg{Org-Mode} 7 Reference Manual: Organize
  Your Life with GNU Emacs},
  publisher ={Network Theory},
  year = 2010,
  address =  {UK},
  note = {with contributions by David O`Toole, Bastien Guerry,
  Philip Rooke, Dan Davison, Eric Schulte, and Thomas
  Dye}
}
  (message Thanks for quoting the Org manual!)))
#+end_src

I don't think we need this in Org's core, but it's good to have it
somewhere.

Thanks!

-- 
 Bastien



Re: [O] layout org-babel menu WAS: About org-babel menu

2012-04-10 Thread Bastien
Guys,

let me know when you have a first stable draft for the structure of the
Babel menu and I'll implement it.

Thanks,

-- 
 Bastien



Re: [O] Filtering agenda by the top category

2012-04-10 Thread Bastien
Hi John,

John Wiegley jwieg...@gmail.com writes:

 I discovered the  key in the agenda yesterday (by accident!), which filters
 the Agenda down to entries having the same category.

 However, I use both *categories* and *projects*.  For example:

   * Work
 :CATEGORY: Work
 :OVERLAY:  (face (:background #fdfdeb))
   ** PROJECT Foo
 :CATEGORY: Foo

 I use :CATEGORY: for my project here so it shows up in the leftmost column of
 my agenda.  I don't want every project displaying as just Work.  I use the
 :OVERLAY: so that all Work items have the same background color, which is a
 better way of seeing at a glance which *category* every item falls into.

 What this means is that although I can use  to filter by *project*, I can't
 filter down to the Work *category*.  So that's what the code below does.  I
 bind it to , since I wasn't using what that binding does.

I tested the code and it looks useful.  

Could you make a patch against current master?

 Also, I found a bug: passing a prefix argument to  doesn't have any effect.
 The code doesn't use that argument in any meaningful way.

This is now fixed.  You can use `C-u ' to filter out the category of
the current line.  Thanks for spotting this!

-- 
 Bastien



Re: [O] Problem with dates while generating HTML

2012-04-10 Thread Bastien
Bonjour François,

pin...@iro.umontreal.ca (François Pinard) writes:

 Bastien b...@gnu.org writes:

 Hi François,

 Bonjour, Bastien!

 I added Du  as a prefix to get going, but the ideal would be to
 directly use 2012-02-29 as the link description.  Is there a way, or is
 it a limitation (or a bug)?

 I would call it a limitation.

 Could it be documented somewhere appropriate?  Along with Nick's
 suggestion of prefixing the date with a space to prevent the problem.

Yes, it could be documented in an appropriate place in Worg.

Please suggest one and send a patch!

Best,

-- 
 Bastien



[O] YAOMUC - yet another org-mode use case

2012-04-10 Thread Nick Dokos
Funkload is an HTTP functional test and load tool. In the FAQ, there is
this:

,
| How to modify a report ?
| 
| The report is in reStructuredText, the index.rst can be edited in text
| mode, to rebuild the html version:
| 
|   rst2html --stylesheet=funkload.css   index.rst --traceback  index.html
| 
| Charts are build with gnuplot the gplot script file are present in the
| report directory to rebuild the pages charts for instance:
| 
|   gnuplot pages.gplot
| 
| Since FunkLoad 1.15 you can also use an org-mode output to edit or
| extend the report before exporting it as a PDF.
`

See http://funkload.nuxeo.org/faq.html#how-to-modify-a-report

Nick




[O] Worg = Ikiwiki + Org? (was Re: Usage of disqus instead of mailinglist considered harmful)

2012-04-10 Thread Jambunathan K
Samuel Wales samolog...@gmail.com writes:

 Long shot: is making worg more wiki-like practical?

Worg = Ikiwiki + Org?

http://lists.gnu.org/archive/html/emacs-orgmode/2011-12/msg00431.html

It wouldn't be a bad idea to ask Ikiwiki folks to support Org-mode
natively.  I dropped a note to them a few weeks ago, btw.
-- 



Re: [O] YAOMUC - yet another org-mode use case

2012-04-10 Thread Bastien
Nick Dokos nicholas.do...@hp.com writes:

 See http://funkload.nuxeo.org/faq.html#how-to-modify-a-report

Yeah.  That's great!  Thanks for sharing this.

-- 
 Bastien



Re: [O] [bug] Remote durations are considered as fractions

2012-04-10 Thread Bastien
Hi Sébastien,

Sebastien Vauban wxhgmqzgw...@spammotel.com writes:

 Using the flag T does not help:

 | Planning  | 00:00:03 |
 | Reporting | 00:00:09 |
 #+TBLFM: @1$2=remote(hours-spent,@4$4);T

This should work as expected now (with the T flag.)

Note that the conversion of 3:12 into 1:4 is independant 
of getting the remote references right when they are durations.

| Test | 3:12 |
|  |  1:4 |
#+TBLFM: @2$2=@1$2

Thanks for reporting this!

-- 
 Bastien



[O] To git cloners: please update your tags

2012-04-10 Thread Bastien
Please do a

~$ cd [your-org-clone-dir/]
~$ git fetch --tags origin

as I updated the release_7.8.08 tag by annotating it.

Thanks,

-- 
 Bastien



Re: [O] [PATCH] Separate file time from its tasks times

2012-04-10 Thread Bastien
Hi Sébastien,

Sebastien Vauban wxhgmqzgw...@spammotel.com writes:

 This can be best understood with an example...

I've been thinking about this again and I made up my mind with a clearer
argument.

 Before:

 #+BEGIN: clocktable :maxlevel 4 :scope (file-abc-tom.org 
 file-abc-ann.org) :block 2012-02
 Clock summary at [2012-03-30 Fri 15:12], for February 2012.

 | File | Headline | Time  |   |
 |--+--+---+---|
 |  | ALL Total time   | 19:15 |   |
 |--+--+---+---|
 | file-abc-tom.org | File time| 17:15 |   |
 |  | Task A   | 17:15 |   |
 |  | TODO Subtask A1  |   | 17:15 |
 |--+--+---+---|
 | file-abc-ann.org | File time| 2:00  |   |
 |  | Task B   | 2:00  |   |
 |  | TODO Subtask B2  |   |  2:00 |
  #+END:

 Now:

 #+BEGIN: clocktable :maxlevel 4 :scope (file-abc-tom.org 
 file-abc-ann.org) :block 2012-02
 Clock summary at [2012-03-30 Fri 15:13], for February 2012.

 | File | Headline | Time  |   |   |
 |--+--+---+---+---|
 |  | ALL Total time   | 19:15 |   |   |
 |--+--+---+---+---|
 | file-abc-tom.org | File time| 17:15 |   |   |
 |  | Task A   |   | 17:15 |   |
 |  | TODO Subtask A1  |   |   | 17:15 |
 |--+--+---+---+---|
 | file-abc-ann.org | File time| 2:00  |   |   |
 |  | Task B   |   |  2:00 |   |
 |  | TODO Subtask B2  |   |   |  2:00 |
  #+END:

If we go for the second solution, the next step would be to put the ALL
Total time into a different column than the File time... because it
can look illogical to have both in the same column, for the same reasons
it can look illogical to have a file's tasks times in the same column
than the File time itself.

So I'd rather stick to the current behavior, which I find more readable
in the sense that it adds less columns.  I hope you can explain this to
your collaborators :)

All best,

-- 
 Bastien



Re: [O] ATTR_HTML for a clickable image, howto?

2012-04-10 Thread Samuel Wales
Hi Christian,

Thanks for your reply.

I left implicit the question of whether this can solve OP's problem
also, but believe it is potentially related.

However, if I understood CSS well enough to ask the question
precisely, I'd have the answer.  So bear with me.

More below:

On 2012-04-07, Christian Moe m...@christianmoe.com wrote:
 Will CSS solutions described in this thread work if you always export
 subtrees (not entire .org files) and never include style files?

 Yes, CSS styles apply to exported subtrees as well, whether from the
 default stylesheet, linked external stylesheets, or #+STYLE headers.

Hmm, I think I should have specified further.  I mean
org-export-region-as-html.  The raw HTML without any head section,
files, stylesheets, or anything else.

So for example, could the OP and I use styles that are specified with
div style= wrapping the entire output?  Seems a simple addition to the
exporter or even a defadvice, but I don't know if it would work as I
don't know what the CSS would look like well enough to try it.

The critical thing is to avoid all dependency on anything external
like a stylesheet.  The goal is to keep all information in your file
under Org control, including style.

 But this applies to the static html files as exported by Org. If I
 understand your drift, you're thinking about using it in a content
 management system (CMS) like Blogger. A CMS will typically store only
 the content of your document and substitute its own template for the
 HEAD section where style information goes. Then these solutions won't
 work without modifying CSS in your CMS.

Not even with wrapping the entire output in a div?

 You can edit the CSS template of your CMS to take advantage of the
 classes and ids Org applies to its HTML exports.

The idea is to avoid a dependency like that if possible.

 - You can use #+ATTR_HTML to add class, id or style attributes to
 /some/ elements, and my understanding is that the new exporter that is
 in the works will help do this more systematically.

Wondering if you can control this under my additional requirements
using inheritance from higher-level constructs like a div wrapper
around the whole export.

 - You can enclose blocks in custom block classes (DIV CLASS=foo)
 with org-special-blocks (#+BEGIN_FOO), or with verbatim HTML.

Yes, this is where I was leading.  But it's no good for my purposes if
you can't use CSS directly in your Org file without any header or
external files.

 Locally applying CSS to elements with the STYLE attribute, the very
 lowest level of the cascade, should be the last resort.

Right.  :)

 - You can simplify repeated use with macros. See the manual, section
 11.6. Use the @ notation (section 12.5.3) for literal html tags within
 the macros. E.g.:

 #+MACRO: mycolor @span style=color: black; background-color:
 #f4a460$1@/span

I've tried macros for image specification, but ran into a variety of
issues getting it to work well.

 {{{mycolor(Here I'd like some black text on an orange background.)}}}

For paragraphs and sections and quotes and so on, the #+ blocks would
work better.  Not sure if {{{}}} would nest?  Or be noticeable.  That
seems much better for spans of text, not so much for standalone images
and sections with more than one paragraph, lists, etc.

 - You could probably also use Eric Schulte's contributed
 org-exp-blocks.el, but you'd need to write some code, and it might be
 overkill for this purpose.

I was wondering if this would be useful too.

 Depends on your use case, I guess, but I think it would nearly always
 be a better, simpler, cleaner solution to modify your Blogger CSS.

OK.  But my desire not to depend on the cloud is large enough that I
have to go back to the raw HTML method.

I want this to work no matter who I give the HTML file (singular) to.

Assuming it's possible -- if not I will just keep using raw HTML.

This is not a critical issue, but I thought it could expand the OP's
conversation to include a general solution for everybody if it works.

Samuel

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com



Re: [O] Multiple (natural) languages in a single org-file

2012-04-10 Thread François Pinard
Nicolas Goaziou n.goaz...@gmail.com writes:

 Just use two different drawer names, and select which one to actually
 export through i.e. #+OPTIONS: d:(EN). No need for extra syntax.

Well, the manual says, in node Export options:

 d: turn on/off inclusion of drawers

So one would never guess from the manual that d: may accept drawer
names.  If what Nicolas suggests is real, the documentation should be
adjusted.  I do not find any other explanation in the manual about
values for the d: option.

François



Re: [O] org-yank improvement?

2012-04-10 Thread François Pinard
Memnon Anon gegendosenflei...@googlemail.com writes:

 pin...@iro.umontreal.ca (François Pinard) writes:

 I often cut a list item (or a hierarchy of list items) to reinsert it
 into another heading which I know contains only list items.  All the
 headings are collapsed, so what I usually do is position the cursor at
 the beginning of the /next/ heading and yank the list item there, this
 has the effect of inserting it at the end of the previous heading, no
 need to open it.

 Mhh, why don't you just insert a newline above the next heading and yank
 then? 

Hi, Memnon :-).

Because it would induce a spurious white line.

 However, by mistake, it happens that the cursor is on the only visible
 bullet star of the next heading  instead of really being at the start
 of the line. 

 I wonder how you end up between two stars in the first place...

Usually through Emacs C-n.

 Of course, it is my error.  Yet, Org mode could be friendlier, here!

 Lets say 'safer'.

Safer *is* friendlier :-).

 But while ... indicating folded content at the end
 of a line is an integral part of org, things like org-hide-leading-stars
 seemed to me always to be purely cosmetic.  Nice to have, but if one
 really edits org files by hand (it is all plain text, right),
 potentially a problem.

Agreed that it's all plain text.  Yet, this is Emacs, and Org mode is
a very powerful mode, from which people may expect a lot.

François



Re: [O] org-yank improvement?

2012-04-10 Thread François Pinard
pin...@iro.umontreal.ca (François Pinard) writes:

 [...] so what I usually do is position the cursor at
 the beginning of the /next/ heading and yank the list item there.   [...]
 However, by mistake, it happens that the cursor is on the only visible
 bullet star of the next heading (I'm using org-indent-mode
 instead of really being at the start of the line.

 It never really make sense, in my opinion, to yank in the middle of an
 invisible string.  Luckily enough, yanking is done through a special
 org-yank function, so it is at least theoretically possible to prevent
 this.  My suggestion would be that whenever yanking into a start string,
 that the yanking really occurs at the beginning of it.

While revising old email, I'm stumbling on this, and just got a small
idea.  I do not know if it would work.  While playing with the
visibility of the stars, maybe that the text between the beginning of
the line up to the last and only visible star in a header could be given
the intangible attribute.  I did not play with this in a very long
while, but if I remember well, this would prevent inserting in the
middle of this region.

François



[O] [OT] Defining System, process, methodology and framework

2012-04-10 Thread Marcelo de Moraes Serpa
Hi guys,

I know there are quite a few smart brains around here, and I think this is
valid discussion for this mailing list, even if OT.

I'm not a cientist, nor work inside an academic environment. I'm just a
regular guy trying to understand this world and making better use of my
resources, specially time. For this, I have read dozens of books on
personal productivity, including GTD, Making it All Work, and Work the
System. All great books.

I've started to notice a pattern though. All of them talk about systems and
processes (and some might even use the word framework and methodology / or
method), and although you can live by and be quite productivity if you
apply the principles, I knew I had to understand in an even lower and basic
level. I then asked myself What the heck is a system and what is the
relationship it has with process, methodology and frameworks ?

I found out, for example, that System and Process sometimes are used
inter-changeably. So I went to google to try to find out the answer. The
simplest answers simply say that a process is what a system is made of.
It did not convince me.

By reading the wikipedia article about System (
http://en.wikipedia.org/wiki/System), I found out this paragraph under
System concepts:

Process and transformation process
 A system can also be viewed as a bounded transformation process, that is,
 a process or collection of processes that transforms inputs into outputs.
 Inputs are consumed; outputs are produced. The concept of input and output
 here is very broad. E.g., an output of a passenger ship is the movement of
 people from departure to destination.


A system can viewed as a process? Hmm, confusing.

Right now, my mental model basically says that a system is like blueprint
with different components that communicate, and a process is what runs on
it (or in on of its components). Framework is like a collection of
systems and a methodology is basically akin to system (in my
understanding).

Why am I obsessing about this?

The reason is systems thinking. I think it's a quite interesting mindset
and way to perceive the world. By trying to view yourself and what
surrounds you as systems (with sub-systems), it's much easier to document
(them), get feedback, and improve, automating your life even further,
understanding it more, and living better.

For example, from this perspective I think, GTD is simply a product of an
elevated point of view from the author David Allen. He simply viewed things
systematically and documented them. That's why he says it's 'common-sense'.

But before that, it would be nice to know exactly what a System is, and
it's relationship with process, methodology and framework, in
abstract terms.

 What do you think? I'm sure there are quite a few people here that might
be crazy enough to have the same question, or perhaps, I'm just too crazy.
Let me know, any insights very much appreciated.

Cheers,

- Marcelo.


[O] latex to org converter

2012-04-10 Thread Marvin Doyley
Hi there,

Does anybody has a script that convert latex files to org mode ?

I wrote one in Matlab, but it is a little clunky - I wrote it in matlab
because I am still learning lisp

thanks
M


Re: [O] latex to org converter

2012-04-10 Thread Charles Philip Chan
Marvin Doyley marvin...@gmail.com writes:

 Does anybody has a script that convert latex files to org mode ?

 I wrote one in Matlab, but it is a little clunky - I wrote it in matlab
 because I am still learning lisp

Not exactly a script, but I highly recommend Pandoc[1]. There is also
pandoc-mode[2], which is an Emacs frontend to Pandoc.


Footnotes: 
[1] http://johnmacfarlane.net/pandoc/ 

[2] http://wwwuser.gwdg.de/~jkremer/pandoc-mode.html 

-- 
We are MicroSoft.  You will be assimilated.  Resistance is futile.
(Attributed to B.G., Gill Bates)


pgpGcaeiu7fVS.pgp
Description: PGP signature


Re: [O] layout org-babel menu WAS: About org-babel menu

2012-04-10 Thread Eric Schulte
t...@tsdye.com (Thomas S. Dye) writes:

 Eric Schulte eric.schu...@gmx.com writes:

 Torsten Wagner torsten.wag...@gmail.com writes:

 Hi,

 for me the biggest trouble with babel is to remember the possible
 keywords in the header for different languages.
 There were a lot of ongoing syntax change which did not make it easier
 for me to remember all this.
 Thus a menu which is organised by languages offering all possible
 settings for each language would be very helpful.
 |
 Python
 ||
 |  export - code - result - both - none
 ||
 |  tangle - no - yes- filename
 |   |
 |  result - value - output
 |  |
 | ...
 |
 ...

 Not sure how effectual this would be in a main menu. It would be
 definitely awesome in a context menu

 That would be (copied from worg) [*] indicates cursor position

 #+NAME: factorial
 #+BEGIN_SRC haskell [*] :results silent :exports code :var n=0

 a context menu would appear presenting all possible header arguments for 
 haskell

 #+NAME: factorial
 #+BEGIN_SRC haskell :results [*] :exports code :var n=0

 a context menu presenting all possible values for the header argument
 :results in haskell
 I guess that together with the possibility to call this menu by
 keyboard strokes or alternatively show the same infos in the
 minibuffer would be a great win for babel and it would make many
 questions here on the list unnecessary.
 Furthermore, any change or extension in the syntax for a certain
 language would be directly reflected to the end-user. E.g., If I
 suddenly see the menu entry :exports 3dprint, I would be curious and
 check it out on worg and the manual ;)

 Totti


 Hi,

 I've put together a first pass at such support for interactive header
 argument look up.  Please evaluate this elisp code [1] in your *scratch*
 buffer, then in an Org-mode buffer insert a code block like the
 following with the point at [*], and press tab.

 #+begin_src R :[*]
   :foo
 #+end_src

 You should see an auto-completion list showing which header arguments
 are available and (for those with known arguments) which arguments may
 be specified.  This includes language specific header arguments, i.e.,
 the R code block above suggests about twice as many possible header
 arguments as an elisp block.  Note this expand on tab after : behavior
 is active on #+headers: lines as well.

 This makes use of the `org-babel-common-header-args-w-values' variable
 which holds header argument names and completions, as well as the
 org-babel-header-arg-names:lang variables.

 Does this seem like a good interface?

 Is it missing any important functionality?

 Best,

 Footnotes: 
 [1]  
 ;; Add support for completing-read insertion of header arguments after :
 (defun org-babel-header-arg-expand ()
   Call `org-babel-enter-header-arg-w-completion' in appropriate contexts.
   (when (and (= (char-before) ?\:) (org-babel-where-is-src-block-head))
 (org-babel-enter-header-arg-w-completion (match-string 2

 (defun org-babel-enter-header-arg-w-completion (optional lang)
   Insert header argument appropriate for LANG with completion.
   (let* ((lang-headers-var (intern (concat org-babel-header-arg-names: 
 lang)))
  (lang-headers (when (boundp lang-headers-var)
  (mapcar #'symbol-name (eval lang-headers-var
  (headers (append (mapcar #'symbol-name org-babel-header-arg-names)
   lang-headers))
  (header (org-completing-read Header Arg:  headers))
  (args (cdr (assoc (intern header)
org-babel-common-header-args-w-values)))
  (arg (when (and args (listp args))
 (org-completing-read
  (format %s:  header)
  (mapcar #'symbol-name (car args))
 (insert (concat header   (or arg )))
 (cons header arg)))

 (add-hook 'org-tab-first-hook 'org-babel-header-arg-expand)

 Hi Eric,

 This is potentially much nicer than a function template.  I tried
 filling out an R source code block's header arguments, but I couldn't
 find a way to get :results output graphics, which I use frequently for
 ggplot2 graphics.  With TAB I could see type arguments, but not
 collection or handling arguments.  Is there some way to cycle through
 the various completion lists?

 All the best,
 Tom

Hi Tom,

Currently language specific arguments for header arguments are not
stored in any elisp variables so there is no way to provide this
information to the auto completion function.  I'm adding a new suite of
language-specific variables which may be customized by each language to
provide information on language-specific header-argument arguments.

I've just put together this new code into a patch.  I'm not currently
able to run the test suite without massive failures (with or without
this patch), so I'm just attaching the patch here rather than pushing it
up directly.  If it works well on other people's systems I think it
should be committed.

After this is applied the 

Re: [O] [babel] feature suggestion

2012-04-10 Thread Eric Schulte
Rainer M Krug r.m.k...@gmail.com writes:

 Hi

 There are regularly questions concerning file wide properties set with

 #+PROPERTY: 

 which are simply caused by not C-c C-c  before tangling / executing block.

 Would it be an option to apply these headers automatically e.g. in the 
 pre-tangling hook?

 Or could that cause problems with more complex setups?

 Rainer

You're welcome to try this out.  Adding the function that updates
properties to the pre-tangle hook is more configuration than coding.  If
it works well for you maybe it would be worth considering as a default
setting.

Best,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/



Re: [O] org-babel-C-ensure-main-wrap fails unless I add exit(0)

2012-04-10 Thread Eric Schulte
Applied, thanks!

Dov Grobgeld dov.grobg...@gmail.com writes:

 Sure. They should be equivalent. (In C++ return is prefered as it calls
 destructors. But anyone relying on this when using C++ in org-mode should
 imnsho get a permanent ban from ever using C/C++ ;-).

 Regards,
 Dov

 On Thu, Apr 5, 2012 at 17:56, Eric Schulte eric.schu...@gmx.com wrote:

 Dov Grobgeld dov.grobg...@gmail.com writes:

  Oops. I sawthat  I wrote do not get any error though I meant do not
 get
  any resulting output.
 

 Would this alternate version work (without requiring stdlib.h)?

 (defun org-babel-C-ensure-main-wrap (body)
  Wrap body in a \main\ function call if none exists.
  (if (string-match ^[ \t]*[intvod]+[ \t\n\r]*main[ \t]*(.*) body)
  body
(format int main() {\n%s\nreturn(0);\n}\n body)))

 Thanks,

 
  On Wed, Apr 4, 2012 at 11:13, Dov Grobgeld dov.grobg...@gmail.com
 wrote:
 
  When running a babel C session under Linux/gcc I do not get any error
  unless I add exit(0) as part of the C-code snippet. For some to me not
  understood reason my program exits with error code=4, which is caught by
  org-babel-eval and the printed output is not inserted into my buffer . I
  solved this by adding `#include stdlib.h` and `exit(0);` as part of
  org-babel-C-ensure-main-wrap .
 
  Should I prepare this as patch?
 
  Regards,
  Dov
 
 

 --
 Eric Schulte
 http://cs.unm.edu/~eschulte/


-- 
Eric Schulte
http://cs.unm.edu/~eschulte/



Re: [O] Multiple (natural) languages in a single org-file

2012-04-10 Thread Nick Dokos
François Pinard pin...@iro.umontreal.ca wrote:

 Nicolas Goaziou n.goaz...@gmail.com writes:
 
  Just use two different drawer names, and select which one to actually
  export through i.e. #+OPTIONS: d:(EN). No need for extra syntax.
 
 Well, the manual says, in node Export options:
 
  d: turn on/off inclusion of drawers
 
 So one would never guess from the manual that d: may accept drawer
 names.  If what Nicolas suggests is real, the documentation should be
 adjusted.  I do not find any other explanation in the manual about
 values for the d: option.
 

Two paragraphs below the d: line you found, the manual says

,
|The default values for these and many other options are given by a
| set of variables.  For a list of such variables, the corresponding
| OPTIONS keys and also the publishing keys (*note Project alist::), see
| the constant `org-export-plist-vars'.
`

Examining the value of org-export-plist-vars shows

,
|  ...
|  (:drawers d org-export-with-drawers)
|  ...
`

Also, in section 13.1.5, (info (org) Options for the HTML/LaTeX
exporters), it says

,
|  The table below lists these properties along with
| the variable they belong to.  See the documentation string for the
| respective variable for details.
| 
| ...
| `:drawers'  `org-export-with-drawers'
| ...
`

and examining the doc of org-export-with-drawers (with C-h v) we find:

,
| Non-nil means export with drawers like the property drawer.
| When t, all drawers are exported.  This may also be a list of
| drawer names to export.
`

None of this is an argument for leaving the manual as is: if you had a
problem finding the information, then others will too, so the manual
should be improved.

But the information is there, and moreover, learning how to find it in
this instance has the huge advantage of teaching one how to find it for
all the other options as well.  The question as always is how far to go
in documenting all the options: it would be good to document them all
(as Bastien would say: patches are welcome), but is it better to learn
searching tricks or to submit patches to improve the doc? Each one of us
would probably answer that question differently (we have different
breaking points). So you might prepare a doc patch (please do!) - I
might go on a searching expedition and find things you didn't [fn:1].
The first one benefits everybody, the second one benefits mainly me, but
sometimes I can find a teaching moment and tell other people how to do
something: which is why I spent a half-hour writing this :-) [fn:2]

I think both of these methods (and surely there are other methods as
well) have some value - and some drawbacks as well, but I'll leave that
for another time. 

Nick

Footnotes:

[fn:1] If I think it's easier, I'll search in the sources, rather than
the manual, but that's just me :-) I'm not advocating this as a general
solution of course - otoh, once you have a basic grasp of lisp, it's a
great way to learn how to read programs - real-life, non-trivial
programs at that.

[fn:2] For me, the puzzle aspects are more interesting: I'm not a
power-user of org, and I use maybe 1/10 of its capabilities. But when
I'm climbing walls and I need a distraction, a good juicy question on
org-mode is just what the doctor ordered...