From: "Eric Schulte" <schulte.eric@gmail.com>
To: Hsiu-Khuern Tang <tangoh@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: bug: babel: Export of temporary buffers fails
Date: Tue, 05 Oct 2010 11:56:28 -0600 [thread overview]
Message-ID: <87tyl0bk1f.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTimF_BToj_0iOKSH7Y84-UgxcDkvCbMLuVA2K3xz@mail.gmail.com> (Hsiu-Khuern Tang's message of "Mon, 4 Oct 2010 10:08:08 -0700")
Hi,
This issue is fixed in the "combined-testing" branch of the repository,
I hope to merge that branch into the master branch soon.
If anyone is interested, some of my thoughts on this commit which has
caused these couple of recent problems... It seems that by using
org-links to find the location of a headline in an Org-mode file during
export I have introduced a handful of little bugs in the export process.
I think these have now been fixed but the fixes are a little bit hacky,
however I think that relying on org-mode links for finding these
headlines is still preferable to implementing a Babel-specific method of
linking back to the original export file.
Best -- Eric
Hsiu-Khuern Tang <tangoh@gmail.com> writes:
> Hi Eric,
>
>
> Are you also seeing the problem reported at
> http://thread.gmane.org/gmane.emacs.orgmode/30855? I checked out the
> latest git version and that problem still exists.
>
>
> I don't know how closely it is related to the problem in this thread,
> but it was caused by the same commit
> (efdf78172d9f7c0070c781d136a9b49a2a56fcc4) -- hoping you can shed some
> light on this. Thanks!
prev parent reply other threads:[~2010-10-05 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 16:30 bug: babel: Export of temporary buffers fails Puneeth
2010-10-02 17:21 ` Eric Schulte
2010-10-02 19:38 ` Sebastian Rose
2010-10-03 3:37 ` Puneeth
2010-10-04 13:13 ` Eric Schulte
2010-10-04 13:59 ` Puneeth
2010-10-04 14:39 ` Eric Schulte
2010-10-04 15:16 ` Puneeth
2010-10-04 17:08 ` Hsiu-Khuern Tang
2010-10-05 17:56 ` Eric Schulte [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=87tyl0bk1f.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tangoh@gmail.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).