Re: [O] Leslie Lamport has a foot in the 21st century

[Hubert Chathi]

On Sun, 09 Oct 2016 18:32:55 +0200, Marcin Borkowski  said:

> On 2016-10-09, at 16:26, Hubert Chathi  wrote:

>> It's not a matter of compiling to the right file format, but rather
>> whether LaTeX is the right tool for the type of document structure
>> that Lamport is proposing.  His system requires people to be able to
>> expand and collapse things, which TeX is unable to handle.  You might
>> be able to fake it in TeX by using hyperlinks, but that might drive
>> the PDF/dead tree readers crazy once they get a couple of levels deep
>> in your proof, having to keep track of all the links that they had to
>> follow.  Not to mention, it would probably require a lot of TeX black
>> magic to implement.  It would require adding some new environments
>> and/or commands to LaTeX, which the current LaTeX-to-HTML converters
>> wouldn't be able to handle -- you'd need to implement those bits.  So
>> given that you'd need to create a bunch of new infrastructure, and
>> TeX would basically just be dead weight, the question is: is it worth
>> still using LaTeX, or is it better to start with something else
>> entirely that's better suited to handle hierarchical proofs?

> Please be careful to make the distinction between TeX and LaTeX here.

Yes, I was careful to distinguish between TeX and LaTeX, and I said
"TeX" when I meant "TeX".  I'm sure that LaTeX is perfectly capable of
representing Lamport's proposed proof structure.  But the question is,
why use LaTeX when half the reason for using LaTeX is that it can
generate beautiful printed output through TeX, and Lamport's
hierarchical proof would translate pretty badly to print.  (As I
mentioned, it would be possible to translated it to a printed version,
but reading a printed version would likely be rather painful.)

I don't know much about LaTeX3, but it looks like it's still targeting
print, and so it would have the same problems.  Not only that, but the
existing LaTeX-to-HTML tools might not work with LaTeX3, so if you're
getting rid of half of your toolset, why switch to LaTeX3 instead of
some other format that targets HTML more directly?

I'm sure that there may be good reasons for sticking with LaTeX
(e.g. being able to easily copy-and-paste into for-print articles,
familiarity with the language, etc.), but there are also disadvantages,
and it will be interesting to see what factors determine what type of
system, whether it be LaTeX or something closer to HTML, ends up being
used to write hierarchical proofs.

I suspect that it will be a long time before hierarchical proofs gain
much popularity though, given that Lamport has been talking about them
since at least the 90's, and I haven't seen one "in the wild" yet.  So I
don't know how much of a factor it will be "killing" LaTeX, if LaTeX
ever does get killed.

-- 
Hubert Chathi - Email: hub...@uhoreg.ca - https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca - Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/113A1368 (Key available at pool.sks-keyservers.net)
Fingerprint: F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Re: [O] Leslie Lamport has a foot in the 21st century

[Clément Pit--Claudel]

On 2016-10-11 10:56, Hubert Chathi wrote:
> I suspect that it will be a long time before hierarchical proofs gain
> much popularity though, given that Lamport has been talking about them
> since at least the 90's, and I haven't seen one "in the wild" yet.

Depends how much you're willing to stretch the definition.  Many 
machine-checked proofs are written in a pretty hierarchical style, and some of 
the associated tools support folding and expanding subproofs (see the middle 
gif in 
https://github.com/cpitclaudel/company-coq/#outlines-code-folding-and-jumping-to-definition).



signature.asc
Description: OpenPGP digital signature

Re: [O] Problem with python session

[Nicolas Goaziou]

Hello,

John Kitchin  writes:

> I am not sure it makes sense to change anything for this.

Noted. Thank you for the feedback.

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: make test fails, no org-batch-test-init (8.3.5 tar.gz)

[Nicolas Goaziou]

Hello,

Rich Clark  writes:

> TMPDIR=/tmp/tmp-orgtest emacs  -Q -batch --eval '(setq vc-handled-backends
> nil org-startup-folded nil)'  --eval '(add-to-list '"'"'load-path (concat
> default-directory "lisp"))' --eval '(add-to-list '"'"'load-path (concat
> default-directory "testing"))'  -l org-batch-test-init --eval '(setq
> org-batch-test t org-babel-load-languages (quote ( (awk . t)  (C . t)
>  (fortran . t)  (maxima . t)  (lilypond . t)  (octave . t)  (perl . t)
>  (python . t)  (emacs-lisp . t)  (shell . t)  (org . t)))
> org-test-select-re "\\(org\\|ob\\)" )' -l org-loaddefs.el -l cl -l
> testing/org-test.el -l ert -l org -l ox  --eval '(org-test-run-batch-tests
> org-test-select-re)'
> Cannot open load file: no such file or directory, org-batch-test-init
> make: *** [mk/targets.mk:104: test] Error 255

FWIW, I cannot reproduce it on a recent version of Org.

Regards,

-- 
Nicolas Goaziou

Re: [O] Use headings in sitemap

[Nicolas Goaziou]

Hello,

Thibault Marin  writes:

> I would like to generate a sitemap for a published website and use it to 
> extract
> the last few entries in a specific folder to put on the main page.
>
> The site structure looks like:
> .
> ├── index.org
> ├── posts
> │   ├── A.org
> │   ├── B.org
> │   └── C.org
> ├── misc
> │   ├── page.org
> │   └── other-page.org
> └── sitemap.org
>
> In index.org, I would have:
>
> #+begin_src org
> #+INCLUDE: sitemap.org::*posts :lines "-10" :only-contents t
> #+end_src
>
> to include links to the 10 most recent pages in =posts= (I use
> :sitemap-sort-files anti-chronologically in the project setup).  If I am not
> missing anything, this requires the sitemap.org file to have a =posts= 
> heading,
> but the `org-publish-org-sitemap' function only produces a list of pages.
>
> If there is no better way to get this to work, I would like to propose a patch
> to `org-publish-org-sitemap' to produce headings in the sitemap file when a 
> new
> parameter is passed and non-nil.  The attached patch is my first attempt at 
> it,
> it works for my tests.
>
> I would be interested to hear people's opinion on this:
> - Is there a better way to achieve what I want?
> - Is the proposed patch acceptable?  Any comments would be appreciated.

This reminds me of a patch Rasmus (Cc'ed) is working on (thread starting
at: ).

I'd like to propose here a slightly different, hopefully simpler
approach so as to get flexibility without entering keyword hell.

The first thing to note is that :sitemap-function is, IMO, unusable,
because it puts too much work on the hands of the user. Indeed, they
have to generate the title of the sitemap page, get the list of files in
the project, walk that list, handle sorting according to style...

I suggest to let :sitemap-function operate on the lists of files
included in the sitemap (i.e., the list of files in the project),
already ordered, and formatted according to
`org-publish-sitemap-file-entry-format'.

The list would be provided in the same format as the return value from
`org-list-to-lisp', so that, e.g., `org-list-to-subtree' can be directly
called on it.

Also, I suggest to make `org-publish-sitemap-file-entry-format'
a function instead of a string, so as to get more power, i.e., to not
limit ourselves to the list of placeholders allowed in the format
string. In particular, we could provide a public function
org-publish-get-keyword (file keyword &optional backend), much like what
Rasmus does in his patchset, but with a back-end so as to get the value
of any export keyword. Also, this would make
`org-publish-sitemap-dir-entry-format' unnecessary.

Eventually, we could run a hook at the end of `org-publish-org-sitemap',
which would now always be called, in order to give the opportunity to
modify the sitemap as a whole (e.g., the title).

In a nutshell, ISTM that it would solve both your request and the
difficulties encountered by Rasmus in changes.

WDYT?


Regards,

-- 
Nicolas Goaziou

Re: [O] ODT export

[Eduardo Mercovich]

Hi Philip.

>> First time out, very disappointing and confusing results.
>> Having created a styled example.odt file as per instructions in the manual...
>> [...]
>> (info "(org) Applying custom styles")
> Sanity check: anyone able to confirm they've done this successfully?

I did it, but a looong time ago. I don't remember how to and since those
times, I had a new machine and reinstalled emacs/org-mode from zero to
make it clean, sorry I can't help.

The good news is that -at least in some previous past- it worked. :)

Best...


-- 
eduardo mercovich 

 Donde se cruzan tus talentos 
 con las necesidades del mundo, 
 ahí está tu vocación.

[O] trying to automatically refresh inline images after org-babel-execute:ditaa

[Stig Brautaset]

Hello!

I'm trying to automatically update inline ditaa images, by adding this
advice:

,
|   (advice-add 'org-babel-execute:ditaa
|   :after
|   (lambda (a &rest b)
| (message "my sage advice")
| (org-redisplay-inline-images)))
`

When hitting =C-c C-c= in a =#+begin_src ditaa= block I *do* get my sage
advice printed to *Messages*, but inline images just blinks out of
existence. Is the image overlay removed at a higher level?

Any advice (hah!) welcome.

Stig

-- 
: Stig Brautaset, GNU Emacs 25.1.1, Org-mode version 8.3.6

Re: [O] trying to automatically refresh inline images after org-babel-execute:ditaa

[Grant Rettke]

On Tue, Oct 11, 2016 at 12:01 PM, Stig Brautaset  wrote:
> Hello!
>
> I'm trying to automatically update inline ditaa images, by adding this
> advice:
>
> ,
> |   (advice-add 'org-babel-execute:ditaa
> |   :after
> |   (lambda (a &rest b)
> | (message "my sage advice")
> | (org-redisplay-inline-images)))
> `
>
> When hitting =C-c C-c= in a =#+begin_src ditaa= block I *do* get my sage
> advice printed to *Messages*, but inline images just blinks out of
> existence. Is the image overlay removed at a higher level?
>
> Any advice (hah!) welcome.

(defun help/org-babel-after-execute-hook ()
  "HELP settings for the `org-babel-after-execute-hook'.

This does not interfere with exports.

Attribution: URL
`https://lists.gnu.org/archive/html/emacs-orgmode/2015-01/msg00534.html'"
  (interactive)
  (org-redisplay-inline-images))

(add-hook 'org-babel-after-execute-hook #'help/org-babel-after-execute-hook)

Re: [O] Export tangle filename with source block

[Nicolas Goaziou]

Hello,

Thibault Marin  writes:

> *Question 1*: Is the `org-element-src-block-parser' function supposed to 
> resolve
>  the tangle filename (including inheritance, i.e. to handle the 3 :tangle
>  sources listed above)?

No, it isn't.

> From the docstring, it would appear that it shouldn't return a :tangle keyword
> and that the tangling functions are responsible for choosing the output tangle
> file for each block.  Is this correct?

That's correct.

> ** Improvements (which I cannot get to work)
>
> - Add collected blocks to `info' in order to perform the collection only once
>   and re-use it for subsequent blocks: I couldn't get it to work, function
>   arguments seem to be passed by value (?)

They are not. You may want to see how cache is used with info in, e.g.,
`org-export-get-footnote-definition'.

> - Use `org-babel-tangle-single-block' to process only one block at a time, 
> this
>   sounds like the right method.  I believe I must first move point to the
>   src-block being processed, which I try to do with
>   (org-babel-goto-named-src-block src-block-name): this gives me the correct
>   tangle filename when run from a simple code snippet in the scratch buffer
>   (using (org-element-map (org-element-parse-buffer) ...)), but results in the
>   wrong tangle file when I do that within the `my-html-src-block' function 
> (the
>   :tangle options passed on the #+BEGIN_SRC line as in case 3. are ignored and
>   are always preempted by the inherited tangle value coming either from the
>   ,#+PROPERTY entry or the PROPERTY drawer value).  *Question 2*: How can I 
> use
>   `org-babel-tangle-single-block' within the custom src-block handling 
> function?
>   I notice the (point) value is different after the
>   (org-babel-goto-named-src-block src-block-name) call when used from the
>   `my-html-src-block' function (possibly due to some pre-processing performed 
> on
>   the buffer, I am not sure).

The buffer used during export is unlikely to be the same as the original
one. Macros are expanded, comments are removed and Babel code is
possibly evaluated. The only hook run in an exact copy of the original
buffer is `org-export-before-processing-hook'. You can collect anything
here, but INFO doesn't exist yet.

Regards,

-- 
Nicolas Goaziou

Re: [O] PDF font

[Eduardo Mercovich]

Hi Philip.

[...]
>>> What *do* you need exactly?

>> Cantarell for the sans-serif, FreeSerif for the serif, don't care
>> about the mono.

> Oh yes, and #cc for the title background.

HTML is easier to style, yes. Does that format, exported to pdf, has
what you need? Because latex may take more effort, but it's only once.
Then, you have pdfs with the index, pages of the size you'd like,
everything packaged in 1 file (or not), metadata, and so on.

I tried a bit of HTML as documents, but the un-packaged nature of it
(document + images + css + etc.) always gave me problems with other
people. Self contained pdfs, on the other hand, just work in every OS.

If the only specs you'd like to change are just those fonts, and
something like Memoir starts with a decent general layout (depending on
your needs), then it makes sense to tweak it a bit and from then on,
just use the latex export.

Best...


-- 
eduardo mercovich 

 Donde se cruzan tus talentos 
 con las necesidades del mundo, 
 ahí está tu vocación.

Re: [O] Best diagram, image software?

[Eduardo Mercovich]

Hi everyone. 

>> [...] What is the best way to make diagrams and
>> images? [...]

> Depends, what kind of images you are talking about. [...]

Agreed 200%.

Detail: if your result is vector like (not like a photo, but more like a
graph), you can export to pdf and include the pdf as it is. It works
perfectly directly for inside org.

Also, if your pdfs have raster images on them, check this great script
for compression:
http://www.tjansson.dk/2012/04/compressing-pdfs-using-ghostscript-under-linux/

Best...


-- 
eduardo mercovich 

 Donde se cruzan tus talentos 
 con las necesidades del mundo, 
 ahí está tu vocación.

[O] exporting latex to html

[Jeremie Juste]

Hello,

How is it possibile to modify the image attributes when exporting latex
to html?


For instance if I have a table in the following org-buffer. Doing
org-mime-org-buffer-htmlize convert the table into an image and put put
it in latex as a picture. I would like to control the size and quality
of this image


#+OPTIONS:   H:3 num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t 
tex:imagemagick

\begin{table}
\begin{center}
\begin{tabular}{l c }
\hline
   & Model 1 \\
\hline
test   & $0.46^{***}$ \\
   & $(0.00)$ \\
\hline
R$^2$  & 0.42 \\
Adj. R$^2$ & 0.42 \\
Num. obs.  & 27162\\
RMSE   & 7.97 \\
\hline
\multicolumn{2}{l}{\scriptsize{$^{***}p<0.001$, $^{**}p<0.01$, $^*p<0.05$}}
\end{tabular}
\caption{Statistical models}
\label{table:coefficients}
\end{center}
\end{table}


Best wishes,

Jeremie

[O] org-link interface

[Daniele Nicolodi]

Hello,

I would like to add a new link type to org-mode.  Following the example
in the manual it is a very easy task.  However I would like to customize
how the link is visualized, specifically I would like a link like
"[[foo:bar]]" to be visualized simply as "bar" where the protocol type
has been hidden (same effect I would obtain with a link in the form
"[[foo:bar][bar]]".

Is it possible to hook somehow into org-mode to have that transformation
done, or there is an easy way to accomplish that?

Thank you!

Cheers,
Daniele

[O] One org file to multiple pages static website.

[Pierre-Henry Frohring]

Hi!

Here is some code to go from one org-file to a multiple pages static
website,
one heading -> one post.

Since I did not find anything like it, did it myself, think maybe others may
find this helpful.

https://github.com/phfrohring/org-to-blog

Cheers!

Re: [O] One org file to multiple pages static website.

[Kaushal Modi]

Thanks for sharing this.

I have bookmarked something similar for the Hugo SSG:
http://www.holgerschurig.de/en/emacs-blog-from-org-to-hugo/

On Tue, Oct 11, 2016 at 7:04 PM Pierre-Henry Frohring <
frohring.pierrehe...@gmail.com> wrote:

> Hi!
>
> Here is some code to go from one org-file to a multiple pages static
> website,
> one heading -> one post.
>
> Since I did not find anything like it, did it myself, think maybe others
> may
> find this helpful.
>
> https://github.com/phfrohring/org-to-blog
>
> Cheers!
>
>
>
> --

Kaushal Modi

[O] member-ignore-case: Wrong type argument: stringp, nil

[Vikas Rawal]

I get this message when trying to export an org file (with embedded source code 
blocks) to latex:

member-ignore-case: Wrong type argument: stringp, nil

How do I go about figuring out what exactly is going wrong?

I have tried to isolate the problem by removing stuff from the file, to see 
when does the problem go away. Some source code blocks seem to cause it. If I 
remove them, the problem goes. But there is nothing in those code blocks.. For 
example, the one below is giving me trouble. 

#+NAME: australiafabainst
#+BEGIN_SRC R :results output graphics :exports results :file 
australia-faba-instability.png :width 1200 :height 700  :type cairo :family 
serif :session pulses

## Some R code here to make a graph

#+END_SRC

But there are many others like this, which are not giving any error.

Vikas

Re: [O] member-ignore-case: Wrong type argument: stringp, nil

[Vikas Rawal]

> On 12-Oct-2016, at 9:10 am, Vikas Rawal  
> wrote:
> 
> Wrong type argument: stringp, nil


Debug gives me this:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  compare-strings(nil 0 nil "CAPTION" 0 nil t)
  member-ignore-case(nil ("CAPTION"))
  #[0 "\212\214~\210`\300\206\306 
\211\211:\204\211;\205$\307\262
\202&\211@9\205$\211@\262
\310\211;\2037\311\312#\266\202\202?\313
A@\"\266\202\211\203\233
W\203\233\314
 
\210\315\316\n!\210)\317\320\321!\"\204d\322\323\"\210\202\225\312\225W\203t\312\225\324
 
}\210\202\225\325\224\203\220\325\224Y\203\220\325\225W\203\220\325\224\325\225}\210\202\225\322\323\"\210\326\262\202=
\327=\203\370\330\211;\203\262\311\312#\266\202\202\272\313
A@\"\266\202\211\203\305\331
 U\204\315\322\323\"\210\202\364\314 \210\332
\324 
\"\210\312\224b\210`Y\203\357\312\225W\203\357`\312\225}\210\202\364\322\323\"\210\210\202=
\333>\203R
\334\211;\203
\311\312#\266\202\202
\313
A@\"\266\202b\210\316\f!\210\335\225\211\204+
\322\323\"\210\202N
\335\224b\210\336\316
!)\203<
\312\225b\210`
Y\203J
\322\323\"\210\202N
`
}\210\210\202=
\337>\203\272
\340\211;\203i
\311\312#\266\202\202q
\313
A@\"\266\202\341\211;\203\202
\311\312#\266\202\202\212
\313
A@\"\266\202
\203\257
\211\203\257
Y\203\257

W\204\250

U\203\257
m\203\257


}\210\202\265
\322\323\"\210\266\202=
\342=\2038\343\211\203/\211@\211\211;\203\330
\311\312#\266\202\202\340
\313
A@\"\266\202\211\203'\334
\211;\203\365
\311\312#\266\202\202\375
\313
A@\"\266\202X\203'\344
\211;\203\311\312#\266\202\202\313
A@\"\266\202V\203'\322\323\"\210\210
A\266\202\202\301
\210\322\323\"\210\202=\322\323\"\210eb\210
\2119\203J\211\202e\211\211:\204[\211;\205c\307\262
\202e\211@9\205c\211@\262
3\236A\262
CC4\203~5\203~\345\346!\204\202\336\202\2236\203\217\3476\"\202\223\350
 \210\336C\336C\336C\336C\351\352\353\312\354\355\356





&\357\"\360\361%D\215\362\n\242\"\210\266\206\266\204*\207" [nil 
case-fold-search org-element--affiliated-re org-element-parsed-keywords 
org-complex-heading-regexp org-comment-string org-element-at-point plain-text 
:post-affiliated get-text-property 0 plist-get beginning-of-line t looking-at 
member-ignore-case match-string 1 throw objects-forbidden line-end-position 2 
keyword item :tag line-beginning-position search-forward (headline inlinetask) 
:begin 4 nil (paragraph table-row verse-block) :contents-begin :contents-end 
planning (:closed :deadline :scheduled) :end derived-mode-p org-mode gethash 
org-element-cache-reset exit funcall make-byte-code 
"\304\242\204\"\302\242\303\242\236\211\203\305
\240\210\202!\303\305\302\242\307D\240\303\242B\240\210\210\310\311\312\313\314\315\316\300\301\302\304\305%\317\"\320\321%D\215\210\304\242\203[\322\304\242\211;\203N\323\313#\266\202\202V\324
A@\"\266\202\300V\203i\325\326\306\242\206d\302\242\"\210\202\327\304\242\211;\203{\323\313#\266\202\202\203\324
A@\"\266\202\330\304\242\211;\203\225\323\313#\266\202\202\235\324
A@\"\266\202\331\304\242\211;\203\257\323\313#\266\202\202\267\324
A@\"\266\202\300X\203\334dU\204\334b\210\300U\203T
`Sf\332>\204T
\306\304\242\240\210\202T

\203N
\211\203N
\300Y\203N
\300
W\204
\300
U\203N
d\300U\204
\300\206

`Sf\333>\204N

b\210`
}\210\302\304\242\240\210\301\304\242\2119\203
 

\211\202;
\211\211:\2041
\211;\2059
\334\262
\202;
\211@9\2059
\211@\262
\236A\262
\240\210\304\307\240\210\305\307\240\210\202T
\325\326\304\242\"\210\266\202"
 vconcat vector [nil found funcall make-byte-code 0 
"\303\242\203\303\305\301\242!\240\210\202\312\304\242\211AA\262
\304\242A@
\204+\211\203+\306\307\302\242\"\210\202\310
\2049\303\305\301\242!\240\210\202\310\310@\211;\203K\311\312#\266\202\202S\313
A@\"\266\202\211\300Y\203\275\211\203\263\211@\314
\211;\203q\311\312#\266\202\202y\313
A@\"\266\202\300X\203\254\310
\211;\203\217\311\312#\266\202\202\227\313
A@\"\266\202\300Y\203\246\306\315\303\240\"\210\202\254\306\307\302\242\"\210
A\266\202\202Z\306\307\302\242\"\266\202\307\211b\210\303\305\301\242!\240\210\210\266\303\242\203
\303\242\316\302\242;\203\344\317\320$\266\203\202\362A\321A@#\240\210\266\203\210\304\242\211A\303\242\211AA\262
B\241\207\304\242A\322\240\207"
 vconcat vector [org-element--object-lex throw exit :end get-text-property 0 
plist-get :begin found :parent org-add-props nil plist-put t] 11 "\n\n(fn)" 
:begin get-text-property plist-get throw exit :end :contents-begin 
:contents-end (32 9) (32 9) plain-text org-element-object-restrictions] 12 
"\n\n(fn)" ...] 24 "\n\n(fn)"]()
  funcall(#[0 "\212\214~\210`\300\206\306 
\211\211:\204\211;\205$\307\262
\202&\211@9\205$\211@\262
\310\211;\2037\311\312#\266\202\202?\313
A@\"\266\202\211\203\233
W\203\233\314
 
\210\315\316\n!\210)\317\320\321!\"\204d\322\323\"\210\202\225\312\225W\203t\312\225\324
 
}\2

Re: [O] Export tangle filename with source block

[Thibault Marin]

Thanks for your reply, it is very helpful.

Nicolas Goaziou writes:
> They are not. You may want to see how cache is used with info in, e.g.,
> `org-export-get-footnote-definition'.
That looks like what I was trying to achieve (except better), thanks.

> The buffer used during export is unlikely to be the same as the original
> one. Macros are expanded, comments are removed and Babel code is
> possibly evaluated. The only hook run in an exact copy of the original
> buffer is `org-export-before-processing-hook'. You can collect anything
> here, but INFO doesn't exist yet.

OK, then it looks like I may be able to build a list of source block
name/tangle filename pairs on pre-processing, store it in a global
variable and use it when processing source-blocks.  It is probably a
little hack-ish but that would be fine for me.  On my initial attempt,
`org-babel-tangle-collect-blocks' seems to be skipping blocks on one of
my tests, but I haven't spent much time on it yet, I'll report back.

Thanks again for the help.
Best,
thibault

Re: [O] Use headings in sitemap

[Thibault Marin]

Nicolas Goaziou writes:
> This reminds me of a patch Rasmus (Cc'ed) is working on (thread starting
> at: ).
I missed that for some reason, it is better and more ambitious.

> I suggest to let :sitemap-function operate on the lists of files
> included in the sitemap (i.e., the list of files in the project),
> already ordered, and formatted according to
> `org-publish-sitemap-file-entry-format'.
>
> The list would be provided in the same format as the return value from
> `org-list-to-lisp', so that, e.g., `org-list-to-subtree' can be directly
> called on it.
That sounds good to me.

> Also, I suggest to make `org-publish-sitemap-file-entry-format'
> a function instead of a string, so as to get more power, i.e., to not
> limit ourselves to the list of placeholders allowed in the format
> string. In particular, we could provide a public function
> org-publish-get-keyword (file keyword &optional backend), much like what
> Rasmus does in his patchset, but with a back-end so as to get the value
> of any export keyword. Also, this would make
> `org-publish-sitemap-dir-entry-format' unnecessary.
>
> Eventually, we could run a hook at the end of `org-publish-org-sitemap',
> which would now always be called, in order to give the opportunity to
> modify the sitemap as a whole (e.g., the title).
>
> In a nutshell, ISTM that it would solve both your request and the
> difficulties encountered by Rasmus in changes.
>
> WDYT?
I think it would definitely address my needs and clearly improve the
overall process.  I'll need some time to digest this as I am not too
familiar with the process, but please let me know how I can help with
this (implementation and testing).

Thanks.
thibault