Hi,
if a value outputted by R in a Babel block contains quotes only the
quoted parted is exported.
Consider this:
#+BEGIN_SRC R
q = 'cat="S"'
q
#+END_SRC
#+RESULTS:
: S
The expected result would be entire string, i.e. 'cat="S"' (without
single quotes). Is there a workaround? I've tried escapin
Hi Luis,
On Sun, Jul 8, 2012 at 3:49 AM, Luis Anaya wrote:
> suvayu ali writes:
>
> Hi Sevayu!
>
>>
>> have the content pages at the end instead of the front. Is there any
>> particular reason for that?
>
> Yes there is a reason.
>
> The MM implementation of table of contents collects all the he
suvayu ali writes:
Hi Sevayu!
>
> have the content pages at the end instead of the front. Is there any
> particular reason for that?
Yes there is a reason.
The MM implementation of table of contents collects all the headers and
captions that have read up to the point of execution of the table
Hi Nick,
Nick Dokos wrote:
> Viktor Rosenfeld wrote:
>
> > Hi,
> >
> > I can't get SBE blocks called from a table to work, if they use
> > functions like org-parse-time-string.
> >
> > Suppose I have the following table:
> >
> > | Start| Ende | |
> > |
Hi Luis,
The outputs look great. However I have a question; I see all the PDFs
have the content pages at the end instead of the front. Is there any
particular reason for that?
Keep up the good work. :)
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Thorsten Jolitz writes:
> in elisp code, with point in entry1, I do a save-excursion that inserts
> another entry2 and does some work there. After existing from the
> save-excursion form, I add e.g. a global ID with org-id-get-create - and
> would expect to find it in entry1 when save-excursion d
Hi List,
in elisp code, with point in entry1, I do a save-excursion that inserts
another entry2 and does some work there. After existing from the
save-excursion form, I add e.g. a global ID with org-id-get-create - and
would expect to find it in entry1 when save-excursion did its job right.
But
I should clarify that image files that are supported in groff, get
inlined when a link is written.
Hence,
[[file:image.eps]] or
[[file:image.pic]]
Will include the image and write the image in the resultant PDF file.
Sorry if I confused anybody... :(
--
Luis Anaya
papo anaya aroba hot mail p
In case you were curious how today's updates look like (if you're not,
then yeah, I'm showing up :) ), samples of these can be found at:
Sources:
graph.org - http://ppl.ug/droqQrYmMkw/
todo.org - http://ppl.ug/W6RBCb7gNAs/
PDF results:
graph.pdf - http://ppl.ug/YGVUBTwhknY/
todo.org - http://p
oops. attached the wrong patch. amended patch follows.
>From b9192f5e9a3bbe9620d9f588313d7f62e33135a5 Mon Sep 17 00:00:00 2001
From: Suhail Shergill
Date: Sun, 8 Apr 2012 10:49:51 -0400
Subject: [PATCH] org-html.el: Make footnotes unique to an entry
* lisp/org-html.el (org-export-as-html): Assig
Viktor Rosenfeld wrote:
> Hi,
>
> I can't get SBE blocks called from a table to work, if they use
> functions like org-parse-time-string.
>
> Suppose I have the following table:
>
> | Start| Ende | |
> |--+--+-|
> | [2011-06-29 Wed] | [20
running org-export-as-html on a subtree is currently problematic if the result
is to be merged into a document which contains html-ized versions of other
subtrees: the footnote references and definitions get clobbered.
this patch uses the CUSTOM_ID property of the subtree to generate unique
footno
Nicolas Goaziou writes:
Hi:
> This is the known bug I told you about in another thread. It will be
> fixed soon after org-element hits core.
Oh... I guess I missed that email :( At least I know that named captions are
working for images.
In other news...
Other things I got working today ar
Hello,
Luis Anaya writes:
> Eric Schulte writes:
>
>>
>> Instead of putting the #+Caption: line on the source block, place it on
>> the result. This requires the use of named code blocks and results.
>> The following alternate version of your example should give the behavior
>> you're after.
>
Eric Schulte writes:
>
> Instead of putting the #+Caption: line on the source block, place it on
> the result. This requires the use of named code blocks and results.
> The following alternate version of your example should give the behavior
> you're after.
>
[chomp...]
Hi Eric:
Thanks for you
Hi,
I can't get SBE blocks called from a table to work, if they use
functions like org-parse-time-string.
Suppose I have the following table:
| Start| Ende | |
|--+--+-|
| [2011-06-29 Wed] | [2012-02-29 Wed] | |
#+TBLFM: $3='(sbe "billable-
Not all use cases are identical to yours.
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Samuel Wales writes:
> On 7/7/12, Christoph Groth wrote:
>> I would say that a proper solution would be to reserve
>> delete-other-windows for interactive use and to replace it by
>> something more sensible which ensures that a given window is well
>> visible but tries to preserve the visibility
Luis Anaya writes:
> From the documentation, I know that captions work with inline images
> and tables, but for some reason when then inline images are generated
> through org-babel, #+CAPTION keys turns into regular text. What am I
> doing wrong now? :)
>
Instead of putting the #+Caption: line
Unless I misunderstand, you can set
org-log-repeat to 'time to log state changes and also store
a LAST_REPEAT, or to nil to not log state changes and also
not store a LAST_REPEAT. You can't tell it to do one and
not the other.
I want to log state changes but not store LAST_REPEAT unless
it is alg
On 7/7/12, Christoph Groth wrote:
> I would say that a proper solution would be to reserve
> delete-other-windows for interactive use and to replace it by something
> more sensible which ensures that a given window is well visible but
> tries to preserve the visibility and arrangement other window
Eric Abrahamsen writes:
> On Thu, Jun 14 2012, Christoph Groth wrote:
>> How to ensure that the buffer which was active when org-capture was
>> executed remains visible during date entry?
> I've had the same annoyance. The attached patch is *not* a real
> solution to the problem, as it still pr
>From the documentation, I know that captions work with inline images
and tables, but for some reason when then inline images are generated
through org-babel, #+CAPTION keys turns into regular text. What am I
doing wrong now? :)
-- ORG Source --
#+TITLE: Graphic Tests
#+AUTHOR: Luis R. Anaya
#+G
suvayu ali writes:
> No you understood it correctly. This does not happen for me. Do you
> have any idea how I can track this issue down?
You may try to debug `org-export-to-file'. I have no idea about what
could remove the buffer containing the tex file.
On Sat, Jul 7, 2012 at 2:32 PM, Nicolas Goaziou wrote:
> It does here. Exporting with "l" or "d" leaves the corresponding tex
> file open in a buffer.
>
> Am I misunderstanding your request?
No you understood it correctly. This does not happen for me. Do you
have any idea how I can track this iss
Hello,
suvayu ali writes:
> Another question, I noticed that the new exported does not have the
> exported file open in Emacs after it is done.
It does here. Exporting with "l" or "d" leaves the corresponding tex
file open in a buffer.
Am I misunderstanding your request?
Regards,
--
Nicola
Vikas Rawal writes:
>> >
>> > [1] Off the top of the head I recall a package called `scrlttr'.
>>
>> Yes, part of KOMA (?), but thats rather low level if you have to design
>> your own letters - and who knows all that stuff about professional letter
>> design?. I tried that once and the result w
Mehul Sanghvi writes:
> Just out of curiosity, what was the CV template you used ?
I attach 3 variations of the same template, I used the one from TRAVIS
as a basis for my CV, but the others are nice too.
%% start of file `template_en.tex'.
%% Copyright 2007 Xavier Danaux (xdan...@gmail.com).
%
Hi Nicolas,
Apologies for taking so long to respond.
On Thu, Jul 5, 2012 at 1:56 PM, Nicolas Goaziou wrote:
> Now, /every/ property set through an export keyword can also be defined
> with an headline property. That property has the same name as the
> keyword, with an "EXPORT_" prefix (i.e #+DA
* Nicolas Goaziou wrote:
>
> Hello,
Hello Nicolas!
> Based on your work, I've put up the attached back-end:
> org-koma-letter.el.
... and this is why I *love* this community so much :-)
Yes, you are absolutely right that my method is unnecessary complex
using this «generate TeX-files and Makef
30 matches
Mail list logo
