[O] export: inserting text between source and its results
Hello,
I'm writing a presentation with some source code blocks. At the moment I can
easily evaluate them and have them display in a pretty way (using the :results
code flag). For instance, the following
Evaluating
#+name: with_example
#+begin_src js :results code output :exports both
var x = 1
var f = function(o){ with(o){ return x } }
var o2 = { x : 2 }
var o3 = { x : 3 }
console.log(f({}))
console.log(f(o2))
console.log(f(o3))
#+end_src
gives me something very nice in LaTeX
Evaluating
\begin{minted}[frame=lines,fontsize=\scriptsize]{js}
var x = 1
var f = function(o){ with(o){ return x } }
var o2 = { x : 2 }
var o3 = { x : 3 }
console.log(f({}))
console.log(f(o2))
console.log(f(o3))
\end{minted}
\begin{minted}[frame=lines,fontsize=\scriptsize]{js}
1
2
3
\end{minted}
\end{frame}
Now I would like to insert some text between the source part and the result
part. For this it seems that I need to use a call, but then I can't see how
to get it to display nicely in a minted environment. Here is what I tried:
Evaluating
#+name: with_example
#+begin_src js :results output :exports source
var x = 1
var f = function(o){ with(o){ return x } }
var o2 = { x : 2 }
var o3 = { x : 3 }
console.log(f({}))
console.log(f(o2))
console.log(f(o3))
#+end_src
Results
#+call: with_example() :results code
yields
Evaluating
\begin{minted}[frame=lines,fontsize=\scriptsize]{js}
var x = 1
var f = function(o){ with(o){ return x } }
var o2 = { x : 2 }
var o3 = { x : 3 }
console.log(f({}))
console.log(f(o2))
console.log(f(o3))
\end{minted}
Results
\begin{minted}[frame=lines,fontsize=\scriptsize]{common-lisp}
1\n2\n3\n
\end{minted}
\end{frame}
(It seems the :results code evaluates again the output of the call.)
Any suggestion?
Thanks a lot,
Alan
Re: [O] Variable naming (old vs new exporter)
Hi Nicolas, Nicolas Goaziou wrote: Sebastien Vauban writes: A quick question about the future of the exporters: when the new exporter will be (more) integrated into Org, - will the old ones be removed? Yes. - will the packages be renamed? Yes. - will the variables be renamed (for example, from `org-e-html-preamble-format' to `org-html-preamble-format')? Yes. Thanks for those clarifications! Best regards, Seb -- Sebastien Vauban
Re: [O] export: inserting text between source and its results
Hello Alan, Alan Schmitt wrote: Now I would like to insert some text between the source part and the result part. For this it seems that I need to use a call No, simply use named code blocks, and put #+results: the-name-I-choose wherever you want the results to be located. That way, you can completely separate where the block is, from where the results will be posted to. Best regards, Seb -- Sebastien Vauban
Re: [O] Org variables in LaTeX - how?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/12 16:59, Mikhail Titov wrote:
-Original Message- From: emacs-orgmode-bounces+mlt=gmx...@gnu.org
[mailto:emacs-orgmode- bounces+mlt=gmx...@gnu.org] On Behalf Of Rainer M
Krug Sent: Thursday,
June 07, 2012 6:32 AM To: emacs-orgmode Subject: [O] Org variables in LaTeX
- how?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Hi
I must admit, I don't know the inner workings of LaTeX, so this might be
impossible, but
anyway:
I have the following two variables:
#+PROPERTY: var VER=89 #+PROPERTY: var+ STATE=up-to-date
I create a file in one code block via sh, named
FILE=./../nsa.$VER.$STATE.tar.gz
Now I would likle to attach this file to the pdf:
#+LATEX_HEADER:\\usepackage{attachfile2} #+BEGIN_LaTeX
\textattachfile[print=false,color=0.5
0.5 0.5]{./../nsa.VER.STATE.tar.gz}{R source files} #+END_LaTeX
How can I use the variables in a LaTeX block? Using the ove does obviously
not work, but
#+BEGIN_LaTeX \textattachfile[print=false,color=0.5 0.5
0.5]{./../nsa.98.up-to-
date.tar.gz}{R source files} #+END_LaTeX
does.
So my question: Can I, and if yes how, use org variables in LaTeX code?
You should generate latex code with let's say elisp (or some other language)
fragment that will
output :results latex
Thanks - good idea. Haven't thought about that.
Cheers,
Rainer
Mikhail
- --
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys.
(Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D):+49 - (0)3 21 21 25 22 44
email: rai...@krugs.de
Skype: RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/R6K4ACgkQoYgNqgF2egrDogCfbYpZ04K2mXm9plvizCFgnQUL
7BsAoIKP1KxhsPKWhmOz1gkzInN8Lmo5
=xAhQ
-END PGP SIGNATURE-
Re: [O] org-e-html: Including ATTR_HTML: title=hover text
Hello, William Crandall bc3141...@gmail.com writes: ATTR_HTML is only for paragraphs, not links. This puzzles me, because (1) the old exporter works fine on links that are inside paragraphs, as my example showed, and (2) the Manual says ATTR_HTML lines are for links: That's a major change from previous exporter. Now, almost every element, including paragraphs, can have affiliated keywords at their beginning. Hence you can write: #+attr_latex: something - item 1 - item 2 or #+attr_html: something Some paragraph. This means that One paragraph. #+attr_html: something [[link]] Second paragraph is equivalent to: One paragraph. #+attr_html: something [[link]] Second paragraph Now let's have a look at your example. #+ATTR_HTML: title=The Org mode homepage style=color:red; [[http://orgmode.org]] In this case, the affiliated keyword is attached to the paragraph containing the link. But _the link can inherit from paragraph's attributes_. Since this is not the case yet in, I've added into code base. Is it working as expected? I hope I am clearer now. Regards, -- Nicolas Goaziou
Re: [O] export: inserting text between source and its results
On 8 juin 2012, at 10:57, Sebastien Vauban wrote: Hello Alan, Alan Schmitt wrote: Now I would like to insert some text between the source part and the result part. For this it seems that I need to use a call No, simply use named code blocks, and put #+results: the-name-I-choose wherever you want the results to be located. That way, you can completely separate where the block is, from where the results will be posted to. It worked great, thanks a lot! Alan
Re: [O] Updating orgmode
Hello, I had a similar issue when setting up Org on a Debian system lately. For some reason Emacs was not adding a =subdirs.el= file to =/usr/share/emacs/site-lisp/=. Including the following provided the desired result: ,---(/usr/share/emacs/site-lisp/subdirs.el)--- | ;; -*- no-byte-compile: t -*- | (if (fboundp 'normal-top-level-add-subdirs-to-load-path) | (normal-top-level-add-subdirs-to-load-path)) `- Regards, Jonathan On Thu, Jun 7, 2012 at 9:09 PM, Vikas Rawal vikasli...@agrarianresearch.org wrote: I have a debian system. I am trying to update orgmode using git. But M-x org-version continues to show me version 7.7. How do I find where is it picking up this version from? It seems to me that this is the default version that shipped with my emacs. Debian repository has a more updated version (7.8.09) in its repositories. But I do not see much point in install it. I could compile org correctly. The compiler seems to have installed orgmode in /usr/share/emacs/site-lisp/org. But somehow emacs does not seem to be picking it up from there. Will much appreciate help. Thanks, Vikas
Re: [O] Updating orgmode
Michael Welle mwe012...@gmx.net writes: You might use 'M-x find-library' and at the prompt type 'org.el' to discover which version is loaded by Emacs. Also useful: M-x list-load-path-shadows hth Memnon
Re: [O] [BUG?] Strange effect of noweb name collision on LaTeX export
Ethan Ligon li...@are.berkeley.edu writes: #+TITLE: Example of name collision bug #+AUTHOR: #+EMAIL: #+DATE: 2012-06-07 Thu #+OPTIONS: H:3 num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t :t * Figure and trivial code reference Here we have a figure. This example works as expected; we get a latex figure on export. [[./foo.png]] * Figure and trivial code reference (with collision) Here we have a figure and a trivial code block with a noweb reference. The difference is that the basename of the figure matches the noweb reference. Instead of a figure on latex export, we get a hyperref! [[./bar.png]] #+BEGIN_SRC sh :exports none #bar #+END_SRC Ah, so as it turns out the syntax for the noweb reference happens to be the same as the syntax used to specify a latex label. In this case the LaTeX exporter first mistakes the bar as a label anchor, and then apparently converts the bar.png link to a real link. The latex exporter probably shouldn't try to make anchors out of the text within code blocks. However, in the mean time you can customize the noweb syntax using the `org-babel-noweb-wrap-start' and `org-babel-noweb-wrap-end' variables so that they aren't mistaken for label anchors. Best, -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] [BUG?] Strange effect of noweb name collision on LaTeX export
On Fri, Jun 8, 2012 at 8:13 AM, Eric Schulte eric.schu...@gmx.com wrote:
Ethan Ligon li...@are.berkeley.edu writes:
#+TITLE: Example of name collision bug
#+AUTHOR:
#+EMAIL:
#+DATE: 2012-06-07 Thu
#+OPTIONS: H:3 num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t :t
* Figure and trivial code reference
Here we have a figure.
This example works as expected; we get a latex figure on export.
[[./foo.png]]
* Figure and trivial code reference (with collision)
Here we have a figure and a trivial code block with a noweb reference.
The difference is that the basename of the figure matches the noweb
reference. Instead of a figure on latex export, we get a hyperref!
[[./bar.png]]
#+BEGIN_SRC sh :exports none
#bar
#+END_SRC
Ah, so as it turns out the syntax for the noweb reference happens to be
the same as the syntax used to specify a latex label. In this case the
LaTeX exporter first mistakes the bar as a label anchor, and then
apparently converts the bar.png link to a real link.
The latex exporter probably shouldn't try to make anchors out of the
text within code blocks. However, in the mean time you can customize
the noweb syntax using the `org-babel-noweb-wrap-start' and
`org-babel-noweb-wrap-end' variables so that they aren't mistaken for
label anchors.
This diagnosis seems exactly right (and thanks for the work-around).
The problem is even worse than I indicated earlier, though---things
like
./foo-bar.png
or
./foo_bar.png
are incorrectly turned into a link if there's any source block along
the lines of
#+begin_src sh
foo
#+end_src
or
#+begin_src sh
bar
#+end_src
Note also that this is not just an ambiguity about whether
./foo-bar.png should be treated as a link or a figure, because if it's
a link it's a /broken/ link (in the example above the resulting LaTeX
is \hyperref[.-foo-bar.png]{./foo-bar.png})
-Ethan
--
Ethan Ligon, Associate Professor
Agricultural Resource Economics
University of California, Berkeley
[O] Bug: Line breaks in exported LaTeX code [7.8.11]
Greetings Orgs
When exporting an .org file to LaTeX, no line breaks are inserted into
the LaTeX source code. With default options from a fresh install, the
LaTeX code will not compile, because documentclass information appears
on the first line of the LaTeX source, which is a comment:
% Created 2012-06-08 Fri 12:58 \documentclass{article} [...]
As an experiment, I changed the the time stamp in org-latex.el from
(format-time-string %% Created %Y-%m-%d %a %H:%M\n))
to
(format-time-string %% Created %Y-%m-%d %a %H:%M\r))
and it appears that pdflatex recognizes this \r as a line break and hence
compiles. So the problem seems to be the way the \n is written (or not
written) to the LaTeX source file. Which is beyond me.
Test file:
--- file: test.org
#+TITLE:Test
Test
--- end file --
System and version information:
===
Ubuntu 12.04
Emacs : GNU Emacs 23.3.1 (i686-pc-linux-gnu, GTK+ Version 2.24.10)
of 2012-03-25 on roseapple, modified by Debian
Package: Org-mode version 7.8.11
current state:
==
(setq
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-babel-load-languages '((R . t) (latex . t) (ditaa . t))
org-metaup-hook '(org-babel-load-in-session-maybe)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-babel-tangle-lang-exts '((latex . tex) (emacs-lisp . el))
org-export-latex-format-toc-function 'org-export-latex-format-toc-default
org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
org-babel-hide-result-toggle-maybe)
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-confirm-shell-link-function 'yes-or-no-p
org-export-first-hook '(org-beamer-initialize-open-trackers)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-babel-pre-tangle-hook '(save-buffer)
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-export-preprocess-before-normalizing-links-hook
'(org-remove-file-link-modifiers)
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-confirm-elisp-link-function 'yes-or-no-p
org-export-interblocks '((src org-babel-exp-non-block-elements))
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-occur-hook '(org-first-headline-recenter)
org-from-is-user-regexp \\Uffe Høgsbro Thygesen\\
org-export-preprocess-before-selecting-backend-code-hook
'(org-beamer-select-beamer-code)
org-confirm-babel-evaluate nil
org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc
org-beamer-auto-fragile-frames
org-beamer-place-default-actions-for-lists)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-export-blocks '((src org-babel-exp-src-block nil)
(export-comment org-export-blocks-format-comment t)
(ditaa org-export-blocks-format-ditaa nil)
(dot org-export-blocks-format-dot nil))
)
[O] Error while editing sh source code.
I want to write some shell script in my org file, so I add these line in it. #+name: random line #+begin_src sh cat filename.txt | sort --random-sort | sed -e '1!d' #+end_src But when I put cursor in src block and press `C-c '`, emacs show that error: byte-code: Language mode `sh-mode' fails with: Invalid file-name The other modes (at least python, sql) is run without problem. Can anybody show me how to fix this? My emacs version: 23.4.1 My org-mode version: 7.8.11 And this is my config: https://github.com/favadi/dotemacs -- PHẠM Văn Điệp h : http://favadi.com e : i...@favadi.com m : +84 984 339 841 _ ASCII ribbon campaign ( ) - against HTML email X vCards / \
Re: [O] Variable naming (old vs new exporter)
Hello, Samuel Wales samolog...@gmail.com writes: On 6/7/12, Nicolas Goaziou n.goaz...@gmail.com wrote: No. When they are ready, they will completely replace old exporters. Only old exporters with no equivalent back-end for new export engine will be preserved. Here is my earlier question on this topic and Bastien's answer. I recognize that as backward compatible as possible is open to interpretation, but I find your answer to be possibly requiring me to stop upgrading Org. === While the new exporter has advantages, I hope the old exporter will still be available for a long time. I will need it for various purposes, including speed -- I use it for an exact word counter that works flawlessly -- and some design differences from the new exporter. (Also the new exporter does not currently work on 22.) Good to know. We will try to keep things as backward compatible as possible. There is no plan to destroy existing code anyway. You may want to send your word count function so we can see how you can integrate it in the new exporter engine. About Emacs 22, I cannot help much as I have uninstalled it years ago. Since there is no exotic code in org-export.el, solving the problem could be as simple as adding a defalias in org-compat.el. But you'll have to debug it yourself. Regards, -- Nicolas Goaziou
Re: [O] org-e-html: Including ATTR_HTML: title=hover text
Hello Nicolas, Yes, thanks for explanation and code update. It works as you describe, as you can see below. This is a change; now all links within a paragraph are given (inherit) the same ATTR_HTML. Is it possible with the new exporter to add ATTR_HTML attributes to individual link elements? Thanks again for all your work on this! -BC Org-mode: 7.8.11 (release_7.8.11-55-g3f0f87) Emacs: 24.1.50.1 Windows 7 Org input: -- #+ATTR_HTML: title=The Org mode homepage style=color:red; [[http://orgmode.org]] #+ATTR_HTML: title=Link hover text [[http://www.orgmode.org][This paragraph]] describes how to use orgmode. A paragraph about #+ATTR_HTML: title=Link hover text [[./orgmode][org-mode]] which describes org-e-html... #+ATTR_HTML: title=Link hover text Another paragraph about [[./orgmode][org-mode]] which describes org-e-html... -- Old: -- p a href=http://orgmode.org; title=The Org mode homepage style=color:red;http://orgmode.org/a /p p a href=http://www.orgmode.org; title=Link hover textThis paragraph/a describes how to use orgmode. /p p A paragraph about a href=./orgmode title=Link hover textorg-mode/a which describes org-e-htmlhellip; /p p Another paragraph about a href=./orgmodeorg-mode/a which describes org-e-htmlhellip; /p -- New: -- p a href=http://orgmode.org; title=The Org mode homepage style=color:red;http://orgmode.org/a /p p a href=http://www.orgmode.org; title=Link hover textThis paragraph/a describes how to use orgmode. /p p A paragraph about /p p a href=./orgmode title=Link hover textorg-mode/a which describes org-e-htmlhellip; /p p Another paragraph about a href=./orgmode title=Link hover textorg-mode/a which describes org-e-htmlhellip; -- On Fri, Jun 8, 2012 at 6:28 AM, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, William Crandall bc3141...@gmail.com writes: ATTR_HTML is only for paragraphs, not links. This puzzles me, because (1) the old exporter works fine on links that are inside paragraphs, as my example showed, and (2) the Manual says ATTR_HTML lines are for links: That's a major change from previous exporter. Now, almost every element, including paragraphs, can have affiliated keywords at their beginning. Hence you can write: #+attr_latex: something - item 1 - item 2 or #+attr_html: something Some paragraph. This means that One paragraph. #+attr_html: something [[link]] Second paragraph is equivalent to: One paragraph. #+attr_html: something [[link]] Second paragraph Now let's have a look at your example. #+ATTR_HTML: title=The Org mode homepage style=color:red; [[http://orgmode.org]] In this case, the affiliated keyword is attached to the paragraph containing the link. But _the link can inherit from paragraph's attributes_. Since this is not the case yet in, I've added into code base. Is it working as expected? I hope I am clearer now. Regards, -- Nicolas Goaziou
[O] continuing org-clock after accidental emacs-kill
I was clocked-in and I absentmindedly quit out of emacs without doing a clock-out. How do I get the clock working and picking up from where it left off ? Or have I lost what I had for today ? -- Mehul N. Sanghvi email: mehul.sang...@gmail.com
Re: [O] Error while editing sh source code.
Diep Pham Van i...@favadi.com writes: I want to write some shell script in my org file, so I add these line in it. #+name: random line #+begin_src sh cat filename.txt | sort --random-sort | sed -e '1!d' #+end_src But when I put cursor in src block and press `C-c '`, emacs show that error: byte-code: Language mode `sh-mode' fails with: Invalid file-name The other modes (at least python, sql) is run without problem. Can anybody show me how to fix this? My emacs version: 23.4.1 My org-mode version: 7.8.11 And this is my config: https://github.com/favadi/dotemacs I am able to edit the above with C-' and run it successfully. However you should note that spaces are not allowed in code block names, so when I run this code block my results are simply named random. Please try the above with emacs started with the -Q option to see if the problem lies somewhere in your personal configuration. Thanks, -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] continuing org-clock after accidental emacs-kill
Mehul Sanghvi mehul.sang...@gmail.com writes: I was clocked-in and I absentmindedly quit out of emacs without doing a clock-out. How do I get the clock working and picking up from where it left off ? Or have I lost what I had for today ? Type M-x org-resolve-clocks. John
Re: [O] continuing org-clock after accidental emacs-kill
Hi, John Wiegley wrote: Mehul Sanghvi mehul.sang...@gmail.com writes: I was clocked-in and I absentmindedly quit out of emacs without doing a clock-out. How do I get the clock working and picking up from where it left off ? Or have I lost what I had for today ? Type M-x org-resolve-clocks. And for preventive action, I've this (very similar to what existed in John's Planner): #+begin_src emacs-lisp ;; ask the user if they wish to clock out before killing Emacs (defun my/org-clock-query-out () Ask the user before clocking out. This is a useful function for adding to `kill-emacs-query-functions'. (if (and (featurep 'org-clock) (funcall 'org-clocking-p) (y-or-n-p You are currently clocking time, clock out? )) (org-clock-out) t)) ;; only fails on keyboard quit or error ;; timeclock.el puts this on the wrong hook! (add-hook 'kill-emacs-query-functions 'my/org-clock-query-out) #+end_src Best regards, Seb -- Sebastien Vauban
Re: [O] continuing org-clock after accidental emacs-kill
Mehul Sanghvi mehul.sang...@gmail.com writes: I was clocked-in and I absentmindedly quit out of emacs without doing a clock-out. How do I get the clock working and picking up from where it left off ? Or have I lost what I had for today ? I have the following settings in my .emacs --8---cut here---start-8--- ;; ;; Resume clocking tasks when emacs is restarted (org-clock-persistence-insinuate) ;; Do not prompt to resume an active clock (setq org-clock-persist-query-resume nil) ;; Save the running clock and all clock history when exiting Emacs, load it on startup (setq org-clock-persist t) --8---cut here---end---8--- so simply going to the agenda (C-c a a) resumes whatever was running after I restart emacs. HTH, Bernt
[O] Using: org-e-html-special-string-regexps
Hello Jambunathan, I tried your suggestion of swapping -org-e-html-special-string-regexps- for -org-export-html-special-string-regexps- to add my own strings. I want this for an mdash; between words /without/ any spaces; the \mdash entity requires spaces. Results: The old exporter works as expected (below). The new exporter leads to an error mode I've not seen. With a new org-e-html-special-string-regexps code block in init.el (below), emacs reports: -- Wrote g:/dev/bin/emacs/.emacs.d/init.el Compiling g:/dev/bin/emacs/.emacs.d/init.el...done byte-compile-file: Renaming: permission denied, g:/dev/bin/emacs/.emacs.d/init.elc4856ijc, g:/dev/bin/emacs/.emacs.d/init.elc -- Each attempted compile generates a new init.elcX. I've never seen this before. Is it a known error? Attempts to use org-e-html-special-string-regexps naturally fail (see bottom). Any suggestions? Thanks again, for this, and for the /a tags on targets! -BC Org-mode: 7.8.11 (release_7.8.11-55-g3f0f87) Emacs: 24.1.50.1 Windows 7 -- -- org input: -- Testing: w/ spaces mdash \mdash yes, with spaces Testing: no-spaces mdash\mdashyes, without spaces Testing: my-string mdash-MDASH-yes, without spaces -- Old output: -- p Testing: w/ spaces mdash mdash; yes, with spaces Testing: no-spaces mdash\mdashyes, without spaces Testing: my-string mdashmdash;yes, without spaces /p -- Code in init.el: -- ;; For old exporter // WORKS (eval-after-load org '(setq org-export-html-special-string-regexps (append org-export-html-special-string-regexps '((-MDASH- . mdash;) ;; For new exporter // ERROR (eval-after-load org '(setq org-e-html-special-string-regexps (append org-e-html-special-string-regexps '((-MDASH- . mdash;) -- Debugger: -- Debugger entered--Lisp error: (void-variable org-e-html-special-string-regexps) (append org-e-html-special-string-regexps (quote ((-MDASH- . mdash; (setq org-e-html-special-string-regexps (append org-e-html-special-string-regexps (quote ((-MDASH- . mdash;) [...] --[end]---
Re: [O] org-e-html: Including ATTR_HTML: title=hover text
Hello, William Crandall bc3141...@gmail.com writes: This is a change; now all links within a paragraph are given (inherit) the same ATTR_HTML. Indeed. Is it possible with the new exporter to add ATTR_HTML attributes to individual link elements? No, it isn't possible to control individual link elements with affiliated keywords. Regards, -- Nicolas Goaziou
Re: [O] Using: org-e-html-special-string-regexps
Hello,
William Crandall bc3141...@gmail.com writes:
I want this for an mdash; between words /without/
any spaces; the \mdash entity requires spaces.
You may use \mdash{} like in:
a\mdash{}b
Regards,
--
Nicolas Goaziou
Re: [O] Using: org-e-html-special-string-regexps
So you can!
Splendid.
Thanks,
-BC
On Fri, Jun 8, 2012 at 3:38 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
William Crandall bc3141...@gmail.com writes:
I want this for an mdash; between words /without/
any spaces; the \mdash entity requires spaces.
You may use \mdash{} like in:
a\mdash{}b
Regards,
--
Nicolas Goaziou
Re: [O] org-e-html: Including ATTR_HTML: title=hover text
Ah, that is a pity. Seems like a step back, in allowable specificity. As it was possible in the old. You mentioned before using filters. I take it these are the ones described in org-export-filters.el (line 1775), The Filter System. Has anyone written up any worked examples of these? And, is that the best tool for adding attributes to links? Thanks again, -BC On Fri, Jun 8, 2012 at 3:37 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, William Crandall bc3141...@gmail.com writes: This is a change; now all links within a paragraph are given (inherit) the same ATTR_HTML. Indeed. Is it possible with the new exporter to add ATTR_HTML attributes to individual link elements? No, it isn't possible to control individual link elements with affiliated keywords. Regards, -- Nicolas Goaziou
