Myles English writes:
> Myles English writes:
>
>> Nicolas Goaziou writes:
>>
>>> One option could be to define a specialized latex back-end dedicated to
>>> moderncv class, much like "ox-koma-letter.el" does for "scrlttr2".
>>
>> I did actually make a start on this, I'll dig it out and put it
>>
I would like to export some Org document properties as ODT user defined
fields for use in ODT templates. For example, it would be great if
something like
#+ODT_FIELD: FOO:17 BAR:"Hello, world!"
in the Org document exported the following user defined fields in the
content.xml.
Hi Nicolas,
Thanks for your feedback.
2014ko irailak 20an, Nicolas Goaziou-ek idatzi zuen:
>
> The problem I see here is that you're introducing yet another internal
> representation for lists (along with element's and
> org-list-parse-list's). Worse, it can only be discovered when reading
> the
Hi Nicolas,
2014ko irailak 19an, Nicolas Goaziou-ek idatzi zuen:
>
> Certainly not a message, due to asynchronous export.
Very good point.
>
>> 2. Since this is a feature that many backends will want to use, should
>> we introduce a new “abstract” backend from which other backends can
>> inher
Hi Nicolas,
2014ko irailak 19an, Nicolas Goaziou-ek idatzi zuen:
[...]
>
> In any case, I think you can apply the patch once the docstrings
> questions above have been sorted out.
Thanks for all your feedback. The patch is now applied on master.
> This can do for now. Ultimately, however, I
On Tue, Sep 23, 2014 at 12:00 AM, Nicolas Goaziou
wrote:
> Hello,
>
> "Kyeong Soo (Joseph) Kim" writes:
>
> > By the way, as said, [[*Foo][Section Foo]] does not produce the link in
> > LaTeX export any longer; version 8.x generates just "\texttt{Section
> Foo}"
> > unlike version 7.x.
>
> An EC
Aloha Rasmus,
Rasmus writes:
> So I guess we should let the patch hang for a while and see if someone
> cares to test it.
>
> Of course I'd appreciate more comments/bug reports.
I'm looking forward to this functionality and will test out the patch
now that you're happy with its performance.
Hi,
Another couple of small changes.
Random observation: the patch is "almost" neutral due to the
headline-id function:
88 insertions(+), 72 deletions(-)
Nicolas Goaziou writes:
> I think it would be nice to keep "sec-NUM", with NUM matching current
> numbering, for numbered headlines
Myles English writes:
> Nicolas Goaziou writes:
>
>> One option could be to define a specialized latex back-end dedicated to
>> moderncv class, much like "ox-koma-letter.el" does for "scrlttr2".
>
> I did actually make a start on this, I'll dig it out and put it
> somewhere accessible, soon.
..
Hello,
John Kitchin writes:
> Thanks for the clarification. Is there any chance you know why this
> transformation is done? Does it avoid some problem?
No idea.
Regards,
--
Nicolas Goaziou
I have the following agendas (among others) defined:
("x" "Last worked" ((alltodo "" (
Nicolas Goaziou writes:
Thanks for the clarification. Is there any chance you know why this
transformation is done? Does it avoid some problem?
> Hello,
>
> John Kitchin writes:
>
>> Thanks for the tips. I did not see a way to do the advice here. For what
>> I need, we need to save parameters f
Hello,
phillip.l...@newcastle.ac.uk (Phillip Lord) writes:
> I'm rather struggling with the new exporter. I fear I have used a
> combination of old and new configuration which cannot be helping.
> I am trying to get publishing working mostly in batch, so that it will
> work as part of my continuo
I'm rather struggling with the new exporter. I fear I have used a
combination of old and new configuration which cannot be helping.
I am trying to get publishing working mostly in batch, so that it will
work as part of my continuous integration framework. But having it work
interactively would be
Hello,
John Kitchin writes:
> Thanks for the tips. I did not see a way to do the advice here. For what
> I need, we need to save parameters for each code block. But it appears
> they are all affected by one function org-babel-exp-process-buffer, and
> advising this kind of function is tantamount
Charles Berry writes:
Thanks for the tips. I did not see a way to do the advice here. For what
I need, we need to save parameters for each code block. But it appears
they are all affected by one function org-babel-exp-process-buffer, and
advising this kind of function is tantamount to rewriting t
Aaron Ecay writes:
Thanks for the confirmation this happens, and the pointer to where it
happens.
I guess there was at one point a good reason to do this, but I cannot
see it directly.
I found a way to do it with filters and preprocessing, which is
illustrated here:
http://kitchingroup.cheme.c
Hello,
"Kyeong Soo (Joseph) Kim" writes:
> By the way, as said, [[*Foo][Section Foo]] does not produce the link in
> LaTeX export any longer; version 8.x generates just "\texttt{Section Foo}"
> unlike version 7.x.
An ECM illustrating the problem would be nice.
"\textt{Section Foo}" means that
Hello,
Christian Moe writes:
> Here's a simple CSS workaround that might or might not work well for
> you, and won't work for non-HTML backends, but at least requires minimal
> hacking:
[...]
Good to know.
Anyhow, does my proposal make sense?
Regards,
--
Nicolas Goaziou
Hello,
Rasmus writes:
> With the last patch it gets weird when you have mixed trees, like this:
>
> * numbered
> ** unnumbered
> :PROPERTIES:
> :UNNUMBERED: t
> :END:
>
> The LaTeX output is:
>
> \section{numbered}
> \label{sec-1}
> \subsection*{unnumbered}
>
Hello,
Tobias Getzner writes:
> I have a strange problem when exporting the following file:
>
> * heading 1
> #+BEGIN_SRC sh :eval never
> echo baz
> #+END_SRC
>
> * heading 2
> #+BEGIN_SRC sh :exports results
> echo quux
> #+END_SRC
>
> When I export this document, and point is on heading 1 whe
Hello,
Brett Witty writes:
> (Following Thorsten's helpful response:
> http://article.gmane.org/gmane.emacs.orgmode/90768)
>
> I'd like an extra special property of HEADLINE which is ITEM without all
> the other metadata. Specifically the output of:
>
> (org-get-heading t t)
>
> I find the ITEM
(Following Thorsten's helpful response:
http://article.gmane.org/gmane.emacs.orgmode/90768)
I'd like an extra special property of HEADLINE which is ITEM without all
the other metadata. Specifically the output of:
(org-get-heading t t)
I find the ITEM special property too noisy inside of a table,
whether this is the expected
behavior. Should the export already take into account any results produced
during the export run?
Any ideas where to look or what the problem might be?
Best,
T.
Org-mode version 8.2.7c (8.2.7c-71-g60418c-elpa @ /home/tzg/.emacs.d/elpa/
org-20140922/)
Rainer M Krug writes:
>
> I like Dan's approach as it looks relatively simple, although I still
> have to look into it in detail (and as Joseph notes, there must be a
> problem in the code).
>
> ...
> Dan Griswold writes:
>> ...
>>
>> First, a "cv" class added to org-latex-classes:
>>
>> (add-to
Evaluating LaTeX source blocks had an issue where header options would be
ignored when exporting to SVG; this appears to have been addressed in
246df88. I have patched this commit into my 8.2.7c installation. While
the headers now seem to work, I’ve noticed that LaTeX still doesn’t like
the gen
Xavier Garrido writes:
> Hi Rainer,
>
> You can see mine https://github.com/xgarrido/org-resume that uses
> org-mode to produce a LaTeX->PDF (see attached file) file as well as
> an HTML version.
>
> Hope it gives you some ideas.
I can only say *wow*! This looks seriously impressive to me.
I w
Joseph Vidal-Rosset writes:
> Le sam. 20 sept. 2014 à 02:49:03 , Dan Griswold a
> envoyé ce message:
>> Not sure anybody saw this the first time, so I'll try again, with some
>> expansion.
>>
>> Unlike the others who've commented, I moved my CV from LaTeX to
>> org-mode and I'm happy with t
Myles English writes:
> Hello,
>
> Nicolas Goaziou writes:
>
>> Brady Trainor writes:
>>
>>> And I did have a decent export to LaTeX resume from org, but after
>>> discovering moderncv, I've switched, though I will be curious to read
>>> others' methods of org-to-moderncv export.
>>
>> One opt
Vikas Rawal writes:
> I know I am being lazy in not trying it out, but if you could share a
> PDF, it would give us an idea of what this gives you.
Yes - an example pdf would be great.
Rainer
>
> Vikas
>
> On 20-Sep-2014, at 6:19 am, Dan Griswold wrote:
>
>> Not sure anybody saw this the fi
Rasmus writes:
> Nicolas Goaziou writes:
>
>> Hello,
>>
>> Brady Trainor writes:
>>
>>> And I did have a decent export to LaTeX resume from org, but after
>>> discovering moderncv, I've switched, though I will be curious to read
>>> others' methods of org-to-moderncv export.
>>
>> One option
Brady Trainor writes:
> On 9/19/2014 2:18 AM, Rainer M Krug wrote:
>> Hi
>>
>> - How do you do it (I don't assume you write your CVs in Word?), or are
>> you using LaTeX directly?
>
> Nice question, I will enjoy reading all the examples in this thread.
>
> For a bit, I tried to make org do everyt
torys.ander...@gmail.com (Tory S. Anderson) writes:
> Very nice, John. Thanks for sharing the LaTeX!
I agree - thanks.
I will take a closer look later and possibly use some ideas.
Rainer
>
> John Hendy writes:
>
>> Like the rest, I picked straight LaTeX, as it just felt like forcing Org to
>
First of all, thanks to everybody so far who responded to this
question.
I reply to my question directly, as I am trying to sum up the replies
so far (the complete thread is theoretically below).
There are effectively two "schools",
- using LaTeX (Tory, Andreas, John and Brady), and
- using o
If at least one of your computers can be reached from all the others via
ssh, or you can reach all the other computers from one (i.e. there’s a
star topology), you could use unison to synchronize all kinds of files.
This works very reliably and handles modifications in both directions.
I use git f
Hello Orgers,
please consider: Emacs -Q and evaluate the following
#+BEGIN_SRC emacs-lisp
(org-babel-do-load-languages
'org-babel-load-languages
'((calc . t)
(emacs-lisp . t)
))
#+END_SRC
#+RESULTS:
| (calc . t) | (emacs-lisp . t) |
The following works as expected
#+BEGIN_SRC calc :var
36 matches
Mail list logo
