emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: cberry@tajo.ucsd.edu
To: emacs-orgmode@gnu.org
Subject: Re: Code vanishes on export
Date: Wed, 24 Aug 2011 10:36:25 -0700	[thread overview]
Message-ID: <87wre2ogo6.fsf@tajo.ucsd.edu> (raw)
In-Reply-To: CAMXnza1tNBAH2JBOwUHoznAembP2gVnTednqmHfUx=A9vF1-+g@mail.gmail.com

suvayu ali <fatkasuvayu+linux@gmail.com> writes:

> Hi Eric,
>
> On Wed, Aug 24, 2011 at 3:58 PM, Eric Schulte <schulte.eric@gmail.com> wrote:
>> Vikas Rawal <vikaslists@agrarianresearch.org> writes:
>>
>>> I obviously do not want the code to be removed from my org file.
>>>
>>
>> There are ways of controlling whether code or results or both or neither
>> are included in code export.
>>
>
> As far as I understand from Vikas' last remark, his org file is getting
> changed.

FWIW, I experienced this myself. "#+begin_src R" blocks vanished from
the *.org file during export (but I was saved by version control!).

I think this behavior showed up after 7.7, but I cannot reproduce it now
(I did a git pull at release_7.7.170.gcaaad.dirty and have since modified
the *.org file on which it happened).

IIRC, it did not happen for exports when :export never was set for the
buffer and not circumvented by  '#+begin_src R :eval t'. 

Maybe this has (coincidentally) been corrected by the recent update of
ob-exp.el, ob.el, and org-exp-blocks.el?
 
Chuck


-- 
Charles C. Berry     

  reply	other threads:[~2011-08-24 18:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 10:13 Code vanishes on export Vikas Rawal
2011-08-24 10:23 ` Sebastien Vauban
2011-08-24 13:58 ` Eric Schulte
2011-08-24 14:45   ` suvayu ali
2011-08-24 17:36     ` cberry [this message]
2011-08-24 19:45       ` Eric Schulte
2011-08-24 23:37     ` Vikas Rawal
     [not found]       ` <87obzez7vy.fsf@tajo.ucsd.edu>
2011-08-25  0:08         ` Vikas Rawal
2011-08-25  7:11       ` suvayu ali

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=87wre2ogo6.fsf@tajo.ucsd.edu \
    --to=cberry@tajo.ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    /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).