Re: Developing Moodle resources/sites with Org Mode

[Denis Bitouzé]

Le 17/01/24 à 19h23, Leo Butler a écrit :

> I have used org-mode to do all my STACK question authoring for a few
> years now [1]. I do all the writing in emacs and then copy/paste into the
> STACK textareas, test, repeat. It is not elegant, but it is easier than
> working in a web-browser. It would be really nice to be able to create
> the entire question in emacs, because defining graders in STACK is
> pretty tedious.

Maybe the ~moodle~ LaTeX package, which helps for the generation of
Moodle quizzes via LaTeX could be helpful:

  ┌
  │ https://www.ctan.org/pkg/moodle
  └

Just my 2 cents.
-- 
Denis

Re: Option that prevents Org to add \lstset{language=⟨language⟩,...} when code blocks are exported to LaTeX

[Denis Bitouzé]

Le 18/10/22 à 04h14, Ihor Radchenko a écrit :

> Denis Bitouzé  writes:
>
>> here is a feature request about the LaTeX export.
>>
>> With ~(setq org-latex-listings t)~, code blocks such as:
>>
>>   ┌
>>   │ #+BEGIN_SRC ⟨language⟩ :exports code
>>   │ ...
>>   │ #+END_SRC
>>   └
>>
>> are exported to LaTeX into:
>>
>>   ┌
>>   │ \lstset{language=⟨language⟩,label= ,caption= ,captionpos=b,numbers=none}
>>   │ \begin{lstlisting}
>>   │ ...
>>   │ \end{lstlisting}
>>   └
>>
>> But the:
>>
>>   ┌
>>   │ \lstset{language=⟨language⟩,label= ,caption= ,captionpos=b,numbers=none}
>>   └
>>
>> systematically added before each of the ~lstlisting~ LaTeX environments
>> is not always desirable and let me explain why.
>
> Confirmed.
> Is there a way to apply \lstset locally for the environment?

It is enough to put it in a group:

  ┌
  │ \bgroup
  │ \lstset{...}
  │ \begin{lstlisting}
  │ ...
  │ \end{lstlisting}
  │ \egroup
  └

Otherwise, all the options specified by `\lstset` can be applied as an
option of the `lstlisting` environment:

  ┌
  │ \begin{lstlisting}[language=⟨language⟩,...]
  └
-- 
Denis

Export (to `LaTeX`) `~⟨code snippet⟩~` into `\lstinline+⟨code snippet⟩+` (just as does `src_⟨language⟩{⟨code snippet⟩}`)

[Denis Bitouzé]

Hi,

here is a feature request about the LaTeX export (another one: the
previous mine, https://list.orgmode.org/87zgmda67z@example.com/,
sadly didn't get any answer).

With `(setq org-latex-listings t)`, `src_⟨language⟩{⟨code snippet⟩}` is
exported from `org-mode` to `LaTeX` into
`\lstinline[language=⟨language⟩]~⟨code snippet⟩~` (here, `~` could be
almost any token): so far, so good.

But one could expect to get the same export with the usual `org-mode`
syntax for code snippets: `~⟨code snippet⟩~` (this supposes the ⟨language⟩
to be declared globally), as in the following example:

--8<---cut here---start->8---
#+OPTIONS:   toc:nil title:nil

#+LaTeX_HEADER: \usepackage{xcolor}
#+LaTeX_HEADER: \usepackage{listings}
#+LaTeX_HEADER: 
\lstset{language=[auto]lisp,basicstyle=\ttfamily,keywordstyle=\color{red}}

#+PROPERTY: header-args :padline no :exports both :noweb yes :eval always

src_lisp{defun} is fun!

~defun~ is fun!
--8<---cut here---end--->8---

For this, it is possible to redefine the `org-latex-code` function:

--8<---cut here---start->8---
;; Inspired by https://emacs.stackexchange.com/q/70720/5267
(defun org-latex-code (code _contents info)
  "Transcode a CODE object from Org to LaTeX.
CONTENTS is nil.  INFO is a plist used as a communication
channel."
  (format "\\lstinline+%s+"
  (org-element-property :value code)))
--8<---cut here---end--->8---

but, IMHO, this should be the default.

WDYT?
-- 
Denis

Option that prevents Org to add \lstset{language=⟨language⟩,...} when code blocks are exported to LaTeX

[Denis Bitouzé]

Hi,

here is a feature request about the LaTeX export.

With ~(setq org-latex-listings t)~, code blocks such as:

  ┌
  │ #+BEGIN_SRC ⟨language⟩ :exports code
  │ ...
  │ #+END_SRC
  └

are exported to LaTeX into:

  ┌
  │ \lstset{language=⟨language⟩,label= ,caption= ,captionpos=b,numbers=none}
  │ \begin{lstlisting}
  │ ...
  │ \end{lstlisting}
  └

But the:

  ┌
  │ \lstset{language=⟨language⟩,label= ,caption= ,captionpos=b,numbers=none}
  └

systematically added before each of the ~lstlisting~ LaTeX environments
is not always desirable and let me explain why.

Sometimes, you want the ~listings~ package to have some global settings
that are overridden by this ~\lstset{...}~ added by Org. Typically, you
may define some dialects ⟨dialect1⟩, ..., ⟨dialectN⟩ of a given
⟨language⟩ and you want to load them in addition to the (main)
⟨language⟩. This can be done by the following global setting:

  ┌
  │ \lstset{
  │ language=⟨language⟩,
  │ alsolanguage=[⟨dialect1⟩]⟨language⟩,
  │ ...
  │ alsolanguage=[⟨dialectN⟩]⟨language⟩,
  │ }
  └

Unfortunately, it is overridden by each ~\lstset{...}~ added by Org.

So would it be possible to provide an option that prevents Org to add
these systematic:

  ┌
  │ \lstset{language=⟨language⟩,label= ,caption= ,captionpos=b,numbers=none}
  └

Thanks!
-- 
Denis

Re: [O] Bug: The headers' anchors from custom ids should be at the beginning, and not at the end, of these headers [8.3.1 (8.3.1-129-ga7c8d2-elpa @ /home/bitouze/.emacs.d/elpa/org-20150921/)]

[Denis Bitouzé]

Le 22/09/15 à 21h39, Nicolas Goaziou  a écrit :

> Hello,

Hello,

>> As you can see, the anchor in the .md file is at the end of the header and, 
>> in
>> case this header contains long text, clicking on a link to this anchor would
>> lead us to the end, eventually not at the first line, of this header.
>
> True. But there's a trade-off: putting anchor at the beginning of the
> heading is less readable.

I don't see your point.

1. What is less readable: the anchor or, if the anchor is at its
   beginning, the heading ?
2. At what level is it less readable: .org or .md or .html, etc.?

Regards,
-- 
Denis

Re: [O] Bug: The headers' anchors from custom ids should be at the beginning, and not at the end, of these headers [8.3.1 (8.3.1-129-ga7c8d2-elpa @ /home/bitouze/.emacs.d/elpa/org-20150921/)]

[Denis Bitouzé]

Le 22/09/15 à 22h01, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit :

> Denis Bitouzé <dbitouze-39zsbgiqgt5gwvitb5q...@public.gmane.org> writes:
>
>> I don't see your point.
>>
>> 1. What is less readable: the anchor or, if the anchor is at its
>>beginning, the heading ?
>
> The latter.
>
>> 2. At what level is it less readable: .org or .md or .html, etc.?
>
> .md

OK but, AFAICS, markdown export from org mode is usually not intended to
be read, isn't it?

Regards.
-- 
Denis

Re: [O] Bug: Custom id taken into account with html, but not with markdown, exports [8.3.1 (8.3.1-123-g823cad-elpa @ /home/bitouze/.emacs.d/elpa/org-20150914/)]

[Denis Bitouzé]

Le 21/09/15 à 08h30, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit :

> Hello,
>
> Denis Bitouzé <dbitouze-39zsbgiqgt5gwvitb5q...@public.gmane.org> writes:
>
>> BTW, do you agree with the other issue I reported:
>>
>> #+begin_src org
>> - A [[/rootsite/somepage/][(relative) page]].
>> - A [[/rootsite/somepage][(relative) page]].
>> #+end_src
>>
>> is exported as:
>>
>> #+begin_src markdown
>> -   A [(relative) page](file:///rootsite/somepage/).
>> -   A [(relative) page](file:///rootsite/somepage).
>> #+end_src
>>
>> whereas, IMHO, the expected behavior should be:
>>
>> #+begin_src markdown
>> -   A [(relative) page](/rootsite/somepage/).
>> -   A [(relative) page](/rootsite/somepage).
>> #+end_src
>
> Not really. If a link URI starts with "/", it is assumed to be an
> absolute file name.

Is it a shared rule? Using relative file names is rather common in
CMS...

And this rule is not the same applied for image files:

#+begin_src org
[[/rootsite/somepath/file.png]]
#+end_src

leads to:

#+begin_src markdown
![img](/rootsite/somepath/file.png)
#+end_src

and not to:

#+begin_src markdown
![img](file:///rootsite/somepath/file.png)
#+end_src

> Try prepending http:// to your URL.

#+begin_src org
- A [[http:///rootsite/somepage/][(relative) page]].
#+end_src

leads to:

#+begin_src markdown
[(relative) page](http:///rootsite/somepage/)
#+end_src

which is the interpreted as is when rendered as html page as:

#+begin_src html
http:///rootsite/somepage/;>(relative) page
#+end_src

hence isn't relevant.

Regards.
-- 
Denis

[O] Bug: The headers' anchors from custom ids should be at the beginning, and not at the end, of these headers [8.3.1 (8.3.1-129-ga7c8d2-elpa @ /home/bitouze/.emacs.d/elpa/org-20150921/)]

[Denis Bitouzé]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.


The following org file:

#+begin_src org
* Heading with custom id
:PROPERTIES:
:CUSTOM_ID: custom-id-heading
:END:

* Heading bis with custom id and very very very very very very very very very 
very very very very very very very very very very very very very very very long 
text
:PROPERTIES:
:CUSTOM_ID: custom-id-heading-bis
:END:

See [[#custom-id-heading-bis][heading bis with custom id and very long text]].
#+end_src

is exported as markdown to:

#+begin_src markdown

Table of Contents


1. Heading with custom id
2. Heading bis with custom id and very 
very very very very very very very very very very very very very very very very 
very very very very very very very long text




# Heading with custom id

# Heading bis with custom id and very very very very very very very very very 
very very very very very very very very very very very very very very very long 
text

See [heading bis with custom id and very long text](#custom-id-heading-bis).
#+end_src

As you can see, the anchor in the .md file is at the end of the header and, in
case this header contains long text, clicking on a link to this anchor would
lead us to the end, eventually not at the first line, of this header.

The expected behavior would be:

#+begin_src markdown

Table of Contents


1. Heading with custom id
2. Heading bis with custom id and very 
very very very very very very very very very very very very very very very very 
very very very very very very very long text




# Heading with custom id

# Heading bis with custom id and very very 
very very very very very very very very very very very very very very very very 
very very very very very very long text

See [heading bis with custom id and very long text](#custom-id-heading-bis).
#+end_src

I didn't look at it but, from this point of view, I guess other exports are
suboptimal as well.

Emacs  : GNU Emacs 24.5.1 (i686-pc-linux-gnu, GTK+ Version 3.14.8)
 of 2015-06-29 on drums.chezmoi.fr
Package: Org-mode version 8.3.1 (8.3.1-129-ga7c8d2-elpa @ 
/home/bitouze/.emacs.d/elpa/org-20150921/)

current state:
==
(setq
 org-entities-user '(("nok" "{\\color{red}\\ding{55}}" nil "" "NOK"
  "NOK" "✘")
 ("ok" "{\\color{checkmark}\\ding{51}}" nil ""
  "OK" "OK" "✔")
 )
 org-enforce-todo-checkbox-dependencies t
 org-inlinetask-default-state "TODO"
 org-agenda-search-view-always-boolean t
 org-agenda-log-mode-items '(clock)
 org-latex-format-headline-function 'leuven--org-latex-format-headline
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point 
org-babel-execute-safely-maybe)
 org-pretty-entities t
 org-latex-packages-alist '(("" "listings") ("" "xcolor") ("french" "babel"))
 org-html-format-inlinetask-function 
'org-html-format-inlinetask-default-function
 org-stuck-projects '("+LEVEL=2/-DONE" ("TODO" "STRT") nil "")
 org-refile-use-cache t
 org-clock-in-resume t
 org-clock-out-when-done nil
 org-log-states-order-reversed nil
 org-odt-preferred-output-format "doc"
 org-agenda-sticky t
 org-goto-interface 'outline-path-completion
 outline-minor-mode-hook '(leuven--outline-minor-mode-hook
   (lambda nil
(if (and outline-minor-mode (derived-mode-p (quote
 
emacs-lisp-mode)))
 (progn (hide-sublevels 1000)))
)
   )
 org-agenda-skip-scheduled-if-done t
 org-ellipsis " ►"
 org-clock-persist t
 org-archive-location "::* Archive"
 org-agenda-window-setup 'current-window
 org-adapt-indentation nil
 org-agenda-entry-text-leaders "   │ "
 org-agenda-scheduled-leaders '("Scheduled  " "   ")
 org-clock-mode-line-total 'all
 org-tab-first-hook '(org-hide-block-toggle-maybe
  org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-agenda-exporter-settings '((ps-number-of-columns 1) (ps-landscape-mode t)
(htmlize-output-type (quote css)))
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-refile-targets '((nil :maxlevel . 4) (nil :maxlevel . 2))
 org-html-htmlize-output-type 'css
 org-modules '(org-info org-habit org-gnus org-id org-checklist)
 org-cycle-hook '(org-inlinetask-hide-tasks org-cycle-hide-archived-subtrees
  org-cycle-hide-drawers
  org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change)
 org-html-checkbox-type 'unicode
 org-mime-send-subtree-hook '((lambda nil
   (org-entry-put (point) 

Re: [O] Bug: Internal links broken when exporting from org mode to markdown and odt [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Le 19/09/15 à 00h06, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit :

> Denis Bitouzé <dbitouze-39zsbgiqgt5gwvitb5q...@public.gmane.org> writes:
>
>> Via ELPA, it will be okay?
>
> It should. There is a new ELPA release every week.

OK, thanks.

>> I should have been more explicit, sorry: AFAICS, when clicking on the
>> "another" link, we jump *not* at the second section but at its
>> corresponding entry in the TOC.
>
> This should be fixed too.

AFAICS, that's not the case with Org-mode version 8.3.1
(8.3.1-123-g823cad-elpa @ /home/bitouze/.emacs.d/elpa/org-20150914/)

and e.g.:

#+begin_src org
* One section
See the [[another][another]] section.
* Another section<>
#+end_src

The "another" link points, not to the "Another section", but to its
corresponding entry in the TOC.

> Thank you.

You're welcome: many thanks to you !

Regards.
--
Denis

[O] Bug: Custom id taken into account with html, but not with markdown, exports [8.3.1 (8.3.1-123-g823cad-elpa @ /home/bitouze/.emacs.d/elpa/org-20150914/)]

[Denis Bitouzé]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.


When the following org mode file:

#+begin_src org
* Heading with custom id
:PROPERTIES:
:CUSTOM_ID: custom-id-heading
:END:

See [[#custom-id-heading][heading with custom id]].
#+end_src

is exported to html, the org mode :CUSTOM_ID: "custom-id-heading" is an
anchor (as html id attribute):

#+begin_src html
[...]
Table of Contents


1. Heading with custom id


[...]
1 Heading with custom id
[...]
See heading with custom id.
[...]
#+end_src

but, when exported to markdown, the org mode :CUSTOM_ID:
"custom-id-heading" is not an anchor (and the link
href="#custom-id-heading" points nowhere):

#+begin_src markdown
[...]

Table of Contents


1. Heading with custom id




# Heading with custom id

See heading with custom id (See section 1).
#+end_src

Expected result:

#+begin_src markdown
[...]

Table of Contents


1. Heading with custom id




# Heading with custom id

See heading with custom id.
#+end_src

Emacs  : GNU Emacs 24.5.1 (i686-pc-linux-gnu, GTK+ Version 3.14.8)
 of 2015-06-29 on drums.chezmoi.fr
Package: Org-mode version 8.3.1 (8.3.1-123-g823cad-elpa @ 
/home/bitouze/.emacs.d/elpa/org-20150914/)

current state:
==
(setq
 org-entities-user '(("nok" "{\\color{red}\\ding{55}}" nil "" "NOK"
  "NOK" "✘")
 ("ok" "{\\color{checkmark}\\ding{51}}" nil ""
  "OK" "OK" "✔")
 )
 org-enforce-todo-checkbox-dependencies t
 org-inlinetask-default-state "TODO"
 org-agenda-search-view-always-boolean t
 org-agenda-log-mode-items '(clock)
 org-latex-format-headline-function 'leuven--org-latex-format-headline
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point 
org-babel-execute-safely-maybe)
 org-pretty-entities t
 org-latex-packages-alist '(("" "listings") ("" "xcolor") ("french" "babel"))
 org-html-format-inlinetask-function 
'org-html-format-inlinetask-default-function
 org-stuck-projects '("+LEVEL=2/-DONE" ("TODO" "STRT") nil "")
 org-refile-use-cache t
 org-clock-in-resume t
 org-clock-out-when-done nil
 org-log-states-order-reversed nil
 org-odt-preferred-output-format "doc"
 org-agenda-sticky t
 org-goto-interface 'outline-path-completion
 outline-minor-mode-hook '(leuven--outline-minor-mode-hook
   (lambda nil
(if (and outline-minor-mode (derived-mode-p (quote
 
emacs-lisp-mode)))
 (progn (hide-sublevels 1000)))
)
   )
 org-agenda-skip-scheduled-if-done t
 org-ellipsis " ►"
 org-clock-persist t
 org-archive-location "::* Archive"
 org-agenda-window-setup 'current-window
 org-adapt-indentation nil
 org-agenda-entry-text-leaders "   │ "
 org-agenda-scheduled-leaders '("Scheduled  " "   ")
 org-clock-mode-line-total 'all
 org-tab-first-hook '(org-hide-block-toggle-maybe
  org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-agenda-exporter-settings '((ps-number-of-columns 1) (ps-landscape-mode t)
(htmlize-output-type (quote css)))
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-refile-targets '((nil :maxlevel . 4) (nil :maxlevel . 2))
 org-html-htmlize-output-type 'css
 org-modules '(org-info org-habit org-gnus org-id org-checklist)
 org-cycle-hook '(org-inlinetask-hide-tasks org-cycle-hide-archived-subtrees
  org-cycle-hide-drawers
  org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change)
 org-html-checkbox-type 'unicode
 org-mime-send-subtree-hook '((lambda nil
   (org-entry-put (point) "mail_composed"
(current-time-string)))
  )
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-confirm-babel-evaluate nil
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-src-window-setup 'current-window
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-export-preprocess-hook '(leuven--org-export-preprocess-hook)
 org-clock-total-time-cell-format "%s"
 org-export-snippet-translation-alist '(("b" . "beamer") ("l" . "latex") ("h" . 
"html"))
 org-agenda-current-time-string "Right now"
 org-blocker-hook '(org-block-todo-from-checkboxes 
org-block-todo-from-children-or-siblings-or-parent)
 org-fontify-done-headline t
 org-agenda-skip-deadline-prewarning-if-scheduled 7
 org-agenda-restore-windows-after-quit t
 org-return-follows-link t
 org-babel-pre-tangle-hook '(save-buffer)

Re: [O] Bug: [Markdown export] Relative pages considered as files if links' targets [8.3.1 (8.3.1-123-g823cad-elpa /home/bitouze/.emacs.d/elpa/org-20150914/)]

[Denis Bitouzé]

Rasmus  gmx.us> writes:

> What if you add a dot? 
> 
> #+begin_src org
> - A [[./rootsite/somepage/][(relative) page]].
> - A [[./rootsite/somepage][(relative) page]].
> #+end_src
> 
> ⇒
> 
> #+begin_src markdown
> -   A [(relative) page](./rootsite/somepage/).
> -   A [(relative) page](./rootsite/somepage).
> #+end_src

It doesn't give the expected result neither because, if this link is
entered on the page /rootsite/anotherpage, it will point to:

  ┌
  │ /rootsite/anotherpage/rootsite/somepage/
  └
-- 
Denis

[O] Bug: [Markdown export] Relative pages considered as files if links' targets [8.3.1 (8.3.1-123-g823cad-elpa @ /home/bitouze/.emacs.d/elpa/org-20150914/)]

[Denis Bitouzé]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.


Sometimes, you need to have links, the targets of which are relative
pages of your site. Unfortunately, when exported to Markdown, these
relative pages are considered as files:

#+begin_src org
- A [[/rootsite/somepage/][(relative) page]].
- A [[/rootsite/somepage][(relative) page]].
#+end_src

is exported as:

#+begin_src markdown
-   A [(relative) page](file:///rootsite/somepage/).
-   A [(relative) page](file:///rootsite/somepage).
#+end_src

whereas the expected behavior would be:

#+begin_src markdown
-   A [(relative) page](/rootsite/somepage/).
-   A [(relative) page](/rootsite/somepage).
#+end_src

Emacs  : GNU Emacs 24.5.1 (i686-pc-linux-gnu, GTK+ Version 3.14.8)
 of 2015-06-29 on drums.chezmoi.fr
Package: Org-mode version 8.3.1 (8.3.1-123-g823cad-elpa @ 
/home/bitouze/.emacs.d/elpa/org-20150914/)

current state:
==
(setq
 org-entities-user '(("nok" "{\\color{red}\\ding{55}}" nil "" "NOK"
  "NOK" "✘")
 ("ok" "{\\color{checkmark}\\ding{51}}" nil ""
  "OK" "OK" "✔")
 )
 org-enforce-todo-checkbox-dependencies t
 org-inlinetask-default-state "TODO"
 org-agenda-search-view-always-boolean t
 org-agenda-log-mode-items '(clock)
 org-latex-format-headline-function 'leuven--org-latex-format-headline
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point 
org-babel-execute-safely-maybe)
 org-pretty-entities t
 org-latex-packages-alist '(("" "listings") ("" "xcolor") ("french" "babel"))
 org-html-format-inlinetask-function 
'org-html-format-inlinetask-default-function
 org-stuck-projects '("+LEVEL=2/-DONE" ("TODO" "STRT") nil "")
 org-refile-use-cache t
 org-clock-in-resume t
 org-clock-out-when-done nil
 org-log-states-order-reversed nil
 org-odt-preferred-output-format "doc"
 org-agenda-sticky t
 org-goto-interface 'outline-path-completion
 outline-minor-mode-hook '(leuven--outline-minor-mode-hook
   (lambda nil
(if (and outline-minor-mode (derived-mode-p (quote
 
emacs-lisp-mode)))
 (progn (hide-sublevels 1000)))
)
   )
 org-agenda-skip-scheduled-if-done t
 org-ellipsis " ►"
 org-clock-persist t
 org-archive-location "::* Archive"
 org-agenda-window-setup 'current-window
 org-adapt-indentation nil
 org-agenda-entry-text-leaders "   │ "
 org-agenda-scheduled-leaders '("Scheduled  " "   ")
 org-clock-mode-line-total 'all
 org-tab-first-hook '(org-hide-block-toggle-maybe
  org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-agenda-exporter-settings '((ps-number-of-columns 1) (ps-landscape-mode t)
(htmlize-output-type (quote css)))
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-refile-targets '((nil :maxlevel . 4) (nil :maxlevel . 2))
 org-html-htmlize-output-type 'css
 org-modules '(org-info org-habit org-gnus org-id org-checklist)
 org-cycle-hook '(org-inlinetask-hide-tasks org-cycle-hide-archived-subtrees
  org-cycle-hide-drawers
  org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change)
 org-html-checkbox-type 'unicode
 org-mime-send-subtree-hook '((lambda nil (org-entry-put (point) "mail_composed"
   (current-time-string)))
  )
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-confirm-babel-evaluate nil
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-src-window-setup 'current-window
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-export-preprocess-hook '(leuven--org-export-preprocess-hook)
 org-clock-total-time-cell-format "%s"
 org-export-snippet-translation-alist '(("b" . "beamer") ("l" . "latex") ("h" . 
"html"))
 org-agenda-current-time-string "Right now"
 org-blocker-hook '(org-block-todo-from-checkboxes 
org-block-todo-from-children-or-siblings-or-parent)
 org-fontify-done-headline t
 org-agenda-skip-deadline-prewarning-if-scheduled 7
 org-agenda-restore-windows-after-quit t
 org-return-follows-link t
 org-babel-pre-tangle-hook '(save-buffer)
 org-agenda-diary-file "~/org/diary.org"
 org-export-time-stamp-file nil
 org-occur-hook '(org-first-headline-recenter)
 org-emphasis-alist '(("*" bold "" "") ("/" italic "" "")
  ("_" underline "" "")
  ("=" org-verbatim "" "" verbatim)
  ("~" org-code "" "" 

Re: [O] Bug: Internal links broken when exporting from org mode to markdown and odt [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Le 20/09/15 à 13h26, Nicolas Goaziou  a écrit :

> The fix is only 2 days old and is not included in Org ELPA yet.

OK, thanks, sorry to have been so impatient :)

Regards.
-- 
Denis

Re: [O] Bug: Custom id taken into account with html, but not with markdown, exports [8.3.1 (8.3.1-123-g823cad-elpa @ /home/bitouze/.emacs.d/elpa/org-20150914/)]

[Denis Bitouzé]

Le 20/09/15 à 23h01, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit :

> Hello,

Hello,

> dbito...@wanadoo.fr (Denis Bitouzé) writes:
>
>> When the following org mode file:
>>
>> #+begin_src org
>> * Heading with custom id
>> :PROPERTIES:
>> :CUSTOM_ID: custom-id-heading
>> :END:
>>
>> See [[#custom-id-heading][heading with custom id]].
>> #+end_src
>>
>> is exported to html, the org mode :CUSTOM_ID: "custom-id-heading" is an
>> anchor (as html id attribute):
>>
>> #+begin_src html
>> [...]
>> Table of Contents
>> 
>> 
>> 1. Heading with custom id
>> 
>> 
>> [...]
>> > class="section-number-2">1 Heading with custom id
>> [...]
>> See heading with custom id.
>> [...]
>> #+end_src
>>
>> but, when exported to markdown, the org mode :CUSTOM_ID:
>> "custom-id-heading" is not an anchor (and the link
>> href="#custom-id-heading" points nowhere):
>>
>> #+begin_src markdown
>> [...]
>> 
>> Table of Contents
>> 
>> 
>> 1. Heading with custom id
>> 
>> 
>> 
>>
>> # Heading with custom id
>>
>> See heading with custom id (See section 1).
>> #+end_src
>
> Both issues fixed.

Thanks so much!

BTW, do you agree with the other issue I reported:

#+begin_src org
- A [[/rootsite/somepage/][(relative) page]].
- A [[/rootsite/somepage][(relative) page]].
#+end_src

is exported as:

#+begin_src markdown
-   A [(relative) page](file:///rootsite/somepage/).
-   A [(relative) page](file:///rootsite/somepage).
#+end_src

whereas, IMHO, the expected behavior should be:

#+begin_src markdown
-   A [(relative) page](/rootsite/somepage/).
-   A [(relative) page](/rootsite/somepage).
#+end_src

Anyway, thanks again! :)

Regards.
-- 
Denis

Re: [O] Bug: Extra blank line in subitem list when exported to markdown [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Le 16/09/15 à 14h51, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit :

> Denis Bitouzé <dbitouze-39zsbgiqgt5gwvitb5q...@public.gmane.org> writes:
>
>> Well, please, don't trust me too quickly :) I must admit I'm very far
>> from a mardown expert: I'm only a very occasional user.
>
> I never use markdown myself. Between the two of us, you are de facto
> the expert.

;)

>> In fact, my suggestion was wrong: AFAICS, the last example doesn't give
>> the expected HTML result neither and the less bad solution for nested
>> lists in markdown seems to be:
>>
>> #+NAME: test.md
>> #+begin_src markdown
>> -   Foo 1
>>
>> -   Foo 2:
>>
>> -   Foo 21
>> -   Foo 22
>>
>> End of Foo 2 item.
>> #+end_src
>>
>> which is interpreted as (rather ugly):
>>
>> #+begin_src html
>> 
>>   
>> Foo 1:
>>   
>>   
>> Foo 2:
>> 
>>   Foo 21
>>   Foo 22
>> 
>> End of Foo 2 item.
>>   
>> 
>> #+end_src
>
> This is problematic. There is a rule in "ox-md" that contradicts what
> you are suggesting. From org-md-separate-elements's docstring:
>
>   2. In an item, remove any blank line before the very first
>  paragraph and the next sub-list.
>
> As a consequence, we try hard to produce
>
>   -   Foo 2:
>   -   Foo 21
>   -   Foo 22
>
> instead of
>
>   -   Foo 2:
>
>   -   Foo 21
>   -   Foo 22
>
> which was the case in early versions of Markdown exporter. I guess we
> should produce the latter only when the sub-list is followed by another
> block element, e.g., "End of Foo 2 item".
>
> WDYT?

Indeed but maybe my usecase is too specific for consuming time on it...

>>> Also, what about other block types, e.g., which one is valid:
>>>
>>>   - Foo 1
>>>   - Foo 2:
>>> - Foo 21
>>> - Foo 22
>>>
>>> #+begin_example
>>> Some example
>>> #+end_example
>>>
>>> or
>>>
>>>   - Foo 1
>>>   - Foo 2:
>>> - Foo 21
>>> - Foo 22
>>> #+begin_example
>>> Some example
>>> #+end_example
>>
>> I'm not sure to understand what you have in mind: are these last two
>> examples at org mode level?
>
> I'm trying to generalize the rule. Your previous suggestion applied to
> paragraphs. I wondered if it was the same with other block types, e.g.,
> example blocks.

Indeed, this a problem as the Markdown export will put "Some example" on
a separate line as well.

Maybe other more experienced Markdown users could help.

Regards,
-- 
Denis

Re: [O] Please confirm your message

[Denis Bitouzé]

Le 14/09/15 à 08h36, Gmane Remailer 
 a écrit :

> This message was created automatically by mail delivery software (TMDA).
>
> Your message attached below is being held because the address
> <dbito...@wanadoo.fr> has not been verified.
>
> To release your message for delivery, please send an empty message
> to the following address, or use your mailer's "Reply" feature.
>
>
> public-emacs-orgmode-mXXj517/zsq-confirm-1442212612.9320.da9...@plane.gmane.org
>
> This confirmation verifies that your message is legitimate and not
> junk-mail. You should only have to confirm your address once.
>
> If you do not respond to this confirmation request within 14 days,
> your message will not be delivered.
>
> From: Denis Bitouzé <dbito...@wanadoo.fr>
> Subject: Re: Bug: \vert{} exported to markdown not as expected [8.3.1
>   (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]
> To: Nicolas Goaziou <m...@nicolasgoaziou.fr>
> Cc: Denis Bitouzé
>   <public-dbitouze-39zsbgiqgt5gwvitb5q...@plane.gmane.org>,
>   public-emacs-orgmode-mXXj517/z...@plane.gmane.org
> Date: Mon, 14 Sep 2015 08:35:04 +0200 (35 minutes, 18 seconds ago)
>
>
> Le 13/09/15 à 22h47, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit :
>
>> Denis Bitouzé <dbitouze-39zsbgiqgt5gwvitb5q...@public.gmane.org> writes:
>>
>>> 1. For _, \under{} is necessary since _ at the org mode level is
>>>exported as \_.
>>> 2. For |, source | could be okay. But I'd like to use strings as above
>>>in tables and, AFAIK, the only way to have pipe symbols in a table at
>>>the org mode level is to code them \vert{}.  And that's the purpose
>>>of my bug report, \vert{} is exported as , not as "real" |.
>>>
>>> In other words, I was happy with \under{} that exports real _ and,
>>> IMHO, \vert{} should do the same with |.
>>
>> Markdown export back-end use :html conventions to translate entities.
>> For some reason, HTML prefers  over |, and so does markdown.
>
>  and | are displayed the same way but can have different
> "meanings".
>
>> There are a few options available:
>>
>>   1. Prefer | over  in HTML
>
> Maybe I'm wrong but wouldn't this break backward compatibility?
>
>>   2. Overwrite "vert" entity with a new one that would do 1. So
>>  basically, this is 1 but on your machine only.
>
> The feature I'm requesting may be useful to others.
>
>>   3. Use a new entity that becomes | when used in HTML export.
>
> It would be harmless.
>
>> WDYT?
>
> The 3rd option looks the best one to me.
>
> Regards.
-- 
Denis

Re: [O] Please confirm your message

[Denis Bitouzé]

Le 14/09/15 à 09h12, Gmane Remailer 
 a écrit :

> This message was created automatically by mail delivery software (TMDA).
>
> Your message attached below is being held because the address
> <dbito...@wanadoo.fr> has not been verified.
>
> To release your message for delivery, please send an empty message
> to the following address, or use your mailer's "Reply" feature.
>
>
> public-emacs-orgmode-mXXj517/zsq-confirm-1442214744.28220.0d5...@plane.gmane.org
>
> This confirmation verifies that your message is legitimate and not
> junk-mail. You should only have to confirm your address once.
>
> If you do not respond to this confirmation request within 14 days,
> your message will not be delivered.
>
> From: Denis Bitouzé <dbito...@wanadoo.fr>
> Subject: Re: Please confirm your message
> To: Gmane Remailer 
> Cc: 
> public-emacs-orgmode-mXXj517/zsq-confirm-1442212612.9320.da9...@plane.gmane.org
> Date: Mon, 14 Sep 2015 09:10:40 +0200 (1 minute, 2 seconds ago)
>
>
> Le 14/09/15 à 08h36, Gmane Remailer 
>  a écrit :
>
>> This message was created automatically by mail delivery software (TMDA).
>>
>> Your message attached below is being held because the address
>> <dbito...@wanadoo.fr> has not been verified.
>>
>> To release your message for delivery, please send an empty message
>> to the following address, or use your mailer's "Reply" feature.
>>
>>
>> public-emacs-orgmode-mXXj517/zsq-confirm-1442212612.9320.da9...@plane.gmane.org
>>
>> This confirmation verifies that your message is legitimate and not
>> junk-mail. You should only have to confirm your address once.
>>
>> If you do not respond to this confirmation request within 14 days,
>> your message will not be delivered.
>>
>> From: Denis Bitouzé <dbito...@wanadoo.fr>
>> Subject: Re: Bug: \vert{} exported to markdown not as expected [8.3.1
>>  (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]
>> To: Nicolas Goaziou <m...@nicolasgoaziou.fr>
>> Cc: Denis Bitouzé
>>  <public-dbitouze-39zsbgiqgt5gwvitb5q...@plane.gmane.org>,
>>  public-emacs-orgmode-mXXj517/z...@plane.gmane.org
>> Date: Mon, 14 Sep 2015 08:35:04 +0200 (35 minutes, 18 seconds ago)
>>
>>
>> Le 13/09/15 à 22h47, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit :
>>
>>> Denis Bitouzé <dbitouze-39zsbgiqgt5gwvitb5q...@public.gmane.org> writes:
>>>
>>>> 1. For _, \under{} is necessary since _ at the org mode level is
>>>>exported as \_.
>>>> 2. For |, source | could be okay. But I'd like to use strings as above
>>>>in tables and, AFAIK, the only way to have pipe symbols in a table at
>>>>the org mode level is to code them \vert{}.  And that's the purpose
>>>>of my bug report, \vert{} is exported as , not as "real" |.
>>>>
>>>> In other words, I was happy with \under{} that exports real _ and,
>>>> IMHO, \vert{} should do the same with |.
>>>
>>> Markdown export back-end use :html conventions to translate entities.
>>> For some reason, HTML prefers  over |, and so does markdown.
>>
>>  and | are displayed the same way but can have different
>> "meanings".
>>
>>> There are a few options available:
>>>
>>>   1. Prefer | over  in HTML
>>
>> Maybe I'm wrong but wouldn't this break backward compatibility?
>>
>>>   2. Overwrite "vert" entity with a new one that would do 1. So
>>>  basically, this is 1 but on your machine only.
>>
>> The feature I'm requesting may be useful to others.
>>
>>>   3. Use a new entity that becomes | when used in HTML export.
>>
>> It would be harmless.
>>
>>> WDYT?
>>
>> The 3rd option looks the best one to me.
>>
>> Regards.
-- 
Denis

Re: [O] Bug: \vert{} exported to markdown not as expected [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Le 14/09/15 à 02h10, "Charles C. Berry" <ccbe...@ucsd.edu> a écrit :

> On Sun, 13 Sep 2015, Nicolas Goaziou wrote:
>
>>
>>
>> Denis Bitouzé <dbitouze-39zsbgiqgt5gwvitb5q...@public.gmane.org> writes:
>>
> [...]
>
>> Markdown export back-end use :html conventions to translate entities.
>> For some reason, HTML prefers  over |, and so does markdown.
>>
>> There are a few options available:
>>
>>  1. Prefer | over  in HTML
>>  2. Overwrite "vert" entity with a new one that would do 1. So
>> basically, this is 1 but on your machine only.
>>  3. Use a new entity that becomes | when used in HTML export.
>>
>
> If this creates a backend derived from 'md (and does not modify ox-md.el),
> then fine. But, ...
>
> It seem like there are flavors of Markdown that use verticals for varying
> purposes.

Sigh... :)

> For example, rmarkdown
>
>   http://rmarkdown.rstudio.com/authoring_pandoc_markdown.html
>
> uses them as `line block' markers and to construct `table.el' style tables.
>
> And I have seen verticals used to set off citations elsewhere.

Sigh... again :)

> And I am not even sure what Denis meant by using them to `interpret
> strings'.

As said, I'm only a very occasional markdown user, mainly on github and
SE (flavors).

In my current usecase (on a OSQA site), e.g. |REP_GAIN_BY_UPVOTED|
entered as markdown displays the value of REP_GAIN_BY_UPVOTED (some
internal site variable) when rendered as HTML.

Anyway, as pointed out in my answer to Nicolas, it may be useful to
other org mode users to be able to obtain "real" pipe symbol in markdown
export. Hence, a new entity that becomes | when used in md export could
be nice...

Best.
-- 
Denis

Re: [O] Bug: \vert{} exported to markdown not as expected [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Le 13/09/15 à 22h47, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit :

> Denis Bitouzé <dbitouze-39zsbgiqgt5gwvitb5q...@public.gmane.org> writes:
>
>> 1. For _, \under{} is necessary since _ at the org mode level is
>>exported as \_.
>> 2. For |, source | could be okay. But I'd like to use strings as above
>>in tables and, AFAIK, the only way to have pipe symbols in a table at
>>the org mode level is to code them \vert{}.  And that's the purpose
>>of my bug report, \vert{} is exported as , not as "real" |.
>>
>> In other words, I was happy with \under{} that exports real _ and,
>> IMHO, \vert{} should do the same with |.
>
> Markdown export back-end use :html conventions to translate entities.
> For some reason, HTML prefers  over |, and so does markdown.

 and | are displayed the same way but can have different
"meanings".

> There are a few options available:
>
>   1. Prefer | over  in HTML

Maybe I'm wrong but wouldn't this break backward compatibility?

>   2. Overwrite "vert" entity with a new one that would do 1. So
>  basically, this is 1 but on your machine only.

The feature I'm requesting may be useful to others.

>   3. Use a new entity that becomes | when used in HTML export.

It would be harmless.

> WDYT?

The 3rd option looks the best one to me.

Regards.
-- 
Denis

Re: [O] Bug: Extra blank line in subitem list when exported to markdown [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Le 13/09/15 à 22h41, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit :

> Hello,

Hello,

> dbito...@wanadoo.fr (Denis Bitouzé) writes:
>
>> When exported to markdown, an extra blank line is added in subitem
>> lists, as shown by the following minimal example.
>>
>> #+NAME: test.org
>> #+begin_src org
>> - Foo 1
>> - Foo2:
>>   - Foo21
>>   - Foo22
>>   End of Foo2 item.
>> #+end_src
>>
>> *Expected* behavior (note the *absence* of blank line after =Foo22=):
>>
>> #+NAME: test-ok.md
>> #+begin_src markdown
>> -   Foo 1
>> -   Foo2:
>> -   Foo21
>> -   Foo22
>> End of Foo2 item.
>> #+end_src
>>
>> *Current* behavior (note the blank line after =Foo22=):
>>
>> #+NAME: test.md
>> #+begin_src markdown
>> -   Foo 1
>> -   Foo2:
>> -   Foo21
>> -   Foo22
>> 
>> End of Foo2 item.
>> #+end_src
>
> Well, the rules governing blank lines in Mardown are mysterious to me.
> They are also, AFAIK, totally undocumented.

I agree.

> Anyway, you are suggesting to remove any blank line before paragraphs
> following a plain list, but only when they are already contained
> within a list.

Well, please, don't trust me too quickly :) I must admit I'm very far
from a mardown expert: I'm only a very occasional user.

> In other words, both
>
>   - Foo 1
>   - Foo 2
>
>   A paragraph
>
> and
>
>   - Foo 1
>   - Foo 2:
> - Foo 21
> - Foo 22
> End of Foo 2 item.
>
> are valid examples. Am I correct? 

In fact, my suggestion was wrong: AFAICS, the last example doesn't give
the expected HTML result neither and the less bad solution for nested
lists in markdown seems to be:

#+NAME: test.md
#+begin_src markdown
-   Foo 1

-   Foo 2:

-   Foo 21
-   Foo 22

End of Foo 2 item.
#+end_src

which is interpreted as (rather ugly):

#+begin_src html

  
Foo 1:
  
  
Foo 2:

  Foo 21
  Foo 22

End of Foo 2 item.
  

#+end_src

> Also, what about other block types, e.g., which one is valid:
>
>   - Foo 1
>   - Foo 2:
> - Foo 21
> - Foo 22
>
> #+begin_example
> Some example
> #+end_example
>
> or
>
>   - Foo 1
>   - Foo 2:
> - Foo 21
> - Foo 22
> #+begin_example
> Some example
> #+end_example

I'm not sure to understand what you have in mind: are these last two
examples at org mode level?

Regards,
-- 
Denis

Re: [O] Bug: \vert{} exported to markdown not as expected [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Le 13/09/15 à 22h04, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit :

> Hello,

Hello,

> dbito...@wanadoo.fr (Denis Bitouzé) writes:
>
>> The following file:
>>
>> #+NAME: test.org
>> #+begin_src org
>> Foo |bar_baz|
>>
>> Foo \vert{}bar\under{}baz\vert{}
>> #+end_src
>>
>> is exported to markdown as follows:
>>
>> #+NAME: test.md
>> #+begin_src markdown
>> Foo |bar\_baz|
>>
>> Foo bar_baz
>> #+end_src
>>
>> Whereas:
>>
>> - \under{} gives the expected underscore symbol (_),
>> - \vert{} gives  instead of the expected pipe symbol (|).
>
> What is wrong with ? Doesn't Markdown accept HTML entities
> anyway?

The point is the following: the site where the .md file (exported from
the .org file) will be used has this (maybe current) feature to be able
to interpret strings such as:

|REP_TO_COMMENT|

Hence, I have to export "real" _ and |.

1. For _, \under{} is necessary since _ at the org mode level is
   exported as \_.
2. For |, source | could be okay. But I'd like to use strings as above
   in tables and, AFAIK, the only way to have pipe symbols in a table at
   the org mode level is to code them \vert{}.  And that's the purpose
   of my bug report, \vert{} is exported as , not as "real" |.

In other words, I was happy with \under{} that exports real _ and, IMHO,
\vert{} should do the same with |.

Regards.
-- 
Denis

Re: [O] Bug: LaTeX source code blocks not exported in Markdown [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Le 11/09/15 à 17h58, Nicolas Goaziou  a écrit :

> Hello,

Hi Nicolas and Charles,

>> Expected behavior:
>>
>>   ┌
>>   │ #+BEGIN_SRC latex
>>   │ latex
>>   │ #+END_SRC
>>   └
>>
>> gives:
>>
>>   ┌
>>   │ latex
>>   └
>
> This is because latex block can be evaluated, which gives:
>
>   #+RESULTS:
>   #+BEGIN_LaTeX
>   latex
>   #+END_LaTeX
>
> i.e., the generated results appear only when using latex export backend.
> The original block is removed thereafter. You can use instead:
>
>   #+BEGIN_SRC latex :exports code
>   latex
>   #+END_SRC

Ooops, sorry for the noise due to this misuse.

Regards.
-- 
Denis

[O] Bug: \vert{} exported to markdown not as expected [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.


The following file:

#+NAME: test.org
#+begin_src org
Foo |bar_baz|

Foo \vert{}bar\under{}baz\vert{}
#+end_src

is exported to markdown as follows:

#+NAME: test.md
#+begin_src markdown
Foo |bar\_baz|

Foo bar_baz
#+end_src

Whereas:

- \under{} gives the expected underscore symbol (_),
- \vert{} gives  instead of the expected pipe symbol (|).

Emacs  : GNU Emacs 24.5.1 (i686-pc-linux-gnu, GTK+ Version 3.14.8)
 of 2015-06-29 on drums.chezmoi.fr
Package: Org-mode version 8.3.1 (8.3.1-103-g366dc4-elpa @ 
/home/bitouze/.emacs.d/elpa/org-20150907/)

current state:
==
(setq
 org-entities-user '(("nok" "{\\color{red}\\ding{55}}" nil "" "NOK"
  "NOK" "✘")
 ("ok" "{\\color{checkmark}\\ding{51}}" nil ""
  "OK" "OK" "✔")
 )
 org-enforce-todo-checkbox-dependencies t
 org-inlinetask-default-state "TODO"
 org-agenda-search-view-always-boolean t
 org-agenda-log-mode-items '(clock)
 org-latex-format-headline-function 'leuven--org-latex-format-headline
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point 
org-babel-execute-safely-maybe)
 org-pretty-entities t
 org-latex-packages-alist '(("" "listings") ("" "xcolor") ("french" "babel"))
 org-html-format-inlinetask-function 
'org-html-format-inlinetask-default-function
 org-stuck-projects '("+LEVEL=2/-DONE" ("TODO" "STRT") nil "")
 org-refile-use-cache t
 org-clock-in-resume t
 org-clock-out-when-done nil
 org-log-states-order-reversed nil
 org-odt-preferred-output-format "doc"
 org-agenda-sticky t
 org-goto-interface 'outline-path-completion
 outline-minor-mode-hook '(leuven--outline-minor-mode-hook
   (lambda nil
(if (and outline-minor-mode (derived-mode-p (quote
 
emacs-lisp-mode)))
 (progn (hide-sublevels 1000)))
)
   )
 org-agenda-skip-scheduled-if-done t
 org-ellipsis " ►"
 org-clock-persist t
 org-archive-location "::* Archive"
 org-agenda-window-setup 'current-window
 org-adapt-indentation nil
 org-agenda-entry-text-leaders "   │ "
 org-agenda-scheduled-leaders '("Scheduled  " "   ")
 org-clock-mode-line-total 'all
 org-tab-first-hook '(org-hide-block-toggle-maybe
  org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-agenda-exporter-settings '((ps-number-of-columns 1) (ps-landscape-mode t)
(htmlize-output-type (quote css)))
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-refile-targets '((nil :maxlevel . 4) (nil :maxlevel . 2))
 org-html-htmlize-output-type 'css
 org-modules '(org-info org-habit org-gnus org-id org-checklist)
 org-cycle-hook '(org-inlinetask-hide-tasks org-cycle-hide-archived-subtrees
  org-cycle-hide-drawers
  org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change)
 org-html-checkbox-type 'unicode
 org-mime-send-subtree-hook '((lambda nil
   (org-entry-put (point) "mail_composed"
(current-time-string)))
  )
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-confirm-babel-evaluate nil
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-src-window-setup 'current-window
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-export-preprocess-hook '(leuven--org-export-preprocess-hook)
 org-clock-total-time-cell-format "%s"
 org-export-snippet-translation-alist '(("b" . "beamer") ("l" . "latex") ("h" . 
"html"))
 org-agenda-current-time-string "Right now"
 org-blocker-hook '(org-block-todo-from-checkboxes 
org-block-todo-from-children-or-siblings-or-parent)
 org-fontify-done-headline t
 org-agenda-skip-deadline-prewarning-if-scheduled 7
 org-agenda-restore-windows-after-quit t
 org-return-follows-link t
 org-babel-pre-tangle-hook '(save-buffer)
 org-agenda-diary-file "~/org/diary.org"
 org-export-time-stamp-file nil
 org-occur-hook '(org-first-headline-recenter)
 org-emphasis-alist '(("*" bold "" "") ("/" italic "" "")
  ("_" underline "" "")
  ("=" org-verbatim "" "" verbatim)
  ("~" org-code "" "" verbatim))
 org-font-lock-hook '(org-inlinetask-fontify)
 org-agenda-auto-exclude-function 'leuven--org-auto-exclude-function
 org-refile-target-verify-function 'bh/verify-refile-target
 org-speed-commands-user '(("y" org-todo-yesterday "DONE") ("d" 

[O] Bug: Extra blank line in subitem list when exported to markdown [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.


When exported to markdown, an extra blank line is added in subitem
lists, as shown by the following minimal example.

#+NAME: test.org
#+begin_src org
- Foo 1
- Foo2:
  - Foo21
  - Foo22
  End of Foo2 item.
#+end_src

*Expected* behavior (note the *absence* of blank line after =Foo22=):

#+NAME: test-ok.md
#+begin_src markdown
-   Foo 1
-   Foo2:
-   Foo21
-   Foo22
End of Foo2 item.
#+end_src

*Current* behavior (note the blank line after =Foo22=):

#+NAME: test.md
#+begin_src markdown
-   Foo 1
-   Foo2:
-   Foo21
-   Foo22

End of Foo2 item.
#+end_src

This last =.md= code is interpreted by markdown engines as the following
crazy =.html= code:

#+begin_src html

Foo 1


Foo21
Foo22

Foo2:
End of Foo2 item.


#+end_src

Emacs  : GNU Emacs 24.5.1 (i686-pc-linux-gnu, GTK+ Version 3.14.8)
 of 2015-06-29 on drums.chezmoi.fr
Package: Org-mode version 8.3.1 (8.3.1-103-g366dc4-elpa @ 
/home/bitouze/.emacs.d/elpa/org-20150907/)

current state:
==
(setq
 org-entities-user '(("nok" "{\\color{red}\\ding{55}}" nil "" "NOK"
  "NOK" "✘")
 ("ok" "{\\color{checkmark}\\ding{51}}" nil ""
  "OK" "OK" "✔")
 )
 org-enforce-todo-checkbox-dependencies t
 org-inlinetask-default-state "TODO"
 org-agenda-search-view-always-boolean t
 org-agenda-log-mode-items '(clock)
 org-latex-format-headline-function 'leuven--org-latex-format-headline
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point 
org-babel-execute-safely-maybe)
 org-pretty-entities t
 org-latex-packages-alist '(("" "listings") ("" "xcolor") ("french" "babel"))
 org-html-format-inlinetask-function 
'org-html-format-inlinetask-default-function
 org-stuck-projects '("+LEVEL=2/-DONE" ("TODO" "STRT") nil "")
 org-refile-use-cache t
 org-clock-in-resume t
 org-clock-out-when-done nil
 org-log-states-order-reversed nil
 org-odt-preferred-output-format "doc"
 org-agenda-sticky t
 org-goto-interface 'outline-path-completion
 outline-minor-mode-hook '(leuven--outline-minor-mode-hook
   (lambda nil
(if (and outline-minor-mode (derived-mode-p (quote
 
emacs-lisp-mode)))
 (progn (hide-sublevels 1000)))
)
   )
 org-agenda-skip-scheduled-if-done t
 org-ellipsis " ►"
 org-clock-persist t
 org-archive-location "::* Archive"
 org-agenda-window-setup 'current-window
 org-adapt-indentation nil
 org-agenda-entry-text-leaders "   │ "
 org-agenda-scheduled-leaders '("Scheduled  " "   ")
 org-clock-mode-line-total 'all
 org-tab-first-hook '(org-hide-block-toggle-maybe
  org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-agenda-exporter-settings '((ps-number-of-columns 1) (ps-landscape-mode t)
(htmlize-output-type (quote css)))
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-refile-targets '((nil :maxlevel . 4) (nil :maxlevel . 2))
 org-html-htmlize-output-type 'css
 org-modules '(org-info org-habit org-gnus org-id org-checklist)
 org-cycle-hook '(org-inlinetask-hide-tasks org-cycle-hide-archived-subtrees
  org-cycle-hide-drawers
  org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change)
 org-html-checkbox-type 'unicode
 org-mime-send-subtree-hook '((lambda nil
   (org-entry-put (point) "mail_composed"
(current-time-string)))
  )
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-confirm-babel-evaluate nil
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-src-window-setup 'current-window
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-export-preprocess-hook '(leuven--org-export-preprocess-hook)
 org-clock-total-time-cell-format "%s"
 org-export-snippet-translation-alist '(("b" . "beamer") ("l" . "latex") ("h" . 
"html"))
 org-agenda-current-time-string "Right now"
 org-blocker-hook '(org-block-todo-from-checkboxes 
org-block-todo-from-children-or-siblings-or-parent)
 org-fontify-done-headline t
 org-agenda-skip-deadline-prewarning-if-scheduled 7
 org-agenda-restore-windows-after-quit t
 org-return-follows-link t
 org-babel-pre-tangle-hook '(save-buffer)
 org-agenda-diary-file "~/org/diary.org"
 org-export-time-stamp-file nil
 org-occur-hook '(org-first-headline-recenter)
 org-emphasis-alist '(("*" bold "" 

[O] Bug: LaTeX source code blocks not exported in Markdown [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.


When exported to Mardown, the following org mode file:

--8<---cut here---start->8---
* Lisp code
#+begin_src emacs-lisp
(some-code)
#+end_src

* Foo code
#+BEGIN_SRC foo
Foo
#+END_SRC

* \LaTeX code
#+BEGIN_SRC latex
latex
#+END_SRC

(Huh: nothing?)
--8<---cut here---end--->8---

gives:

  ┌
  │ 
  │ [...]
  │ 
  │ 
  │ # Lisp code
  │ 
  │ (some-code)
  │ 
  │ # Foo code
  │ 
  │ Foo
  │ 
  │ # \LaTeX code
  │ 
  │ (Huh: nothing?)
  └

Expected behavior:

  ┌
  │ #+BEGIN_SRC latex
  │ latex
  │ #+END_SRC
  └

gives:

  ┌
  │ latex
  └
  
Emacs  : GNU Emacs 24.5.1 (i686-pc-linux-gnu, GTK+ Version 3.14.8)
 of 2015-06-29 on drums.chezmoi.fr
Package: Org-mode version 8.3.1 (8.3.1-103-g366dc4-elpa @ 
/home/bitouze/.emacs.d/elpa/org-20150907/)

current state:
==
(setq
 org-entities-user '(("nok" "{\\color{red}\\ding{55}}" nil "" "NOK"
  "NOK" "✘")
 ("ok" "{\\color{checkmark}\\ding{51}}" nil ""
  "OK" "OK" "✔")
 )
 org-enforce-todo-checkbox-dependencies t
 org-inlinetask-default-state "TODO"
 org-agenda-search-view-always-boolean t
 org-agenda-log-mode-items '(clock)
 org-latex-format-headline-function 'leuven--org-latex-format-headline
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point 
org-babel-execute-safely-maybe)
 org-pretty-entities t
 org-latex-packages-alist '(("" "listings") ("" "xcolor") ("french" "babel"))
 org-html-format-inlinetask-function 
'org-html-format-inlinetask-default-function
 org-stuck-projects '("+LEVEL=2/-DONE" ("TODO" "STRT") nil "")
 org-refile-use-cache t
 org-clock-in-resume t
 org-clock-out-when-done nil
 org-log-states-order-reversed nil
 org-odt-preferred-output-format "doc"
 org-agenda-sticky t
 org-goto-interface 'outline-path-completion
 outline-minor-mode-hook '(leuven--outline-minor-mode-hook
   (lambda nil
(if (and outline-minor-mode (derived-mode-p (quote
 
emacs-lisp-mode)))
 (progn (hide-sublevels 1000)))
)
   )
 org-agenda-skip-scheduled-if-done t
 org-ellipsis " ►"
 org-clock-persist t
 org-archive-location "::* Archive"
 org-agenda-window-setup 'current-window
 org-adapt-indentation nil
 org-agenda-entry-text-leaders "   │ "
 org-agenda-scheduled-leaders '("Scheduled  " "   ")
 org-clock-mode-line-total 'all
 org-tab-first-hook '(org-hide-block-toggle-maybe
  org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-agenda-exporter-settings '((ps-number-of-columns 1) (ps-landscape-mode t)
(htmlize-output-type (quote css)))
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-refile-targets '((nil :maxlevel . 4) (nil :maxlevel . 2))
 org-html-htmlize-output-type 'css
 org-modules '(org-info org-habit org-gnus org-id org-checklist)
 org-cycle-hook '(org-inlinetask-hide-tasks org-cycle-hide-archived-subtrees
  org-cycle-hide-drawers
  org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change)
 org-html-checkbox-type 'unicode
 org-mime-send-subtree-hook '((lambda nil
   (org-entry-put (point) "mail_composed"
(current-time-string)))
  )
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-confirm-babel-evaluate nil
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-src-window-setup 'current-window
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-export-preprocess-hook '(leuven--org-export-preprocess-hook)
 org-clock-total-time-cell-format "%s"
 org-export-snippet-translation-alist '(("b" . "beamer") ("l" . "latex") ("h" . 
"html"))
 org-agenda-current-time-string "Right now"
 org-blocker-hook '(org-block-todo-from-checkboxes 
org-block-todo-from-children-or-siblings-or-parent)
 org-fontify-done-headline t
 org-agenda-skip-deadline-prewarning-if-scheduled 7
 org-agenda-restore-windows-after-quit t
 org-return-follows-link t
 org-babel-pre-tangle-hook '(save-buffer)
 org-agenda-diary-file "~/org/diary.org"
 org-export-time-stamp-file nil
 org-occur-hook '(org-first-headline-recenter)
 org-emphasis-alist '(("*" bold "" "") ("/" italic "" "")
  ("_" underline "" "")
  ("=" org-verbatim 

Re: [O] Bug: Internal links broken when exporting from org mode to markdown and odt [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Hi,

Le 10/09/15 à 22h06, Nicolas Goaziou  a écrit :

> Thank you for the report.

You're welcome.

> I fixed it in Markdown back-end yesterday.

Many thanks.

> You may want to upgrade Org.

Via ELPA, it will be okay?

> However, I don't see anything wrong with ODT.

I should have been more explicit, sorry: AFAICS, when clicking on the
"another" link, we jump *not* at the second section but at its
corresponding entry in the TOC.

Regards.
-- 
Denis

[O] Bug: Internal links broken when exporting from org mode to markdown and odt [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

[Denis Bitouzé]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.


When exporting from ~org-mode~, the internal links are okay for ~latex~ or
~html~ export but are broken for ~markdown~ (and ~odt~ as well but ).

For instance, the following file:

#+NAME: test.org
#+begin_src org
* One section
See the [[another][another]] section.
* Another section<>
#+end_src

 

leads to the following (excerpt):

1. (okay) ~.tex~ file (see ~\label{orgtarget1}~ and
   ~\hyperref[orgtarget1]{another}~): 

#+NAME: test.tex
#+begin_src latex
\documentclass[11pt]{article}
[...]
\usepackage{hyperref}
[...]
\begin{document}
[...]
\section{One section}
\label{sec:orgheadline1}

See the \hyperref[orgtarget1]{another} section.

\section{Another section\label{orgtarget1}}
\label{sec:orgheadline2}
\end{document}
#+end_src

2. (okay) ~.html~ file (see ~~ and
   ~another~): 

#+NAME: test.html
#+begin_src html

http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml; lang="en" xml:lang="en">
[...]

[...]

1 One section


See the another section.





2 Another section

[...]


#+end_src


3. (*not* okay) ~.md~ file (see ~~ *but the lack* of
   any ~another~): 

#+begin_src markdown
[...]
# One section

See the another section.

# Another section
#+end_src

1. (*not* okay) ~.odt~ file (see ~~ *but the double*
   ~~: one at the TOC
   level and one at the section level): 

#+begin_src xml


[...]


[...]

1. One section

2. Another section



[...]


One section

See the another section.





Another section







#+end_src

Thanks.

Emacs  : GNU Emacs 24.5.1 (i686-pc-linux-gnu, GTK+ Version 3.14.8)
 of 2015-06-29 on drums.chezmoi.fr
Package: Org-mode version 8.3.1 (8.3.1-103-g366dc4-elpa @ 
/home/bitouze/.emacs.d/elpa/org-20150907/)

current state:
==
(setq
 org-entities-user '(("nok" "{\\color{red}\\ding{55}}" nil "" "NOK"
  "NOK" "✘")
 ("ok" "{\\color{checkmark}\\ding{51}}" nil ""
  "OK" "OK" "✔")
 )
 org-enforce-todo-checkbox-dependencies t
 org-inlinetask-default-state "TODO"
 org-agenda-search-view-always-boolean t
 org-agenda-log-mode-items '(clock)
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point 
org-babel-execute-safely-maybe)
 org-pretty-entities t
 org-stuck-projects '("+LEVEL=2/-DONE" ("TODO" "STRT") nil "")
 org-refile-use-cache t
 org-clock-in-resume t
 org-clock-out-when-done nil
 org-log-states-order-reversed nil
 org-agenda-sticky t
 org-goto-interface 'outline-path-completion
 outline-minor-mode-hook '(leuven--outline-minor-mode-hook
   (lambda nil
(if (and outline-minor-mode (derived-mode-p (quote
 
emacs-lisp-mode)))
 (progn (hide-sublevels 1000)))
)
   )
 org-agenda-skip-scheduled-if-done t
 org-ellipsis " ►"
 org-clock-persist t
 org-archive-location "::* Archive"
 org-agenda-window-setup 'current-window
 org-adapt-indentation nil
 org-agenda-entry-text-leaders "   │ "
 org-agenda-scheduled-leaders '("Scheduled  " "   ")
 org-clock-mode-line-total 'all
 org-tab-first-hook '(org-hide-block-toggle-maybe
  org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-agenda-exporter-settings '((ps-number-of-columns 1) (ps-landscape-mode t)
(htmlize-output-type (quote css)))
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-refile-targets '((nil :maxlevel . 4) (nil :maxlevel . 2))
 org-modules '(org-info org-habit org-gnus org-id org-checklist)
 org-cycle-hook '(org-inlinetask-hide-tasks org-cycle-hide-archived-subtrees
  org-cycle-hide-drawers
  org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change)
 org-mime-send-subtree-hook '((lambda nil (org-entry-put (point) "mail_composed"
   (current-time-string)))
  )
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-confirm-babel-evaluate nil
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-src-window-setup 'current-window
 org-export-preprocess-hook '(leuven--org-export-preprocess-hook)
 org-clock-total-time-cell-format "%s"
 org-agenda-current-time-string "Right now"
 org-blocker-hook '(org-block-todo-from-checkboxes 
org-block-todo-from-children-or-siblings-or-parent)
 org-fontify-done-headline t
 org-agenda-skip-deadline-prewarning-if-scheduled 7
 org-agenda-restore-windows-after-quit t