[O] Bug: file+olp capture target path relative to default-dir [9.0 (9.0-elpa @ /home/mir/.emacs.d/elpa/org-20161102/)]

2016-11-05 Thread Allen Li

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 mailing list.


The file+olp target for `org-capture-templates', when a relative path is
used, the path is resolved relative to `default-dir’, as opposed to
relative to `org-directory’ like file+headline.

Emacs  : GNU Emacs 25.1.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.20.9)
 of 2016-09-18
Package: Org mode version 9.0 (9.0-elpa @ /home/mir/.emacs.d/elpa/org-20161102/)

current state:
==
(setq
 org-export-babel-evaluate nil
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-speed-command-hook '(org-speed-command-default-hook
  org-babel-speed-command-hook)
 org-clock-history-length 25
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-clock-into-drawer "CLOCK"
 org-log-done 'time
 org-confirm-shell-link-function 'yes-or-no-p
 org-columns-default-format "%60ITEM %TODO %Effort{:} %CLOCKSUM"
 org-clock-idle-time 10
 org-agenda-sticky t
 org-pretty-entities t
 org-agenda-custom-commands '(("d" "Daily agenda"
   ((agenda "" ((org-agenda-span (quote day
(tags "refile"))
   )
  ("n" "Next actions" tags-todo
   "SCHEDULED=\"\"-BLOCKED=t")
  ("o" "Old tasks" tags "CLOSED<=\"<-1m>\""))
 org-use-sub-superscripts '{}
 org-default-notes-file "~/qualia/agenda/refile.org"
 org-capture-templates '(("n" "Note" entry (file "")
  "* %?\n:LOGBOOK:\n- Captured on %U\n:END:")
 ("t" "Task" entry (file "")
  "* TODO %?\n:LOGBOOK:\n- Captured on %U\n:END:")
 ("j" "Journal" entry
  (file+datetree "agenda/journal.org") "" :clock-in t
  :clock-resume t)
 ("a" "Anison" entry
  (file+olp "agenda/collect.org" "Anison" "Fall 2016")
  "* TODO Download %?\n:LOGBOOK:\n- Captured on 
%U\n:END:")
 ("d" "Diary" entry (file+datetree "log/diary.org") "")
 ("f" "Fitness" entry (file+datetree "log/fitness.org")
  "")
 ("h" "Health" entry (file+datetree "log/health.org") 
""))
 org-agenda-include-diary t
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
 org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-global-properties '(("Effort_ALL" .
  "0:10 0:30 1:00 2:00 3:00 4:00 5:00 6:00 7:00")
 )
 org-log-redeadline 'note
 org-mode-hook '(org-clock-load
 #[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook org-show-block-all append
local]
   5]
 #[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook org-babel-show-result-all
append local]
   5]
 org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-refile-targets '((org-agenda-files :maxlevel . 3) (nil :maxlevel . 3))
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-use-speed-commands '(lambda nil
  (and (looking-at org-outline-regexp)
   (looking-back "^**"))
  )
 org-clock-persist 'history
 org-refile-use-outline-path 'file
 org-directory "~/qualia/"
 org-enforce-todo-dependencies t
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-log-refile 'time
 org-agenda-text-search-extra-files '(agenda-archives)
 org-archive-default-command 'org-archive-to-archive-sibling
 org-log-reschedule 'time
 org-refile-allow-creating-parent-nodes 'confirm
 org-todo-keywords '((sequence "TODO(t)" "|" "DONE(d!)" "CANCELED(c@)"))
 org-babel-tangle-lang-exts '(("python" . "py") ("emacs-lisp" . "el")
  ("elisp" . "el"))
 org-confirm-elisp-link-function 'yes-or-no-p
 org-edit-src-content-indentation 0
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-log-into-drawer t
 org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent)
 org-link-parameters '(("id" :follow org-id-open)
   ("rmail" :follow 

[O] Feature wish: macro functionality for literate programming

2016-11-05 Thread Zhaohui Li
I use org-babel with [:noweb] argument for literate programming.
But soon I find the macro functionality is absent in this system.
For example, I have
#+name: example
#+BEGIN_SRC ruby :tangle yes :noweb yes
dir = "~"
Find.find(dir) do |path|
  if <>
puts path
  end
end
#+END_SRC

#+name: path is a file
#+BEGIN_SRC ruby :tangle no :noweb yes
FileTest.file?(path)
#+END_SRC

But with macro functionality, the program can be more flexible:
#+name: example
#+BEGIN_SRC ruby :tangle yes :noweb yes
dir = "~"
Find.find(dir) do |path|
  if <>
puts path
  end
end
#+END_SRC

#+name: is_a_file?
#+BEGIN_SRC ruby :tangle no :noweb yes :noweb-macro file-path
FileTest.file?(file-path)
#+END_SRC

In [is_a_file?] block, I use argument [:noweb-macro] to indicate this block
is a macro with
one argument.
When expanding block [example], <> will be expanded to
[FileTest.file?(path)].
As a result, The src-block [is_a_file?] achieves better abstraction.

I have tried native macro replacement of org({{{is_a_file?(path)}}}), but
it doesn't work well in src-block.

So, is this feature valuable?


Re: [O] html-email in org-mode

2016-11-05 Thread Eric Brown
John Kitchin  writes:

> htmlize-mail.org
>
>
> * Send org files by html email so they look like org files.
>   :PROPERTIES:
>   :MAIL_FMT: html
>   :END:
>
> We might not always want a full export of an org heading to html for sending 
> an email. Eric Brown would like to just send something that looks like what 
> he sees in org-mode. There is another way to get html from emacs: htmlize! 
> Here is an example. Eric: if this is what you mean, see my modified 
> org-mime.el at https://github.com/jkitchin/scimax/blob/master/org-mime.el. 
>
> The command to send a subtree is: elisp:org-mime-subtree-htmlize
>
>
> #+BEGIN_EXAMPLE
> My comment was motivated by other usage where I wish that I could simply
> wrap an entire simple text, whitespace-formatted email message,
> e.g. generated from org export to a plain text buffer, with a Monospace
> directive so that webmail users could appreciate what I see with Sans
> Mono.
> #+END_EXAMPLE
>
> | a | b | c |
> | 4 | 5 | 6 |
>
> An equation 
> \(e^{i\pi} + 1 = 0\)
>
>
> A figure: 
>
> #+name: fig-particle
> #+attr_org: :width 30%
> ./images/Au-icosahedron-3.png
>
>
> A code block:
> #+BEGIN_SRC python :results output org drawer
> for i in range(5):
> print(i)
> #+END_SRC
>
> ** A subtree
>
> An orgmode reference: cite:Dominik201408. A figure reference: 
> ref:fig-particle.


Thanks John. This is very helpful!



Re: [O] Bug: Export error with #+TITLE [9.0 (9.0-elpa @.emacs.d/elpa/org-20161102/)]

2016-11-05 Thread Nicolas Goaziou
Klarre N  writes:

> How do I load those beside what I all ready have in my minimal init
> file?

I do not remember the details, but this error was reported a couple of
times already on this ML. I think a solution involves cleaning any
lingering Org directory in ELPA and install it again. You may want to
search the ML for more details.

> The manual also has this line:
> (add-to-list 'load-path (expand-file-name "/path/to/org-mode/contrib/lisp"
> t))
>
> But I do not have that directory in my elpa directory?

Org provides two packages. "org" and "org-plus-contrib". Only the latter
provides the directory above.

Regards,



Re: [O] latex exporting to different directory with v9.0

2016-11-05 Thread Nicolas Goaziou
Hello,

Alex Fenton  writes:

> One thing that has unfortunately stopped working is my setup for
> exporting to pdf, putting all the intermediary  (.tex, .aux, .bbl,
> etc) and output files in a different directory to the source .org
> files. My setup is basically
>
> project/
> - images/
> - out/
>
> with all the .org files in the project base directory. A simple
> publishing set-up exported .tex to out/ then called org-latex-compile.
>
> With 9.0, org-latex-compile hands off to org-compile-file, in which
> (as documented) "`default-directory' is set to SOURCE directory during
> the whole
> process." This means, however, that all the image and bibliograpy
> links in the .org files are now broken, since they point to
> ./img/foo.png and not ../img/foo.png

Honestly, I'm surprised it worked. I'm also surprised it could be
related to `default-directory' set-up, since links are created during
Org -> LaTeX conversion, whereas `org-compile-file' handles LaTeX ->
PDF. What is that "simple publishing set-up" you are talking about?

Not that there is not something fishy in `org-compile-file' at the
moment (see, e.g.,
), but I cannot
see a way out without breaking some eggs.

Basically, there are three directories to consider: source (".tex")
directory, output (".pdf") directory, and working directory, i.e.,
probably ".org" file directory.

The assumption for `org-compile-file', and before it,
`org-latex-compile', is that source and output directories are the same.
Hence `org-compile-file' returns an error when

  (concat out-dir tex-file.pdf)

cannot be found.

Now, according to `org-latex-pdf-process', some values do not care much
about the working directory, e.g.,

  "pdflatex -interaction nonstopmode -output-directory %o %f"

but others clearly require the working directory to be the output
directory (note the absence of output directory in the command below)

  "texi2dvi -p -b -V %f"

As a consequence, if we do not set `default-directory' to the output
directory, the latter is broken. Note that if we do, "%o" place-holder
becomes useless as it is always "./".

In a nutshell we can either set default-directory to source/output
directory or leave it as-is. In all cases, it seems to break something
anyway.

I'm Cc'ing Joon Ro since he reported a related issue with
`org-compile-file'.

Comments welcome.


Regards,

-- 
Nicolas Goaziou



Re: [O] Bug: Org Capture with Concatenated filenames [9.0 (9.0-elpa @ .emacs.d/elpa/org-20161102/)]

2016-11-05 Thread Klarre N
Wasn't sure what the (sexp) part was, and tried to switch out file+headline
to function (got invalid function), but with the help of the second link I
got it working, thanks!​


Re: [O] Bug: Export error with #+TITLE [9.0 (9.0-elpa @.emacs.d/elpa/org-20161102/)]

2016-11-05 Thread Klarre N
Hi again and thanks for everything you do!

How do I load those beside what I all ready have in my minimal init file?

(package-initialize)
;; add latest org-mode to load path
(add-to-list 'load-path (expand-file-name "/elpa/org-20161102"))
(provide 'init)
;;; init.el ends here

The manual also has this line:
(add-to-list 'load-path (expand-file-name "/path/to/org-mode/contrib/lisp"
t))

But I do not have that directory in my elpa directory?
This error never occurred before during all org updates through the built
in package manager.


Re: [O] Bug: Export error with #+TITLE [9.0 (9.0-elpa @.emacs.d/elpa/org-20161102/)]

2016-11-05 Thread Nicolas Goaziou
Hello,

Klarre N  writes:

> if the document has a "#+TITLE" (maybe other #+COMMANDS also) export (at
> least LaTeX - PDF and HTML) will fail with this error (since 9.0):
>
> Wrong type argument: listp, #("Title" 0 5 (:parent (#0)).

I think you have a mixed installation. You could make sure that all
libraries from Org 9.0 are properly loaded.

Regards,

-- 
Nicolas Goaziou



[O] Bug: Export error with #+TITLE [9.0 (9.0-elpa @.emacs.d/elpa/org-20161102/)]

2016-11-05 Thread Klarre N
Hi,
if the document has a "#+TITLE" (maybe other #+COMMANDS also) export (at
least LaTeX - PDF and HTML) will fail with this error (since 9.0):

Wrong type argument: listp, #("Title" 0 5 (:parent (#0)).

ECM:
#+TITLE: Title
* Export Error


[O] latex exporting to different directory with v9.0

2016-11-05 Thread Alex Fenton
Firstly, congratulations and thanks to all the contributors to the new 
release.


One thing that has unfortunately stopped working is my setup for 
exporting to pdf, putting all the intermediary  (.tex, .aux, .bbl, etc) 
and output files in a different directory to the source .org files. My 
setup is basically


project/
- images/
- out/

with all the .org files in the project base directory. A simple 
publishing set-up exported .tex to out/ then called org-latex-compile.


With 9.0, org-latex-compile hands off to org-compile-file, in which (as 
documented) "`default-directory' is set to SOURCE directory during the whole
process." This means, however, that all the image and bibliograpy links 
in the .org files are now broken, since they point to ./img/foo.png and 
not ../img/foo.png


It is easy enough to continue to compile from the base directory with 
latexmk and --output-directory, but how is it now intended to do this 
within org's export/publishing framework?


symlinks are not an option since I'm sometimes working on Windows.

thanks
alex



Re: [O] ob-sh loaded from org-babel-do-load-languages is bad

2016-11-05 Thread Nicolas Goaziou
Hello,

Steve Downey  writes:

> Moving ob-sh to ob-shell means that
> (org-babel-do-load-languages
> 'org-babel-load-languages
> '( (sh . t)))
> ;; eliding the full list
>
> will end up loading from the ob-sh shipped with emacs. And hilarity ensues.
> Mostly, for me, being unable to eval any src blocks at all.

This is bad, indeed. This was announced in "Incompatible changes"
section from Org 8.2 release notes, though:

  ** Incompatible changes
  *** =ob-sh.el= renamed to =ob-shell=
  This may require two changes in user config.

  1. In =org-babel-do-load-languages=, change =(sh . t)= to =(shell . t)=.
  2. Edit =local.mk= files to change the value of =BTEST_OB_LANGUAGES=
 to remove "sh" and include "shell".

At that time, we could have provided a dummy "ob-sh.el" raising an error
when loaded, but, three years and a major version later, it doesn't make
much sense anymore.


Regards,

-- 
Nicolas Goaziou



[O] multicolumn cells in latex export

2016-11-05 Thread Vikas Rawal
Two years ago, Eric Schulte had shared some most useful code snippets 
(https://lists.gnu.org/archive/html/emacs-orgmode/2014-08/msg00113.html 
). This 
included an export filter (code pasted below) that provided a very useful way 
of introducing multicolumn cells in latex export.

I have been using this since then without any trouble. But today I tried using 
it to centre-align column headings in the top row by using <1colc>. While it 
works for other columns, it does not work on the last column. 

The last column gets exported as 
\multicolumn{1}{c}{Australia (2015)\\
}\hline

rather than as

\multicolumn{1}{c}{Australia (2015)}\\
\hline

Can anyone help debug what is wrong with this code?

Vikas

---

;;; Multi-column Table Cells
;;
;; Export table cells with multiple columns using Latex-like syntax.
;; For example in the following the "<3colc>Backends" cell spans 3
;; columns with it's text centered.
;;
;; |   | <3colc>Backends |   |   |
;; |   |   LaTeX |  HTML |  Text |
;; |---+-+---+---|
;; | extension |.tex | .html | .txt  |
;;
;; The `org-export-multicolumn-filter-latex' function is taken from
;; the following.
;; 
http://thread.gmane.org/gmane.emacs.orgmode/66332/match=latex+table+multicolumn+cell
(defun org-export-multicolumn-filter (row backend info)
  (cond
   ((org-export-derived-backend-p backend 'latex)
(org-export-multicolumn-filter-latex row backend info))
   ((org-export-derived-backend-p backend 'html)
(org-export-multicolumn-filter-html row backend info

(defun org-export-multicolumn-filter-latex (row backend info)
  (while (string-match
  "\\(<\\([0-9]+\\)col\\([lrc]\\)?>[[:blank:]]*\\([^&]+\\)\\)" row)
(let ((columns (string-to-number (match-string 2 row)))
  (start (match-end 0))
  (contents (replace-regexp-in-string
 "" ""
 (replace-regexp-in-string "[[:blank:]]*$" ""
   (match-string 4 row
  (algn (or (match-string 3 row) "l")))
  (setq row (replace-match
 (format "multicolumn{%d}{%s}{%s}" columns algn contents)
 nil nil row 1))
  (while (and (> columns 1) (string-match "&" row start))
(setq row (replace-match "" nil nil row))
(decf columns
  row)

(defun org-export-multicolumn-filter-html (row backend info)
  (while (string-match "class=\".*\" *>\\([0-9]+\\)col\\([lrc]\\)?" row)
(let ((columns (string-to-number (match-string 1 row)))
  (start (match-end 0))
  (algn (case (intern (or (match-string 2 row) "l"))
  (c "center")
  (r "right")
  (l "left"
  (setq row (replace-match
 (format " class=\"%s\" colspan=\"%s\">" algn columns)
 nil nil row))
  (while (and (> columns 1)
  (string-match "" row start))
(setq row (replace-match "" nil nil row))
(decf columns
  row)

(add-to-list 'org-export-filter-table-row-functions
 'org-export-multicolumn-filter)



Re: [O] Bug: :html-head-extra ignored when publishing project [8.2.10 (release_8.2.10 @ /usr/share/emacs/24.5/lisp/org/)]

2016-11-05 Thread Nicolas Goaziou
Hello,

Michel Damiens  writes:

> Emacs  : GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9)
>  of 2016-04-17 on lgw01-04, modified by Debian
> Package: Org-mode version 8.2.10 (release_8.2.10 @
> /usr/share/emacs/24.5/lisp/org/)

Could you use last stable version and try again?

Regards,

-- 
Nicolas Goaziou



Re: [O] Bug: Unable to nest headings within export blocks [9.0 (9.0-elpa @ c:/Data/Documents/emacs.d/elpa/org-20161102/)]

2016-11-05 Thread Nicolas Goaziou
Hello,

Lixin Chin  writes:

> As per the subject, when a heading line is included within a
> `#+BEGIN_EXPORT backend ... #+END_EXPORT' block, it breaks the parsing
> of the block, which is instead split into multiple `paragraph' elements.
>
> See the attached example (test.org), and associate exports (test.tex)
> and (test.html).
>
> Tested with `emacs -Q -l minimal-org.el', with the org package installed
> from http://orgmode.org/elpa/, org-20161102.
>
> * Test heading
>
> #+BEGIN_EXPORT latex
> Text which should appear in \LaTeX{} exports, but not HTML.
> #+END_EXPORT
>
> #+BEGIN_EXPORT html
> * HTML only heading
> Text which should appear in HTML exports, but not \LaTeX{}.
> #+END_EXPORT

You need to escape the pseudo-headline with a comma.

  #+BEGIN_EXPORT html
  ,* HTML only heading
  Text which should appear in HTML exports, but not \LaTeX{}.
  #+END_EXPORT


Regards,

-- 
Nicolas Goaziou



[O] ob-sh loaded from org-babel-do-load-languages is bad

2016-11-05 Thread Steve Downey
Moving ob-sh to ob-shell means that
(org-babel-do-load-languages
'org-babel-load-languages
'( (sh . t)))
;; eliding the full list

will end up loading from the ob-sh shipped with emacs. And hilarity ensues.
Mostly, for me, being unable to eval any src blocks at all.


Re: [O] Bug: Unable to nest headings within export blocks [9.0 (9.0-elpa @ c:/Data/Documents/emacs.d/elpa/org-20161102/)]

2016-11-05 Thread Lixin Chin

This seems to be a symptom of the same issue as
http://lists.gnu.org/archive/html/emacs-orgmode/2016-10/msg00175.html

A workaround is to put the contents of the #+BEGIN_EXPORT ... block into
a separate .org file (include.org), and #+INCLUDE it in the main document

#+INCLUDE: "include.org" export 

where "include.org":
* Heading
other text

On 03/11/2016 11:47 AM, Lixin Chin wrote:

As per the subject, when a heading line is included within a
`#+BEGIN_EXPORT backend ... #+END_EXPORT' block, it breaks the parsing
of the block, which is instead split into multiple `paragraph' elements.

See the attached example (test.org), and associate exports (test.tex)
and (test.html).

Tested with `emacs -Q -l minimal-org.el', with the org package installed
from http://orgmode.org/elpa/, org-20161102.





[O] Bug: Org fontifying bracket links as plain links [8.2.10 (release_8.2.10 @ /home/bhj/external/local/emacs25/share/emacs/25.0.95/lisp/org/)]

2016-11-05 Thread Bao Haojun


When I wrote "[[http://hello]],hello", with a FULLWIDTH COMMA and no
space after it, the whole string is fontified as link, instead of just
the text in the brackets. This is because the org-plain-link-re is used
whereas org-bracket-link-regexp should have matched it, I think.

I understand that in English, there is normally a space after the comma,
thus org-plain-link-re works fine, but as a Chinese user, we don't put
space after a FULLWIDTH COMMA.

Currently I'm working around this with:

(defadvice org-make-link-regexps (after bhj/org-link-tweak activate)
(setq org-plain-link-re org-any-link-re))


Emacs : GNU Emacs 25.0.95.1 (x86_64-pc-linux-gnu, GTK+ Version 3.20.7)
of 2016-08-18
Package: Org-mode version 8.2.10 (release_8.2.10 @ 
/home/bhj/external/local/emacs25/share/emacs/25.0.95/lisp/org/)


current state:
==
(setq
org-tab-first-hook '(org-hide-block-toggle-maybe 
org-src-native-tab-command-maybe

org-babel-hide-result-toggle-maybe org-babel-header-arg-expand)
org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)

org-occur-hook '(org-first-headline-recenter)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-confirm-shell-link-function 'yes-or-no-p
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)

org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-babel-pre-tangle-hook '(save-buffer)
org-mode-hook '(#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook org-show-block-all append local] 5]
#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook org-babel-show-result-all append 
local] 5]

org-babel-result-hide-spec org-babel-hide-all-hashes)
org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point 
org-babel-execute-safely-maybe)

org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
org-cycle-hide-inline-tasks org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-confirm-elisp-link-function 'yes-or-no-p
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
)




[O] Bug: Unable to nest headings within export blocks [9.0 (9.0-elpa @ c:/Data/Documents/emacs.d/elpa/org-20161102/)]

2016-11-05 Thread Lixin Chin

As per the subject, when a heading line is included within a
`#+BEGIN_EXPORT backend ... #+END_EXPORT' block, it breaks the parsing
of the block, which is instead split into multiple `paragraph' elements.

See the attached example (test.org), and associate exports (test.tex)
and (test.html).

Tested with `emacs -Q -l minimal-org.el', with the org package installed
from http://orgmode.org/elpa/, org-20161102.
* Test heading

#+BEGIN_EXPORT latex
Text which should appear in \LaTeX{} exports, but not HTML.
#+END_EXPORT

#+BEGIN_EXPORT html
* HTML only heading
Text which should appear in HTML exports, but not \LaTeX{}.
#+END_EXPORT
% Created 2016-11-03 Thu 11:34
% Intended LaTeX compiler: pdflatex
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{graphicx}
\usepackage{grffile}
\usepackage{longtable}
\usepackage{wrapfig}
\usepackage{rotating}
\usepackage[normalem]{ulem}
\usepackage{amsmath}
\usepackage{textcomp}
\usepackage{amssymb}
\usepackage{capt-of}
\usepackage{hyperref}
\date{\today}
\title{}
\hypersetup{
 pdfauthor={},
 pdftitle={},
 pdfkeywords={},
 pdfsubject={},
 pdfcreator={Emacs 25.1.1 (Org mode 9.0)}, 
 pdflang={English}}
\begin{document}

\tableofcontents

\section{Test heading}
\label{sec:org0b53ca6}

Text which should appear in \LaTeX{} exports, but not HTML.

\#+BEGIN\(_{\text{EXPORT}}\) html
\section{HTML only heading}
\label{sec:org14261e8}
Text which should appear in HTML exports, but not \LaTeX{}.
\#+END\(_{\text{EXPORT}}\)
\end{document}






Table of Contents


1. Test heading
2. HTML only heading




1 Test heading


#+BEGINEXPORT html




2 HTML only heading


Text which should appear in HTML exports, but not \LaTeX{}.
#+ENDEXPORT





Created: 2016-11-03 Thu 11:34
Validate



(setq user-emacs-directory "C:/Data/Documents/emacs.d/")
(package-initialize)
(require 'org)


[O] Bug: :html-head-extra ignored when publishing project [8.2.10 (release_8.2.10 @ /usr/share/emacs/24.5/lisp/org/)]

2016-11-05 Thread Michel Damiens

Hello,

when publishing "org-linux.manthano.fr" project (see below) I get this head in 
exported html which uses only :html-head


index