>
>
> Is POV-Ray out of the question?
>
> - command-line driven
> - outputs many graphic types
> - very programmable
> - can (be programmed to) read and parse intermediary text/data files
> - robust
> - render to animation later with ffmpeg or mencoder
- and can import a variety of existing
Aloha all,
I noticed a redundant list of R device header arguments in ob-R.el. The
attached patch removes the redundant list, along with two setq's that
appeared to be unnecessary.
All the best,
Tom
>From 843e173e1135a15a542afa9795de0cd7ed4672e0 Mon Sep 17 00:00:00 2001
From: Thomas Dye
Date:
On Tue, 2012-06-19 at 12:05 +0900, Torsten Wagner wrote:
> Hi,
>
> its a bit OT (well maybe there is a babel solution ;) )
> I am looking for a way to generate small animations for educational
> purpose. I know many here did/do/plan to do similar things, thus I
> would like to ask here.
>
> Those
Andreas Leha writes:
> Hi all,
>
> I am having troubles in using the header argument :units which is
> implemented for R source blocks. Example:
>
> #+begin_src R :results graphics :file wideplot.png :width 14 :height 7 :units
> "cm"
> plot(1:10, 1:10)
> #+end_src
>
>
> This expands to
>
> :
Hi,
its a bit OT (well maybe there is a babel solution ;) )
I am looking for a way to generate small animations for educational
purpose. I know many here did/do/plan to do similar things, thus I
would like to ask here.
Those animations need to follow some underlying algorithms (I would
need a cor
Hmm, maybe something like this:
$[link "http://mysite.example"; :label "Example" :html-attr "..."
:latex-attr "..."]
Code that adds functionality or safety to this syntax (including all
future code) will also apply to other features than links. For a new
feature, replace the first element with
n 6.33x) (by turning off
the Emacs package manager) fixed the problem, and so did updating to
Version 7.8.11 org-20120618 (from ELPA using the package manager).
Hello Avdi,
I'm glad you like it!
On Fri, Jun 15, 2012 at 8:15 AM, Avdi Grimm wrote:
> I really like this idea!
>
This change may be Herculean--giving links full access to
target attributes--but I certainly hope not.
As I thought about it, it seems like fair amount of abstraction will be
poss
Hello,
On Mon, Jun 18, 2012 at 5:42 PM, Nicolas Goaziou wrote:
> William Crandall writes:
>>> this is (eval-after-load 'org-e-html ...).
>>
>> Could you elaborate, or point me to some docs?
>
> That's on the same basis as above. Evaluating your code once org.el has
> been loaded is too early.
, and so did updating to
Version 7.8.11 org-20120618 (from ELPA using the package manager).
Hello,
William Crandall writes:
> On Mon, Jun 18, 2012 at 5:04 PM, Nicolas Goaziou wrote:
>
>> You need to require `org-e-html' first.
>
> Well, that was easy. It works fine now. Thanks.
>
>>> Same "void-variable" error, and "Renaming: permission denied"
>>> error, with multiple init.elc3996DWC
Hello Nicolas,
On Mon, Jun 18, 2012 at 5:04 PM, Nicolas Goaziou wrote:
> You need to require `org-e-html' first.
Well, that was easy. It works fine now. Thanks.
>> Same "void-variable" error, and "Renaming: permission denied"
>> error, with multiple init.elc3996DWC, etc.
>
> this is (eval-afte
Hello,
William Crandall writes:
> If I add that one line to the end of init.el:
>
> --
> Debugger entered--Lisp error:
>(void-variable org-e-html-special-string-regexps)
> add-to-list(org-e-html-special-string-regexps ("-nd-" . "--"))
>
Hello,
William Crandall writes:
> While testing org-e-html-special-string-regexps,
> I pulled a new emacs. Startup shows a new message:
>
> "Package assoc is obsolete!"
>
> (require 'assoc) is in org-export-generic, line 102.
org-export-generic is unrelated to the new export engine.
Rega
Nicolas,
While testing org-e-html-special-string-regexps,
I pulled a new emacs. Startup shows a new message:
"Package assoc is obsolete!"
(require 'assoc) is in org-export-generic, line 102.
Some discussion here:
http://www.emacswiki.org/emacs-en/assoc-deprecated
Thanks again for great w
Hello Nicolas,
For me, org-e-html-special-string-regexps
does not (yet) play well.
On Sun, Jun 17, 2012 at 4:47 PM,
Nicolas Goaziou wrote:
> William Crandall writes:
>
>> I've not been able to get special-strings working with
>> the new exporter,
>
> I have no problem with
>
> (add-to-list 'o
Nick Dokos
Mon, 18 Jun 2012 16:44:30 -0400
Eythan Weg wrote:
>
> Hi,
>
>
> I expect that applying org-table-export on
>
> | A\vert B | C |
> |1 | 2 |
>
> would result in
>
> A|BC
> 1 2
>
> but instead \vert remains e
Eythan Weg wrote:
>
> Hi,
>
>
> I expect that applying org-table-export on
>
> | A\vert B | C |
> |1 | 2 |
>
> would result in
>
> A|B C
> 1 2
>
> but instead \vert remains embedded in the exported table.
Exporting to what? The new latex exporter does it right, the old on
Hi,
I expect that applying org-table-export on
| A\vert B | C |
|1 | 2 |
would result in
A|B C
1 2
but instead \vert remains embedded in the exported table.
Is this correct?
Thank you.
Eythan
suvayu ali writes:
> Hi Thomas,
>
> On Mon, Jun 18, 2012 at 7:11 PM, Thomas S. Dye wrote:
>> #+CALL: clean-up() :exports none
>>
>> This way, the original code block will be exported and subsequent calls
>> should not be.
>
> I think John's use case requires other code blocks "using" the common
Dear org-mode maintainers,
I have been trying to include links to rmail folders in my .org file,
and found that following those would lead to "Message not found" unless
(1) the link was to the last message in the folder; and (2) I ensured
that Message-ID was not hidden (the latter also was necessa
Hello experts
When exporting from org (v. 7.8.02) to LaTeX, items in the itemize-environment
look like this:
\item Here comes the text \\
\label{subsec-1}
\item ...
I want to get rid of the linebreak (\\) and don't really need the labels.
I have customized the variable org-export-latex-low-leve
Hello,
"Sebastien Vauban"
writes:
> Nicolas Goaziou wrote:
>> "Sebastien Vauban"
>> writes:
>>
>>> It seems we can't put footnotes in the left part of the
>>> description. Is it intended? Could that restriction be removed?
>>
>> That's not really intended, and the fix is easy, but I have a q
John Hendy writes:
> On Mon, Jun 18, 2012 at 12:16 PM, suvayu ali
> wrote:
>> Hi Thomas,
>>
>> On Mon, Jun 18, 2012 at 7:11 PM, Thomas S. Dye wrote:
>>> #+CALL: clean-up() :exports none
>>>
>>> This way, the original code block will be exported and subsequent calls
>>> should not be.
>>
>> I th
> On Mon, Jun 18, 2012 at 6:50 PM, John Hendy wrote:
> > #+name: preamble
> > #+begin_src R :exports none
> > tikzDevice("file-name")
> > #+end_src
>
> Are you trying to use "file-name" as a variable? if so I think the
> source block header should include this: ":var file-name" and the source
> b
On Mon, Jun 18, 2012 at 12:16 PM, suvayu ali
wrote:
> Hi Thomas,
>
> On Mon, Jun 18, 2012 at 7:11 PM, Thomas S. Dye wrote:
>> #+CALL: clean-up() :exports none
>>
>> This way, the original code block will be exported and subsequent calls
>> should not be.
>
> I think John's use case requires other
Hi Thomas,
On Mon, Jun 18, 2012 at 7:11 PM, Thomas S. Dye wrote:
> #+CALL: clean-up() :exports none
>
> This way, the original code block will be exported and subsequent calls
> should not be.
I think John's use case requires other code blocks "using" the common
code block. Can a "CALL" be done
Hi Suvayu,
suvayu ali writes:
> Glad to see another HEP researcher using org-mode. :)
Greetings!
> Sadly my solution is a big bad hack:
>
> #+begin_latex
> \begin{figure}
> \centering
> \begin{tabular}{c}
> \includegraphics[]{plots/file1.eps} \\
> \includegraphics[]{plots
John Hendy writes:
> I recently started a paper using Babel in a more full-functioned way
> to display both R code as well as output. Previously I've just used
> the convenience of headings and src blocks to create R plots and have
> the code stored nicely for future reference. I'm exporting via
Hi John,
My R knowledge is zero, but I'll give it a shot.
On Mon, Jun 18, 2012 at 6:50 PM, John Hendy wrote:
> #+name: preamble
> #+begin_src R :exports none
> tikzDevice("file-name")
> #+end_src
>
Are you trying to use "file-name" as a variable? if so I think the
source block header should inc
On Mon, Jun 18, 2012 at 11:08 AM, suvayu ali
wrote:
> Hi John,
>
> On Mon, Jun 18, 2012 at 4:53 PM, John Hendy wrote:
>> Doing this got me to thinking how it would be
>> quite neat to run code in a block but mark it to be omitted from
>> export for these kind of "setup" lines that are necessary f
Hello,
Nick Dokos writes:
> Pulled and tested: works nicely. Thanks to Suvayu for the idea and to
> Nicolas for the implementation.
>
> IIUC, this is only implemented in the new exporter: the old one remains
> unchanged - yes?
Correct.
Regards,
--
Nicolas Goaziou
Hi John,
On Mon, Jun 18, 2012 at 4:53 PM, John Hendy wrote:
> Doing this got me to thinking how it would be
> quite neat to run code in a block but mark it to be omitted from
> export for these kind of "setup" lines that are necessary for the
> desired graphs but unnecessary for your reader to se
Hello Brett,
Glad to see another HEP researcher using org-mode. :)
On Mon, Jun 18, 2012 at 5:04 PM, Brett Viren wrote:
> I want to put two images in one figure for LaTeX/PDF export but can't
> find a way.
Sadly my solution is a big bad hack:
#+begin_latex
\begin{figure}
\centering
I'm using GNU emacs 23.2+1-7 and org-mode 6.27a-1 on Debian.
I want to put two images in one figure for LaTeX/PDF export but can't
find a way. Googling has not born fruit. I have tried a few naive
things like:
#+caption: Caption.
#+label: fig:figure
[[./img1.pdf]][[./img2.pdf]]
or:
#+caption:
I recently started a paper using Babel in a more full-functioned way
to display both R code as well as output. Previously I've just used
the convenience of headings and src blocks to create R plots and have
the code stored nicely for future reference. I'm exporting via LaTeX
to create something to
Nicolas Goaziou wrote:
> Hello,
>
> suvayu ali writes:
>
> > On Mon, Jun 18, 2012 at 1:40 AM, Nicolas Goaziou
> > wrote:
> >> This is not a bug. LaTeX has its own command to create the table of
> >> contents. There is no simple way to interfere with the process and
> >> remove the tags.
> >
Hi Eric,
On Mon, Jun 18, 2012 at 9:50 AM, Eric S Fraga wrote:
> Avdi Grimm writes:
>
>> On Fri, Jun 15, 2012 at 12:41 PM, suvayu ali
>> wrote:
>>
>>> With this syntax it would be very easy to write both really long (40-50
>>> frames) as well as quick and short presentations.
>>>
>>
>> I've onl
"Sebastien Vauban"
> IIUC, you seem to say it's difficult to use the overlay notation, but
> you can
> use it very easily that way:
> ** Overlay effects \\ Keep the suspense!
>
> *** Time bomb:B_block:
> :PROPERTIES:
> :BEAMER_env: blo
Hi
I would be grateful if someone could help me sort out my confusion
regarding references to headings (sections) in latex export.
I am used to latex section labels and references via reftex, e.g.
,
| \section{This is a test}
| \label{sec:testit}
|
| In Section \ref{sec:testit}
`
To a
Hello Rasmus,
Rasmus wrote:
> - Operating with pauses are overly hard. One can specify overlays in
>properties, but is just not very convenient, as I may have to
>introduce a new number j'natural' in the current org-beamer (IMO).
I certainly will put my grain of salt later on, but
Nicolas Goaziou writes:
> As I announced in another thread, I'm starting a Beamer back-end for
> the new export engine.
This is indeed good news.
Here are some concerns that I would like to address compared to the
current exporter.
- Operating with pauses are overly hard. One can specify ov
Avdi Grimm writes:
> On Fri, Jun 15, 2012 at 12:41 PM, suvayu ali
> wrote:
>
>> With this syntax it would be very easy to write both really long (40-50
>> frames) as well as quick and short presentations.
>>
>
> I've only been using Org and Beamer for a little while, but if I understand
> it co
Sebastien Vauban writes:
> Hello Nicolas,
>
> Nicolas Goaziou wrote:
[...]
>> Note that even if it had one, it wouldn't work as expected since Beamer
>> is not supported yet (but I'll probably implement a first draft for this
>> back-end soon).
>
> I'll be glad to be your first Beamer tester --
Enda writes:
> How do you essentially turn off font-lock except for headings?
By customising the faces used? You can find out what face is active at
any point with C-u C-x =.
--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.1.50.1 and Org release_7.8.11-69-ga2fd96
Hello,
suvayu ali writes:
> On Mon, Jun 18, 2012 at 1:40 AM, Nicolas Goaziou wrote:
>> This is not a bug. LaTeX has its own command to create the table of
>> contents. There is no simple way to interfere with the process and
>> remove the tags.
>
> I think this should work:
>
> \section[Section
Hi Nicolas,
first of all, I think the block idea is a good one, as long a notes will
remain headlines. Nevertheless I often had the problem in my documents,
that I wanted to insert code between frames. It would be great, if you
could provide a clean solution for such things, too. (ignoreheading
Hi Christian,
> On 6/18/12 9:41 AM, Christian Moe wrote:
>> Hi again,
>>
>> I'm sorry, I'm not looking into it as such -- I haven't had time to
>> catch up with the new exporter goodies. I was just wondering if Org or
>> ODT had suddenly developed any built-in bibtex formatting capabilities
>> I w
On 6/18/12 9:41 AM, Christian Moe wrote:
Hi again,
I'm sorry, I'm not looking into it as such -- I haven't had time to
catch up with the new exporter goodies. I was just wondering if Org or
ODT had suddenly developed any built-in bibtex formatting capabilities
I wasn't aware of. :-)
But if you
Hi Nicolas,
> Hello,
>
> Andreas Leha writes:
>
>> is the new exporter lacking the possibility to set the title of the
>> exported document, when the title is set in the properties?
>>
>> Example:
>> ,
>> | #+title: test
>> |
>> | * testexport
>> | :PROPERTIES:
>> | :EXPORT_TITLE: Pumuck
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Juan Pechiar writes:
> On Sun, Jun 17, 2012 at 08:12:19PM -0400, William LÉCHELLE wrote:
>> > org-mode thinks I finished it for 'today' because it's after 0AM and
>> > schedules it for 'tomorrow'. This way, I'll forget it for one day.
>> >
>> > Is
Hi Christian,
thanks for looking into this.
> Could you say what behavior you expect when exporting \cite commands
> to ODT?
I would say:
Minimal expectation: error-free export
Maximal expectation: LaTeX-like reference ;-)
Realistic expectation: literal export (e.g. \cite{xxx}) as in the ascii e
52 matches
Mail list logo
