emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "D. C. Toedt" <dc@toedt.com>
To: emacs-orgmode@gnu.org
Subject: Re: Exporter aborts upon encountering even one unresolvable link
Date: Thu, 24 Sep 2015 22:00:37 -0500	[thread overview]
Message-ID: <CAGN11+1FhZ7vLibff0VmMvmDjeU7FGGorkP28SS7Zv+f2Jca+w@mail.gmail.com> (raw)
In-Reply-To: <CAGN11+0215j8k83g3RH8Kf8-u4TzqmsqTK5wTr8ZUDZaGXm8Fw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]

P.S.:   Thank heavens for Time Machine.




On Thu, Sep 24, 2015 at 9:50 PM, D. C. Toedt <dc@toedt.com> wrote:

> I just updated to 8.3.1 from 8.3beta (from git).  That appears to have
> been a terrible mistake on my part.
>
> From this thread
> <https://lists.gnu.org/archive/html/emacs-orgmode/2015-09/msg00040.html>
> I see that the exporter now throws an error and aborts when it encounters
> an unresolvable link.  That makes things really, REALLY difficult.  It
> means I can't get a complete, working export to HTML (in my case) until all
> link problems are fixed in my 22KLOC .org file (which I use to generate
> http://www.CommonDraft.org/index.html
> <http://www.commondraft.org/index.html>).  That seems EXTREMELY
> suboptimal. (I'm trying to be tactful here.)
>
> Worse, the exporter doesn't even generate a list of unresolvable links
> before aborting.  That means the only way that I can find and fix busted
> links (so far as I know) is to do an export --- which takes several minutes
> given the large file  --- and have the export abort on a single link.
> Then I fix that one link, export again, and have it abort again. Repeat.
> Aaaargggggg.
>
> I started looking at the hooks, as suggested in a message in the previous
> thread, but I'm not nearly skilled enough in elisp to be able to do
> anything useful.
>
> Any suggestions?
>
>
> *D. C. Toedt III  **(My last name is pronounced "Tate"; I go by "D. C.,"
> which stands for Dell Charles**) *
> Attorney & neutral arbitrator -- tech contracts & IP  |  Adjunct
> professor, University of Houston Law Center
> ​Author, ​​​Common Draft <http://www.commondraft.org/> desk book of
> contract clauses & research notes   |  LinkedIn: dctoedt
> <http://www.linkedin.com/in/dctoedt>   |   Calendar
> <https://www.google.com/calendar/embed?src=dc.toedt@toedt.com&mode=WEEK>
> (redacted)
> E: dc@toedt.com    O: +1 (713) 364-6545    C: +1 (713) 516-8968
> ​​
>
> ​
> Houston, Texas (Central time zone)
>
> Unless expressly stated otherwise, this message is not intended
> to serve as assent to an agreement or other document, whether or not
> attached to this message.
>
>
>

[-- Attachment #2: Type: text/html, Size: 8050 bytes --]

  reply	other threads:[~2015-09-25  3:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25  2:50 Exporter aborts upon encountering even one unresolvable link D. C. Toedt
2015-09-25  3:00 ` D. C. Toedt [this message]
2015-09-25  7:05   ` Rainer M Krug
2015-09-25  7:04 ` Rainer M Krug
2015-09-28  2:19   ` Suvayu Ali
2015-10-07 13:51   ` D. C. Toedt
2015-10-07 14:02     ` Rainer M Krug
2015-10-09 22:28   ` D. C. Toedt
2015-10-10 10:32     ` D. C. Toedt
2015-09-28  7:53 ` thomas
2015-09-28 11:21   ` Nick Dokos

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=CAGN11+1FhZ7vLibff0VmMvmDjeU7FGGorkP28SS7Zv+f2Jca+w@mail.gmail.com \
    --to=dc@toedt.com \
    --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).