[O] beamer export and links with spaces

Dear All, i'm using org documents export to beamer. Recently I've changed my directory structures for the screenshots such, that they are located under date subdirectories, e.g.: screenshots/22 January 2016/140808_21161vUU.png If I'm going org-type beamer document, I was always using this

Re: [O] Icalendar export and contacts

I noticed one more strange thing: the new exporter fails to resolve links to radio targets (which are slightly pointless but worked before). I'm not sure it needs fixing, just thought I'd let you know. I.e. <<>> <> [[works]] [[fails]] Cheers, Simon On 02/12/2016 12:01 AM, Nicolas

Re: [O] beamer export and links with spaces

On Friday, 12 Feb 2016 at 09:57, David Belohrad wrote: [...] > What is the way to make it working? It seems that includegraphics > generally does not like spaces inside unless one uses e.g. grffile, so > the problem could be resolved just by replacing %20 in the latex > output by an ordinary

Re: [O] Columnview *** is exported as *

> Am 12.02.2016 um 00:46 schrieb Nicolas Goaziou : > > Hello, > > Axel Kielhorn writes: > >> When I overwrite the ITME with a custom text it doesn’t: >> :COLUMNS: %ITEM(Item) %6Zeit{+} %6Effort(Plan){+} %6Kosten{+} %10Fällig >> %Fertig{X/}

Re: [O] Errors get suppressed by org-babel-execute-src-block

Hi Nick, 2016ko otsailak 11an, Nick Dokos-ek idatzi zuen: > > Not sure if there are tests for remote babel execution, AFAIK no. It would be useful to have these. All the machines I use run Linux and are configured very similarly. Many of the problems in remote execution come from

Re: [O] Errors get suppressed by org-babel-execute-src-block

Hi Nicolas, 2016ko otsailak 10an, Nicolas Goaziou-ek idatzi zuen: > > Hello, > > Aaron Ecay writes: > >> I’d like to install the attached patch to master, if there are no >> objections. That should resolve your concern as well as cleaning up the >> dead code. > > No

Re: [O] Orgmode slow on windows on startup [8.3.2 (8.3.2-10-g00dacd-elpa @ c:/Users/Michael/AppData/Roaming/.emacs.d/elpa/org-20151005/)]

Hello Nicolas, i did the update but there is no change to my issue. Actually the archiving / unarchiving is solving the issue. Even the agenda building in the state before and after i do the archive/unarchive once is exremely different. Everything is unusable slow before, but afterwards it

[O] problem with babel and dot

Hello, I have the following emacs lisp code to build up a dot input for a dependency graph: #+begin_src org ,#+name: graph-from-tables ,#+header: :var options="" :var nodes='() graph='() ,#+BEGIN_SRC emacs-lisp (org-babel-execute:dot (concat "digraph {\n"

Re: [O] problem with babel and dot

I've had a suggestion to use ":wrap src dot" for my elisp code, to avoid using internal API calls. This is a good suggestion but I cannot figure out how to actually accomplish what I want. Basically, I want to #+call: a src block which takes my tables as arguments, uses my elisp code to generate

[O] Integrating Skewer with org-babel-js

Hey there, My skewer/org babel searches turned up nothing, so I made a simple hack that redirects JS block evaluation in org mode through skewer when you are connected (otherwise it uses standard org-js behavior). I posted it to the skewer repo, but I have no idea whether it will be integrated,

Re: [O] Errors get suppressed by org-babel-execute-src-block

Aaron Ecay writes: > Hi Nick, > > 2016ko otsailak 11an, Nick Dokos-ek idatzi zuen: >> >> Not sure if there are tests for remote babel execution, > > AFAIK no. It would be useful to have these. All the machines I use run > Linux and are configured very similarly. Many of

Re: [O] ox-tufte-latex

Dear Thomas. > I've cobbled together an exporter for the Tufte LaTeX classes, which I'd > like to contribute to Org mode contrib/. [...] Having started with Org, Latex and Tufte-latex just a very little time ago, I'd really like to thank you for your efforts. :) However, I would appreciate some

Re: [O] ox-tufte-latex

Aloha Eduardo, Eduardo Mercovich writes: > However, I would appreciate some help with little details that I'm not > getting clear, mostly sure because of my ignorance. > > + what is the difference between using the :ignore: tag and add > "COMMENT" as the first characters in the line (the native

[O] Help understanding what's imported from a #+SETUPFILE file

Hi, I have a common setup file for all my org files which configure the way the latex and HTML files are exported. #+SETUPFILE: ~/org/common/config.org One of the snippets in my config.org is # Allow multi-page code listings by wrapping the `minted' environment with `mdframed' environment #

Re: [O] Help understanding what's imported from a #+SETUPFILE file

Actually, I just realized that changing those 2 lines to: #+LaTeX_HEADER: \BeforeBeginEnvironment{minted}{\begin{mdframed}} #+LaTeX_HEADER: \AfterEndEnvironment{minted}{\end{mdframed}} in the SETUPFILE works too. I don't recall the reason why I did not have them as LaTeX_HEADER earlier. But the

Re: [O] Icalendar export and contacts

Hello, Simon Thum writes: > do you refer to master, maint or something else? I'm on 8.3 but am > considering an upgrade. Development version = master. > Also I think org-contacts should declare the link type if it has > support for it (in the vcard export). I'd be happy to

Re: [O] Help understanding what's imported from a #+SETUPFILE file

Hello, Kaushal Modi writes: > Actually, I just realized that changing those 2 lines to: > > #+LaTeX_HEADER: \BeforeBeginEnvironment{minted}{\begin{mdframed}} > #+LaTeX_HEADER: \AfterEndEnvironment{minted}{\end{mdframed}} > > in the SETUPFILE works too. I don't recall the

Re: [O] Icalendar export and contacts

Hello, Simon Thum writes: > I noticed one more strange thing: > > the new exporter fails to resolve links to radio targets (which are > slightly pointless but worked before). I'm not sure it needs fixing, > just thought I'd let you know. > > I.e. <<>> <> > > [[works]] >

Re: [O] Help understanding what's imported from a #+SETUPFILE file

> SETUPFILE exports keywords defined in `org-export-options-alist' and in > back-end specific options (i.e. :options-alist). I tried "C-h v org-export-options-alist" but the result seemed cryptic to me: ((:title "TITLE" nil nil parse) (:date "DATE" nil nil parse) (:author "AUTHOR" nil

Re: [O] Help understanding what's imported from a #+SETUPFILE file

On Friday, 12 Feb 2016 at 15:11, Kaushal Modi wrote: > Actually, I just realized that changing those 2 lines to: > > #+LaTeX_HEADER: \BeforeBeginEnvironment{minted}{\begin{mdframed}} > #+LaTeX_HEADER: \AfterEndEnvironment{minted}{\end{mdframed}} This is indeed the solution. > in the SETUPFILE

Re: [O] Help understanding what's imported from a #+SETUPFILE file

Hello, Kaushal Modi writes: >> SETUPFILE exports keywords defined in `org-export-options-alist' and in >> back-end > specific options (i.e. :options-alist). > > I tried "C-h v org-export-options-alist" but the result seemed cryptic to > me: Quoting its docstring:

Re: [O] Export org file to pdf: unable to resolve link

> On 11-Feb-2016, at 6:36 pm, John Hendy wrote: > > On Thu, Feb 11, 2016 at 4:36 AM, Nicolas Goaziou > wrote: >> Hello, >> >> Sergio Bacelar writes: >> >>> Yes, that will work but I hoped that the file >>> won't need to

[O] bug#22635: 25.1.50; wrong-type-argument when using org-beamer-select-environment

Derek Feichtinger writes: > When executing C-c C-b (org-beamer-select-environment) in an org beamer > using the current emacs head (git hash ae928ae), I reproducibly get > the following > error and backtrace, independent of the org beamer file used: > > ###