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

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.

[O] Feature wish: macro functionality for literate programming

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

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

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

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

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

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

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 > >

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

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/)]

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

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

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

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

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

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

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

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

[O] multicolumn cells in latex export

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

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

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

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

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

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

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/)]

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"

[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/)]

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

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

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).

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

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