From: Nick Dokos <nicholas.dokos@hp.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Re: Export to html
Date: Thu, 27 May 2010 17:30:55 -0400 [thread overview]
Message-ID: <14045.1274995855@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from "Thomas S. Dye" <tsd@tsdye.com> of "Thu, 27 May 2010 08:30:08 -1000." <7FBE0CD8-67F9-41AC-B1C1-47D2AEB1C2C3@tsdye.com>
Thomas S. Dye <tsd@tsdye.com> wrote:
> Aloha all,
>
> On the bus this morning I was able to find out a bit more about
> problems with html export.
>
> Using Bernt's minimal.emacs and exporting to html with C-c C-e H, git
> bisect says:
>
> 459d99c44c7df4cd09d82fa54c53e5d5eec47a4e is the first bad commit
> commit 459d99c44c7df4cd09d82fa54c53e5d5eec47a4e
> Author: Tom Breton (Tehom) <tehom@panix.com>
> Date: Mon May 17 18:17:38 2010 -0400
>
> Moved to new branch
>
> Prior to this commit file links are exported like this:
>
> <a href="index.pdf">file:index.pdf</a>
>
> After the commit, file links are exported like this:
>
> <a href="file:index.pdf">index.pdf</a>
>
> I was a bit surprised at the git bisect result because I understood
> Tom Breton (Tehom) to be working on a testing framework, rather than
> html export. So, I ran through git bisect a second time and got
> identical results.
>
> I hope I've understood the procedure correctly and that this
> information is useful. At this point, I'm in way over my head and
> won't be able to do more without specific instructions.
>
> I'm currently using commit d56d417bc214088114e10c959ce78bee2d26635d on
> the master branch to make my exporting and publishing setup work as
> expected.
>
Tom,
I can't reproduce the busted link. With more-or-less-current Org-mode
(version 6.36trans (release_6.36.102.g67b5)), the link looks like this:
<a href="foo.pdf">foo.pdf</a>
Reverting the commit you identified (the revert was not clean: I had to
resolve a merge conflict by hand - a dicey proposition, particularly in
this situation where I have no idea what the patch is trying to do)
gives me:
<a href="foo.pdf">file:foo.pdf</a>
That's with your minimal.emacs for the other problem you've identified
(changed to produce html of course). So it looks like the patch cleaned
up the link name in this case.
Nick
PS. I also looked at the commit: I gave up on figuring it out in any
reasonable time, but I must say the commit comment is no help.
next prev parent reply other threads:[~2010-05-27 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 18:30 Export to html Thomas S. Dye
2010-05-27 21:30 ` Nick Dokos [this message]
2010-05-27 22:06 ` Thomas S. Dye
2010-05-27 22:35 ` Sebastian Rose
2010-05-28 3:13 ` Thomas S. Dye
-- strict thread matches above, loose matches on Subject: below --
2007-06-16 6:14 export " Cecil Westerhof
2007-06-16 12:34 ` Carsten Dominik
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=14045.1274995855@alphaville.usa.hp.com \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).