From: John Hendy <jw.hendy@gmail.com>
To: Li Bowen <a0050726@nus.edu.sg>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
nicholas.dokos@hp.com, Jay Kerns <gjkernsysu@gmail.com>
Subject: Re: org-babel src block generated graphics included twice if CAPTION is added
Date: Sun, 17 Mar 2013 21:53:10 -0500 [thread overview]
Message-ID: <CA+M2ft-rQdNUb0dbZ=y2=kQRQva0wbRDz_NLEdAu-Do_wJXxbw@mail.gmail.com> (raw)
In-Reply-To: <87620pcxuo.fsf@nus.edu.sg>
[-- Attachment #1: Type: text/plain, Size: 1839 bytes --]
On Sun, Mar 17, 2013 at 8:15 PM, Li Bowen <a0050726@nus.edu.sg> wrote:
> Thanks, John.
>
> I also noticed that #+options can lead to re-insertion.
>
> Your piece of instruction should go to the online documentation. It will
> save people hours of time from trouble-shooting. I suppose any one who
writes a report with figures using org-babel will face the same problem.
I've got some other changes to make to Worg... I'll look for a place to put
this as well, though Eric's patch probably makes this obsolete now! At
least your post, the nth inquiry about it to the mailing list, has gotten
us a patch! That counts for something!
By the way, I've run into this very thing before as well :)
- http://osdir.com/ml/emacs-orgmode-gnu/2012-07/msg00230.html
John
>
> John Hendy <jw.hendy@gmail.com> writes:
>
>> On Sun, Mar 17, 2013 at 6:20 PM, Jay Kerns <gjkernsysu@gmail.com> wrote:
>>> On Sun, Mar 17, 2013 at 6:21 PM, Nick Dokos <nicholas.dokos@hp.com>
wrote:
>>>
>>> [snip]
>>>
>>>> I think the best way to deal with problems like this is to name your
code blocks (and results blocks).
>>>>
>>>
>>> [snip]
>>>
>>> I can't speak for Li, but it works on my system and I like Nick's
>>> solution better than mine.
>>
>> This is my preferred syntax as well. This has come up before on the
>> list; essentially any #+options syntax before an un-named #+results
>> block will cause the results to be re-inserted. #+begin_center or any
>> #+attr_backend options result in the same duplicate insertion of
>> results.
>>
>>
>> Also, just in case it's not known, you don't have to manually name the
>> #+results block. Just create your babel block with a #+name: attribute
>> and when you run it with C-c C-c, a named #+result will automatically
>> be created.
>>
>> John
>>
>>>
>>> Cheers,
>>>
>>> --
>>> Jay
>>>
>
> --
> Sincerely,
> Li Bowen.
[-- Attachment #2: Type: text/html, Size: 2717 bytes --]
prev parent reply other threads:[~2013-03-18 2:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a0050726@nus.edu.sg>
2013-03-17 13:10 ` org-babel src block generated graphics included twice if CAPTION is added Li Bowen
2013-03-17 22:08 ` Jay Kerns
2013-03-17 22:21 ` Nick Dokos
2013-03-17 23:20 ` Jay Kerns
2013-03-18 0:32 ` John Hendy
2013-03-18 0:59 ` Eric Schulte
2013-03-18 6:38 ` Achim Gratz
2013-03-18 12:23 ` Eric Schulte
[not found] ` <87620pcxuo.fsf@nus.edu.sg>
2013-03-18 2:53 ` John Hendy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+M2ft-rQdNUb0dbZ=y2=kQRQva0wbRDz_NLEdAu-Do_wJXxbw@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=a0050726@nus.edu.sg \
--cc=emacs-orgmode@gnu.org \
--cc=gjkernsysu@gmail.com \
--cc=nicholas.dokos@hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).