This seems to work from my brief testing:
#+AUTHOR:
#+OPTIONS: toc:nil
#+PROPERTY: header-args:emacs-lisp :var tar-file="bar.tar.gz" :exports none
#+NAME: tar-eg
#+BEGIN_SRC emacs-lisp
(let ((contents (format "> tar xzvf %s" tar-file)))
(with-temp-buffer
(insert contents)
(write
This is turning out to be more complicated than I anticipated ..
I need to
(1) Export the evaluated emacs-lisp block to a separate file, and
(2) also include the result in the same document
I can do that but it is a multi-step process:
(1) First I need to export the result to the file only. I ca
Kaushal Modi writes:
> OK, now I have just one follow up question. I would like to tangle the result
> to a separate file.
>
> So I am looking for a way to save the result "> tar xvzf bar.tar.gz" to a
> separate file. I tried adding
> ":tangle filename" to #+CALL/#+BEGIN_SRC but that did not he
I finally have this working!
#+PROPERTY: header-args:emacs-lisp :var tar-file="bar.tar.gz" :exports none
:file "results.txt"
#+NAME: tar-eg
#+BEGIN_SRC emacs-lisp
(format "> tar xzvf %s" tar-file)
#+END_SRC
#+CALL: tar-eg() :wrap example :exports none
#+CAPTION: =results.txt=
#+NAME: code__resu
Aloha Kaushal,
Kaushal Modi writes:
> OK, now I have just one follow up question. I would like to tangle the
> result to a separate file.
>
> So I am looking for a way to save the result "> tar xvzf bar.tar.gz" to a
> separate file. I tried adding ":tangle filename" to #+CALL/#+BEGIN_SRC but
> th
OK, now I have just one follow up question. I would like to tangle the
result to a separate file.
So I am looking for a way to save the result "> tar xvzf bar.tar.gz" to a
separate file. I tried adding ":tangle filename" to #+CALL/#+BEGIN_SRC but
that did not help. Adding to #+CALL does not do any
That works perfectly! Thank you!
Just to add that I had to have "#+HEADER: :exports none" as I did not want
the elisp code to be visible in the exported documents.
#+PROPERTY: header-args:emacs-lisp :var tar-file="bar.tar.gz"
#+NAME: tar-eg
#+HEADER: :exports none
#+BEGIN_SRC emacs-lisp
(format
Aloha Kaushal,
Kaushal Modi writes:
> Thanks Tom.
>
> Your solution almost gets me there but I still need to manually update the
> tar-file argument value in the #+CALL lines.
>
> What I am looking for is for something like below to work (but it isn't). I
> have multiple such #+CALL lines and I w
Thanks Tom.
Your solution almost gets me there but I still need to manually update the
tar-file argument value in the #+CALL lines.
What I am looking for is for something like below to work (but it isn't). I
have multiple such #+CALL lines and I would like to not manually update the
tar-file arg
Erik Hetzner writes:
> Thanks for bearing with me on getting git-annex to work properly. This fixes
> an
> issue with running tests on debian with older versions of git-annex.
Pushed to master.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for
Aloha Kaushal,
Kaushal Modi writes:
> Hi all,
>
> I'd like to have an EXAMPLE block in my org file whose value is set using
> something like an org macro at the time of export.
>
> So, something like:
>
> #+MACRO TAR_FILE some_file.tar.gz
>
> #+BEGIN_EXAMPLE
>> tar xvzf {{{TAR_FILE}}}
> #+END_EXA
On Tuesday, 16 Feb 2016 at 17:58, Nicolas Goaziou wrote:
[...]
> I think #+ATTR_BACKEND: :align ... goes a long way towards removing
> these limitations, at least on the export side.
I agree.
I have always taken the view that the syntax was for presentation in
org mode, not for export, probabl
On Tuesday, 16 Feb 2016 at 17:44, Nicolas Goaziou wrote:
> Hello,
>
> Samuel Loury writes:
>
>> Nevertheless, org-mode is rather slow when my todo.org file becomes
>> quite large (~20K lines).
>
> Could you share some profiler information under typical usage so that we
> can tell which parts are s
I've got this code:
#+begin_src latex :packages '(("" "tikz")) :exports results :results output
raw :file fsa.png
\usetikzlibrary{backgrounds}
\begin{tikzpicture}
\draw (0,0) grid (10,5);
\draw (0,0) node[below left] {$A$};
\draw (10,5) node[above right] {$B$};
\fill (0,0) circle (2pt);
Hi all,
I'd like to have an EXAMPLE block in my org file whose value is set using
something like an org macro at the time of export.
So, something like:
#+MACRO TAR_FILE some_file.tar.gz
#+BEGIN_EXAMPLE
> tar xvzf {{{TAR_FILE}}}
#+END_EXAMPLE
As the above is not possible, what would be a good
ref:fig2,fig3 will export to \ref{fig2,fig3} just fine. The only missing
functionality is the tooltip/clickability like on a cite link. Could you
add it as an enhancement issue here
https://github.com/jkitchin/org-ref/issues/new?
It should not be too hard to do it, but it will take some time and t
On Tue, 16 Feb 2016, Alan Schmitt wrote:
On 2016-02-16 12:42, John Kitchin writes:
I think you are seeing that the blocks are tangled in reverse. If I add a third
arbitrary lang it comes in reverse.
Interesting! Thanks a lot for trying it.
I see that I made the typical scientific method mi
Hello,
Derek Feichtinger writes:
> When I use this formula
>
> #+TBLFM: $1= @-1 + 1:: @2$1=1
>
> Then org will first fill this part of the table (starting at cell 2$1)
>
> | N | |
> |---+---|
> | | |
> | 1 | |
> | 2 | |
> | 3 | |
> #+TBLFM: $1= -1 + 1:: 2$1=1
>
> Then i
Hello,
Samuel Loury writes:
> Nevertheless, org-mode is rather slow when my todo.org file becomes
> quite large (~20K lines).
Could you share some profiler information under typical usage so that we
can tell which parts are slow?
Regards,
--
Nicolas Goaziou
Hello,
Michael Giepen writes:
> However, with wider tables you have to put a lot of attributes and the
> following implementation would be clearer if it would be more org-mode
> like with the attributes inside the table.
>
> #+CAPTION: My caption
> #+ATTR_LATEX: :align lS
> | Column |Value
Thanks everyone for replying!
I made one mistake before posting that question: I should have looked up
C-h f org-table-recalculate. And now I did :)
I should have done "C-u C-c * " when the point was in the table (I was
doing just C-c *, which evaluates only the current row).
>> Derek
> | N | |
On Tuesday, 16 Feb 2016 at 15:14, Samuel Loury wrote:
[...]
> I still like a lot the liberty of the "plain text approach" of
> org-mode. It is VERY powerful, but it becomes a real problem when
> needing to use that power without emacs.
Yes, org works well because of the plain-text approach but o
\ref{fig2,fig3} not legal unless you use crever-ref package
On Feb 16, 2016, at 10:48 AM, John Kitchin
mailto:jkitc...@andrew.cmu.edu>> wrote:
Is \ref{fig2,fig3} legal LaTeX?
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Ca
Thanks
On Feb 16, 2016, at 10:48 AM, John Kitchin
mailto:jkitc...@andrew.cmu.edu>> wrote:
Is \ref{fig2,fig3} legal LaTeX?
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268
Is \ref{fig2,fig3} legal LaTeX?
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Tue, Feb 16, 2016 at 8:52 AM, Doyl
On 2016-02-16 12:42, John Kitchin writes:
> I think you are seeing that the blocks are tangled in reverse. If I add a
> third
> arbitrary lang it comes in reverse.
Interesting! Thanks a lot for trying it.
I see that I made the typical scientific method mistake of testing for
my hypothesis, ins
luke call writes:
> On 02/02/16 00:23, Robert Klein wrote:
[...]
>> As your 'product' is
>> not relevant to org-mode []
>
> I mentioned OM here only because I thought it of interest to
> org-mode users, which it evidently was to at least two who thanked me,
> and I answered their questions,
Ever since updating my org+contrib to '20160215' all my carefully crafted
keyword faces for TODO's, NEXT, PHONE, etc have transmogrified to a pale
and wasted facsimile of themselves. Now, TODO is just a red text surrounded
by a red border, and done is just a green text surrounded by a green
border.
writes:
> I've had very good luck using adjustbox for diagrams in ox-beamer
> generated presentations. I've had much less luck using the standard
> output (resizebox). I'm wondering if people might consider switching
> over to adjustbox rather than resizebox for graphical inclusion?
>
> The main
I think you are seeing that the blocks are tangled in reverse. If I add a
third arbitrary lang it comes in reverse.
If they are all the same language, they are in the right order. It looks
like org collects by language, so your strategy won't work with org-babel
tangle I guess.
On Tue, Feb 16, 20
Hello,
I thought the order source blocks were tangled was the order of the
file. I just discovered this is not necessarily the case. This file:
--8<---cut here---start->8---
#+BEGIN_SRC foob :tangle foo.ml
let x = 1
#+END_SRC
#+BEGIN_SRC fooa :tangle foo.ml
le
On Tuesday, 16 Feb 2016 at 06:22, Derek Feichtinger wrote:
[...]
> Placing point on the TBLFM line and doing C-c C-c should recalculate
> the whole table.
as should C-u C-c C-c anywhere in the table.
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3.2-164-g50a182
Hi
> >
> > Try this
> >
> > | N | |
> > |---+---|
> > | | |
> > | | |
> > | | |
> > | | |
> > #+TBLFM: $1..>$1= -1 + 1:: 2$1=1
> >
Sorry, I had a typo from copying and replacing in my formula
should be
| N | |
|---+---|
| 1 | |
| 2 | |
| 3 |
33 matches
Mail list logo
