2013ko martxoak 8an, Eric Schulte-ek idatzi zuen:
>
> I would agree. I don't believe *any* changes should take place in the
> buffer when a code block is executed with ":results none".
A common use case for me is to use a babel block to load a large dataset
into R. I want this to be cached, in
Hi Rasmus,
2013ko martxoak 7an, Rasmus Pank Roulund-ek idatzi zuen:
>
> In my book it would seem 'natural' to strive towards the following:
>
> 1. It should be Bibtex-based. I.e. Bibtex should be the 'database'
> or storage for citation information. It may be stored in
> Org-Bibtex
Hello Bastien (et al),
2013ko martxoak 7an, Bastien-ek idatzi zuen:
>
> Hi Nicolas,
>
> I like Aaron's idea (maybe others proposed this too) of having
> parameters in links:
>
> [[file:my.bib::key&&prenote=my prenote&&postnote=my postnote]]
>
> [[http://perdu.com&&title=You're lost?]]
>
> Thi
Hi Thomas,
I think the following patch (on top of current master) will fix the
problem:
-cut-here-
diff --git c/lisp/ox-latex.el w/lisp/ox-latex.el
index d17dd60..eefb272 100644
--- c/lisp/ox-latex.el
+++ w/lisp/ox-latex.el
@@ -1811,9 +1811,9 @@ used as a communication channel."
;
2013ko martxoak 6an, Bastien-ek idatzi zuen:
> I'd suggest to treat org-link-abbrev-alist and locally defined
> abbreviated links differently when opening the link at point and
> when exporting the buffer.
>
> At expand time, the exporter could attach a list of export functions
> (filters?) to the
2013ko otsailak 27an, Nicolas Goaziou-ek idatzi zuen:
> Thank you for your patch. Here are a few comments.
Thank you for the comments! I think the patch is simpler and better
thanks to them.
>
>> These are implemented with \resizebox, and thus are uniform across
>> different types of image incl
