emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Jörg Hagmann" <joerg.hagmann@unibas.ch>
Cc: emacs-orgmode@gnu.org, Giovanni@reflections.co.nz
Subject: Re: Re: Bug: subtree export fails with src block
Date: Mon, 04 Oct 2010 09:06:26 -0600	[thread overview]
Message-ID: <87d3rq6lql.fsf@gmail.com> (raw)
In-Reply-To: <4CA9EC7A.6080103@unibas.ch> ("Jörg Hagmann"'s message of "Mon, 04 Oct 2010 17:02:18 +0200")

Similar,

I think this thread is also related
http://thread.gmane.org/gmane.emacs.orgmode/31312/focus=31392

either way the issue should be fixed in the latest Org-mode.  Please let
me know if that is not the case.

Best -- Eric

Jörg Hagmann <joerg.hagmann@unibas.ch> writes:

>  This might be the same problem I discussed recently?
> See this thread:
> http://thread.gmane.org/gmane.emacs.orgmode/31241/focus=31289
>
> Jörg
>
> On 10/4/10 3:48 PM, Eric Schulte wrote:
>> "Eric Schulte"<schulte.eric@gmail.com>  writes:
>>
>> [...]
>>> "Giovanni Moretti"<Giovanni@reflections.co.nz>  writes:
>>>
>>>> I'm just starting with Babel and have been puzzled about why one file
>>>> worked and another didn't.
>>>>
>>>> I have been playing in a new file without any headers at all (no lines
>>>> starting with '*') and while I could execute the code in the buffer,
>>>> exporting to HTML always failed with:
>>>>
>>>>     No such file: c:/org/babel-python-test.org::
>>>>
>>> Hmm, it looks like it's trying to find a file with "::" attached to the
>>> end which is probably the source of the issue.  I wonder if this is a
>>> windows specific problem?
>>>
>> a-ha,
>>
>> I just noticed that while my test file "python.org" was exporting w/o
>> problem, it was opening a "python.org::" buffer in the process, so maybe
>> the reason this throws errors for you and not for me is just Unix's more
>> permissive file names.
>>
>> I've just pushed up a change to the Babel exporter that will only concat
>> the "::" to the end of a file name, where there is actually a heading to
>> following it.  Hopefully this will fix the error you described, please
>> let me know if that is not the case.
>>
>> Best -- Eric
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-10-04 15:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04  3:02 Re: Bug: subtree export fails with src block Giovanni Moretti
2010-10-04 13:21 ` Eric Schulte
2010-10-04 13:48   ` Eric Schulte
2010-10-04 15:02     ` Jörg Hagmann
2010-10-04 15:06       ` Eric Schulte [this message]
2010-10-05  7:07         ` Jörg Hagmann
  -- strict thread matches above, loose matches on Subject: below --
2010-09-23  7:13 Christian Moe
2010-09-23  7:25 ` Noorul Islam K M
2010-09-23 15:17   ` Eric Schulte
2010-09-23 18:22     ` Christian Moe

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=87d3rq6lql.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=Giovanni@reflections.co.nz \
    --cc=emacs-orgmode@gnu.org \
    --cc=joerg.hagmann@unibas.ch \
    /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).