Re: [O] export: noweb blocks substituted versus verbatim ?

[Brian Beckman]

Brian Beckman  gmail.com> writes:

Found the appropriate docs here: 
http://orgmode.org/manual/noweb.html#noweb

Re: [O] Exporter aborts upon encountering even one unresolvable link

[Suvayu Ali]

On Fri, Sep 25, 2015 at 09:04:29AM +0200, Rainer M Krug wrote:
> 
> Look at publishing instead of exporting to html which works with
> missing links.

That sounds a bit fishy.  AFAIK, ox-publish just wraps around the usual
org-export-as functions from ox.el.  I could be wrong of course.

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] [patch] support latex variants

[Rasmus]

Pushed.
-- 
May contains speling mistake

Re: [O] [RFC] Draft mode

[Marcin Borkowski]

On 2015-09-27, at 20:39, Rasmus  wrote:

> Nicolas Goaziou  writes:
>
>> The following patch implements a draft mode for export. When in draft
>> mode, invalid macros and links do not throw an error. It can be toggled
>> with `org-export-as-draft' variable, or using C-d in export dispatch.

I would welcome this feature...

> Can this just be a variable set by BIND or publish?  The interest of such
> functionality seems to be limited to people who maintain
> broken-but-soon-to-be-fixed documents...  It does not seem to warrant
> prime real estate in the exporter IMO. Further, I don't think 'draft' is
> the correct word for this, but that's of course minor.
>
>> It introduces a backward incompatible change since it modifies signature
>> from `org-export-as' and alike.
>
> Doesn't seem worth it.

...but I agree with the above.

Also, wouldn't it be even better if there were some buffer - like
(La)TeX's log file - accumulating all the errors/warnings from the
exporting process?  Then, the above behavior could be the default, but
it would produce warnings.  Or it might depend on some setting.

> Rasmus

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

Re: [O] babel header arguments tutorial?

[Nick Dokos]

Lawrence Bottorff  writes:

> I guess from a purely elisp perspective I'm baffled. How is
>
> #+begin_src emacs-lisp
>   org-babel-default-header-args:Python
> #+end_src
>
> supposed to produce
>
> #+RESULTS:
> | (:session . foo) |
>
> as it supposedly does in the doc? It doesn't for me. (Where, e.g., would 
> "foo" be coming from?) If it had worked, does it make an addition to some 
> hash table, or an alist somewhere?
> But then running this as an elisp code block is cool from a declarative 
> programming standpoint (see this) . So this
>
> # Local Variables:
> # eval: (setq-local org-babel-default-header-args:Python '((:session . 
> "foo")))
> # End:
>
> is called when you eval-buffer or open the file? 
>

When you open the file. But see some caveats in my reply. Charles
Berry's reply shows the preferred method today, using only what's
available in org, but does not shed any light on the local file
variables question (which is a more general mechanism, available
throughout emacs, not just with org files).

Assuming that you want to learn about file variables, we will forget
temporarily about Charles's reply.

So when you open the file, the local variables section is found and
evaluated. Any variable settings are automatically buffer-local.
That's what sets the org-babel-default-header-args:python variable
to '((:session . "foo")) - in that buffer only.

Then when you go evaluate the code block

#+begin_src emacs-lisp
org-babel-default-header-args:python
#+end_src

the variable has the give value and produces a result

#+RESULTS:
: ((:session . foo))

But if you evaluate the same code block in some other buffer, the
result will be nil (unless you have initialized in some other way
of course, e.g. by adding the initialization to your .emacs).

> Ancillary questions:
> 1. can babel elisp (or CL) blocks be assigned/associated to a
> specifically named session?
> That would enable various elisp code blocks to have separate "session
> spaces" (as does the geiser/scheme babel). If so, I'm guessing the
> block-session communication could also be remote? Again, with babel
> geiser/scheme sessions, can they call "cached" things from each
> other's different sessions?
>

Theoretically, maybe (how's that for exactness?), but there are babel
implementations that don't support sessions at all and (depending on the
underlying interpreter), there may be subtle (or perhaps not so subtle)
differences in evaluation semantics. Some experimentation should provide
answers, but N.B. that the answers may be accidents of implementation
(which some might call "bugs"). I don't think there is a strictly
defined session model that applies to all languages: the implementations
do the best they can under these circumstances.

Now this is more a hunch than anything else: I *think* that's the way
things are but I may be wrong, out-of-date, or both. A set of
well-designed experiments in as many languages as possible would clarify
the situation, and perhaps lead to improvements (they could also be
turned into unit tests, which would be very desirable) - I won't
volunteer, but maybe you would?

> 2. . . . which makes me wonder how code blocks in a buffer can be run besides 
> manually C-c C-c ing them. For example,
>
> #+name: myexptdouble
> #+begin_src emacs-lisp :session
> (defun myexptdouble (x y)
>   (* (myexpt x y) (myexpt x y)))
> #+end_src
>
> #+RESULTS: myexptdouble
> : myexptdouble
>
> #+name: myexpt
> #+begin_src emacs-lisp :session
> (defun myexpt (x y)
>   (expt x y))
> #+end_src
>
> #+BEGIN_SRC emacs-lisp :results output raw
> (myexptdouble 2 3)
> #+END_SRC
>
> Even if I manually evaluate myexptdouble, running the last block gives an 
> error about not knowing what myexpt is. Is there something in the last block 
> that can be told to evaluate all
> the dependent functions? Perhaps if my blocks are named the same as the 
> function name? How tangling and preserving sessions is also an interesting 
> question, IHMO.
>

That's not answering any of your deeper questions, but the problem here
is that the last code block evaluates a function that produces no
output: it produces a return value though, so try

#+BEGIN_SRC emacs-lisp :results value raw
 (myexptdouble 2 3)
#+END_SRC

-- 
Nick

Re: [O] [RFC] Draft mode

[Rasmus]

Nicolas Goaziou  writes:

> The following patch implements a draft mode for export. When in draft
> mode, invalid macros and links do not throw an error. It can be toggled
> with `org-export-as-draft' variable, or using C-d in export dispatch.

Can this just be a variable set by BIND or publish?  The interest of such
functionality seems to be limited to people who maintain
broken-but-soon-to-be-fixed documents...  It does not seem to warrant
prime real estate in the exporter IMO. Further, I don't think 'draft' is
the correct word for this, but that's of course minor.

> It introduces a backward incompatible change since it modifies signature
> from `org-export-as' and alike.

Doesn't seem worth it.

> This patch is incomplete as it is missing some documentation, an entry
> in ORG-NEWS and some tests. Also, export back-end in contrib/ directory
> are not updated yet. In any case, feedback welcome.

I did not test it at this point.

Rasmus

-- 
Sådan en god dansk lagereddike kan man slet ikke bruge mere

[O] [PATCH] Substitute a guid XML element in org-feed

[Hiroshi Saito]

Hi,

A guid XML element is not substituted in org-feed. Here is a patch to fix it.

--
Sincerely,
Hiroshi Saito


0001-org-feed.el-Substitute-a-guid-XML-element.patch
Description: Binary data

Re: [O] babel header arguments tutorial?

[Thomas S . Dye]

Aloha Nick,

Nick Dokos  writes:

> Thomas S. Dye  writes:
>
>> Aloha Nick,
>>
>> Nick Dokos  writes:
>>
>>> The implementation on the page you linked contains a typo (capital P
>>> instead of lower-case p in python) and is much more prolix than it needs
>>> to be. You can get the same effect with
>>>
>>> # Local Variables:
>>> # org-babel-default-header-args:python: ((:session . "foo")))
>>> # End:
>>>
>>> This form should be preferred for just setting variables. The eval
>>> mechanism should be used only when absolutely necessary.
>>
>> Can you elaborate why the eval mechanism should be used only when
>> absolutely necessary?  You've mentioned that a few times but I haven't
>> run across similar warnings elsewhere.
>>
>
> It's a matter of safety: eval allows you to evaluate arbitrary lisp
> code. Doing that in a local-variables block which is run when you
> open the file can lead to all kinds of damage. If you get a file
> with an eval in the local variables section, you'd better be very
> sure before opening the file in emacs.
>
> Here's one warning:
>
> http://www.gnu.org/software/emacs/manual/html_node/emacs/Safe-File-Variables.html

Thanks for the clarification.  Emacs' built-in paranoia seems
appropriate, I guess.  I get asked if I want to evaluate local variables
that might not be safe and one of my choices is to say no, in which case
the file is opened without evaluating them.  At that point I can look at
the code they propose to run and convince myself there is no mischief.

All the best,
Tom

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

Re: [O] [RFC] Draft mode

[Charles C. Berry]

On Sun, 27 Sep 2015, Nicolas Goaziou wrote:


Nicolas Goaziou  writes:


The following patch implements a draft mode for export. When in draft
mode, invalid macros and links do not throw an error. It can be toggled
with `org-export-as-draft' variable, or using C-d in export dispatch.

It introduces a backward incompatible change since it modifies signature
from `org-export-as' and alike.



I don't get it.

Why not add the `draft' arg to the end of the `&optional' args? Won't that 
preserve backward compatibility?


I maintain derived backends that use the `post-process' arg and are 
distributed on github. So now I will need to make them version aware 
and/or provide version specific branches so as not to break when used with 
older org-mode versions, won't I?


Chuck

Re: [O] babel header arguments tutorial?

[Lawrence Bottorff]

I guess from a purely elisp perspective I'm baffled. How is

#+begin_src emacs-lisp
  org-babel-default-header-args:Python
#+end_src

supposed to produce

#+RESULTS:
| (:session . foo) |

as it supposedly does in the doc? It doesn't for me. (Where, e.g., would
"foo" be coming from?) If it had worked, does it make an addition to some
hash table, or an alist somewhere? But then running this as an elisp code
block is cool from a declarative programming standpoint (see this
) . So this

# Local Variables:
# eval: (setq-local org-babel-default-header-args:Python '((:session .
"foo")))
# End:

is called when you eval-buffer or open the file?

Ancillary questions:
1. can babel elisp (or CL) blocks be assigned/associated to a specifically
named session? That would enable various elisp code blocks to have separate
"session spaces" (as does the geiser/scheme babel). If so, I'm guessing the
block-session communication could also be remote? Again, with babel
geiser/scheme sessions, can they call "cached" things from each other's
different sessions?

2. . . . which makes me wonder how code blocks in a buffer can be run
besides manually C-c C-c ing them. For example,


#+name: myexptdouble
#+begin_src emacs-lisp :session
(defun myexptdouble (x y)
  (* (myexpt x y) (myexpt x y)))
#+end_src

#+RESULTS: myexptdouble
: myexptdouble

#+name: myexpt
#+begin_src emacs-lisp :session
(defun myexpt (x y)
  (expt x y))
#+end_src

#+BEGIN_SRC emacs-lisp :results output raw
(myexptdouble 2 3)
#+END_SRC

Even if I manually evaluate myexptdouble, running the last block gives an
error about not knowing what myexpt is. Is there something in the last
block that can be told to evaluate all the dependent functions? Perhaps if
my blocks are named the same as the function name? How tangling and
preserving sessions is also an interesting question, IHMO.

[O] Bug: one column table to array conversion in bash

[Konrad Herbst]

Hello,

Recently I tried to use org-babel for bash with its feature for 
conversation of tables to arrays. I found that a one column table is 
associated with an array in bash while one column of a table retrieved 
by indexing throws the error '(wrong-type-argument listp "foo")'.


Here is an example in org:
---Begin---
* Example 1 -- WORKS
#+NAME: table1
| foo  |
| bar  |
| test |

#+BEGIN_SRC bash :var table=table1 :results scalar
echo ${table[0]}
#+END_SRC

#+RESULTS:
: foo

* Example 2 -- DOESN'T WORK
#+NAME: table2
| foo  | one   |
| bar  | two   |
| test | three |

#+BEGIN_SRC bash :var table=table2[,0] :results scalar
echo ${table[1]}
#+END_SRC

#+RESULTS:
:

* Example 3 -- WORKS
#+BEGIN_SRC bash :var table=table2[,0:-1] :results scalar
echo ${table['bar']}
#+END_SRC

#+RESULTS:
: two
-End-

This was kind of counterintuitive to me but is that maybe the wanted 
behavior? I think it has something to do with that the function 
'org-babel-variable-assignments:bash_array' in ob-shell.el is called for 
the first example, while 'org-babel-variable-assignments:bash_assoc' is 
incorrectly called for the second. Thats why the third example is 
working again.


In the end I drilled it down to this function:
'org-babel-ref-resolve' in ob-ref.el. The first example evaluates to a 
list of lists while the second only to a list. Shouldn't both give the 
same result?


Sorry, but would you say thats a bug or a feature request?

Best,
Konrad

Emacs  : GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll 
bars)

 of 2015-06-28 on trouble, modified by Debian
Package: Org-mode version 8.3.1 (release_8.3.1-280-g6f2579)

Re: [O] [PATCH] ox-latex: Add scrartcl LaTeX class

[Sebastian Boehm]

Hi,

On 24 September 2015 at 12:04, Eric S Fraga  wrote:
> I have done the following:
> […]

thanks for all the great suggestions! I haven't had the opportunity to
try out all proposed solutions yet, but Eric's snippet looks like a
great way to tackle my initial problem.

Best,
Sebastian

Re: [O] [RFC] Draft mode

[Nicolas Goaziou]

Nicolas Goaziou  writes:

> The following patch implements a draft mode for export. When in draft
> mode, invalid macros and links do not throw an error. It can be toggled
> with `org-export-as-draft' variable, or using C-d in export dispatch.
>
> It introduces a backward incompatible change since it modifies signature
> from `org-export-as' and alike.
>
> This patch is incomplete as it is missing some documentation, an entry
> in ORG-NEWS and some tests. Also, export back-end in contrib/ directory
> are not updated yet. In any case, feedback welcome.
>
> It is meant to be applied on top of master branch.

And, here's a first update.

>From bae307895b934328f10f003758446b11cbc13beb Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou 
Date: Sun, 27 Sep 2015 10:59:20 +0200
Subject: [PATCH] ox: Implement draft mode

* lisp/ox.el (org-export-as-draft): New variable.
(org-export-dispatch-use-expert-ui): Document new export option.
(org-export-data): Ignore user errors when in draft mode.
(org-export-as): Add new optional argument to toggle draft mode. Ignore
unknown macros.
(org-export-string-as):
(org-export-to-buffer):
(org-export-to-file): Handle signature change.
(org-export-dispatch):
(org-export--dispatch-ui):
(org-export--dispatch-action): Provide a mean to toggle draft mode.

* lisp/ox-ascii.el (ascii):
(org-ascii-export-as-ascii):
(org-ascii-export-to-ascii):

* lisp/ox-beamer.el (beamer):
(org-beamer-export-as-latex):
(org-beamer-export-to-latex):
(org-beamer-export-to-pdf):

* lisp/ox-html.el (html):
(org-html-export-as-html):

* lisp/ox-icalendar.el (icalendar):

* lisp/ox-latex.el (latex):
(org-latex-export-as-latex):
(org-latex-export-to-latex):
(org-latex-export-to-pdf):

* lisp/ox-man.el (man):
(org-man-export-to-man):
(org-man-export-to-pdf):

* lisp/ox-md.el (md):
(org-md-export-as-markdown):
(org-md-export-to-markdown):

* lisp/ox-odt.el (odt):
(org-odt-export-to-odt):

* lisp/ox-org.el (org):
(org-org-export-to-org):

* lisp/ox-publish.el (org-publish-org-to):

* lisp/ox-texinfo.el (texinfo):
(org-texinfo-export-to-texinfo):
(org-texinfo-export-to-info): Handle signature change.

* testing/lisp/test-ox.el (test-org-export/handle-options):
(test-org-export/with-timestamps):
(test-org-export/uninterpreted):
(test-org-export/expand-macro):
(test-org-export/footnote-first-reference-p):
(test-org-export/handle-inlinetasks): Update tests.
---
 lisp/ox-ascii.el|  39 +++---
 lisp/ox-beamer.el   |  21 +++-
 lisp/ox-html.el |  11 +-
 lisp/ox-icalendar.el|   4 +-
 lisp/ox-latex.el|  26 ++--
 lisp/ox-man.el  |  16 ++-
 lisp/ox-md.el   |  25 ++--
 lisp/ox-odt.el  |  21 ++--
 lisp/ox-org.el  |  13 +-
 lisp/ox-publish.el  |   2 +-
 lisp/ox-texinfo.el  |  20 ++--
 lisp/ox.el  | 311 
 testing/lisp/test-ox.el | 123 +--
 13 files changed, 376 insertions(+), 256 deletions(-)

diff --git a/lisp/ox-ascii.el b/lisp/ox-ascii.el
index 5cc70bd..b50cebb 100644
--- a/lisp/ox-ascii.el
+++ b/lisp/ox-ascii.el
@@ -97,23 +97,23 @@
   :menu-entry
   '(?t "Export to Plain Text"
((?A "As ASCII buffer"
-	(lambda (a s v b)
-	  (org-ascii-export-as-ascii a s v b '(:ascii-charset ascii
+	(lambda (a s v b d)
+	  (org-ascii-export-as-ascii a s v b d '(:ascii-charset ascii
 	(?a "As ASCII file"
-	(lambda (a s v b)
-	  (org-ascii-export-to-ascii a s v b '(:ascii-charset ascii
+	(lambda (a s v b d)
+	  (org-ascii-export-to-ascii a s v b d '(:ascii-charset ascii
 	(?L "As Latin1 buffer"
-	(lambda (a s v b)
-	  (org-ascii-export-as-ascii a s v b '(:ascii-charset latin1
+	(lambda (a s v b d)
+	  (org-ascii-export-as-ascii a s v b d '(:ascii-charset latin1
 	(?l "As Latin1 file"
-	(lambda (a s v b)
-	  (org-ascii-export-to-ascii a s v b '(:ascii-charset latin1
+	(lambda (a s v b d)
+	  (org-ascii-export-to-ascii a s v b d '(:ascii-charset latin1
 	(?U "As UTF-8 buffer"
-	(lambda (a s v b)
-	  (org-ascii-export-as-ascii a s v b '(:ascii-charset utf-8
+	(lambda (a s v b d)
+	  (org-ascii-export-as-ascii a s v b d '(:ascii-charset utf-8
 	(?u "As UTF-8 file"
-	(lambda (a s v b)
-	  (org-ascii-export-to-ascii a s v b '(:ascii-charset utf-8))
+	(lambda (a s v b d)
+	  (org-ascii-export-to-ascii a s v b d '(:ascii-charset utf-8))
   :filters-alist '((:filter-headline . org-ascii-filter-headline-blank-lines)
 		   (:filter-parse-tree org-ascii-filter-paragraph-spacing
    org-ascii-filter-comment-spacing)
@@ -2023,7 +2023,7 @@ a communication channel."
 
 ;;;###autoload
 (defun org-ascii-export-as-ascii
-  (&optional async subtreep visible-only body-only ext-plist)
+  (&optional async subtreep visible-only body-only draft ext-plist)
   "Export current buffer to a text buffer.
 
 If narrowing is active in the current buffer, only export its
@@ -2045,6

Re: [O] Show presence of zero width spaces using overlay

[Nicolas Goaziou]

Hello,

timor  writes:

> I am wondering why there is no simple backslash-escaping of org-mode
> syntax?

I think a backslash escaping is needed. However, I don't think it is
going to be that simple. Do you have some specifications in mind?


Regards,

-- 
Nicolas Goaziou

[O] Creating a subtree with changes (filtered by tag)

[Axel Kielhorn]

Hi,

I’m using org-mode to write specifications.
Since the list grew quite long I want to add a subtree showing the changes as a 
quick overview.
I tag the changes with the week of the modification:

* Subject one
* Subject two :KW38:
* Subject three :KW38:
* Subject four
** Subsubject four-one :KW39:

With this I can get a sparse tree to see the changes.
For my team I export an HTML version of the org file.
I’m using the bigblow theme, thus it is possible to select the changes by using 
a tag filter.

In addition to that I would like to get a new section with the changes:

* Changes
** KW38
** KW39

I had a look at the columnview dblock but I can’t use a tag filter with that.

I’m using Org 8.2.10 with a setup based on John Kitchen’s jmax.

Any ideas?

Axel

[O] [RFC] Draft mode

[Nicolas Goaziou]

Hello,

The following patch implements a draft mode for export. When in draft
mode, invalid macros and links do not throw an error. It can be toggled
with `org-export-as-draft' variable, or using C-d in export dispatch.

It introduces a backward incompatible change since it modifies signature
from `org-export-as' and alike.

This patch is incomplete as it is missing some documentation, an entry
in ORG-NEWS and some tests. Also, export back-end in contrib/ directory
are not updated yet. In any case, feedback welcome.

It is meant to be applied on top of master branch.


Regards,

-- 
Nicolas Goaziou0x80A93738
>From 4ad64f60eb12e39a9140feb4e0c7c046e014ec6c Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou 
Date: Sun, 27 Sep 2015 10:59:20 +0200
Subject: [PATCH] ox: Implement draft mode

* lisp/ox.el (org-export-as-draft): New variable.
(org-export-dispatch-use-expert-ui): Document new export option.
(org-export-data): Ignore user errors when in draft mode.
(org-export-as): Add new optional argument to toggle draft mode.
(org-export-string-as):
(org-export-to-buffer):
(org-export-to-file): Handle signature change.
(org-export-dispatch):
(org-export--dispatch-ui):
(org-export--dispatch-action): Provide a mean to toggle draft mode.

* lisp/ox-ascii.el (ascii):
(org-ascii-export-as-ascii):
(org-ascii-export-to-ascii):

* lisp/ox-beamer.el (beamer):
(org-beamer-export-as-latex):
(org-beamer-export-to-latex):
(org-beamer-export-to-pdf):

* lisp/ox-html.el (html):
(org-html-export-as-html):

* lisp/ox-icalendar.el (icalendar):

* lisp/ox-latex.el (latex):
(org-latex-export-as-latex):
(org-latex-export-to-latex):
(org-latex-export-to-pdf):

* lisp/ox-man.el (man):
(org-man-export-to-man):
(org-man-export-to-pdf):

* lisp/ox-md.el (md):
(org-md-export-as-markdown):
(org-md-export-to-markdown):

* lisp/ox-odt.el (odt):
(org-odt-export-to-odt):

* lisp/ox-org.el (org):
(org-org-export-to-org):

* lisp/ox-publish.el (org-publish-org-to):

* lisp/ox-texinfo.el (texinfo):
(org-texinfo-export-to-texinfo):
(org-texinfo-export-to-info): Handle signature change.

* testing/lisp/test-ox.el (test-org-export/handle-options):
(test-org-export/with-timestamps):
(test-org-export/uninterpreted):
(test-org-export/expand-macro):
(test-org-export/footnote-first-reference-p):
(test-org-export/handle-inlinetasks): Update tests.
---
 lisp/ox-ascii.el|  39 
 lisp/ox-beamer.el   |  21 +++--
 lisp/ox-html.el |  11 ++-
 lisp/ox-icalendar.el|   4 +-
 lisp/ox-latex.el|  26 --
 lisp/ox-man.el  |  16 +++-
 lisp/ox-md.el   |  25 +++--
 lisp/ox-odt.el  |  21 +++--
 lisp/ox-org.el  |  13 ++-
 lisp/ox-publish.el  |   2 +-
 lisp/ox-texinfo.el  |  20 ++--
 lisp/ox.el  | 242 +++-
 testing/lisp/test-ox.el | 123 
 13 files changed, 329 insertions(+), 234 deletions(-)

diff --git a/lisp/ox-ascii.el b/lisp/ox-ascii.el
index 5cc70bd..b50cebb 100644
--- a/lisp/ox-ascii.el
+++ b/lisp/ox-ascii.el
@@ -97,23 +97,23 @@
   :menu-entry
   '(?t "Export to Plain Text"
((?A "As ASCII buffer"
-	(lambda (a s v b)
-	  (org-ascii-export-as-ascii a s v b '(:ascii-charset ascii
+	(lambda (a s v b d)
+	  (org-ascii-export-as-ascii a s v b d '(:ascii-charset ascii
 	(?a "As ASCII file"
-	(lambda (a s v b)
-	  (org-ascii-export-to-ascii a s v b '(:ascii-charset ascii
+	(lambda (a s v b d)
+	  (org-ascii-export-to-ascii a s v b d '(:ascii-charset ascii
 	(?L "As Latin1 buffer"
-	(lambda (a s v b)
-	  (org-ascii-export-as-ascii a s v b '(:ascii-charset latin1
+	(lambda (a s v b d)
+	  (org-ascii-export-as-ascii a s v b d '(:ascii-charset latin1
 	(?l "As Latin1 file"
-	(lambda (a s v b)
-	  (org-ascii-export-to-ascii a s v b '(:ascii-charset latin1
+	(lambda (a s v b d)
+	  (org-ascii-export-to-ascii a s v b d '(:ascii-charset latin1
 	(?U "As UTF-8 buffer"
-	(lambda (a s v b)
-	  (org-ascii-export-as-ascii a s v b '(:ascii-charset utf-8
+	(lambda (a s v b d)
+	  (org-ascii-export-as-ascii a s v b d '(:ascii-charset utf-8
 	(?u "As UTF-8 file"
-	(lambda (a s v b)
-	  (org-ascii-export-to-ascii a s v b '(:ascii-charset utf-8))
+	(lambda (a s v b d)
+	  (org-ascii-export-to-ascii a s v b d '(:ascii-charset utf-8))
   :filters-alist '((:filter-headline . org-ascii-filter-headline-blank-lines)
 		   (:filter-parse-tree org-ascii-filter-paragraph-spacing
    org-ascii-filter-comment-spacing)
@@ -2023,7 +2023,7 @@ a communication channel."
 
 ;;;###autoload
 (defun org-ascii-export-as-ascii
-  (&optional async subtreep visible-only body-only ext-plist)
+  (&optional async subtreep visible-only body-only draft ext-plist)
   "Export current buffer to a text buffer.
 
 If narrowing is active in the current buffer, only export i

[O] Modification dates in Worg (was: babel header arguments tutorial?)

[Michael Strey]

On Sa, 2015-09-26 at 23:39, Charles C. Berry wrote:

[...]

> The source is several years old and filed under the FIXME worg
> directory.

Both things are not visible on the page.  In general there seems to be a
lot of outdated stuff on Worg.  It would be helpful to have at least the
date of last modification on the pages.

-- 
Michael Strey
http://www.strey.biz * https://twitter.com/michaelstrey