From: "D. C. Toedt" <dc@toedt.com>
To: Rainer M Krug <Rainer@krugs.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Exporter aborts upon encountering even one unresolvable link
Date: Sat, 10 Oct 2015 05:32:05 -0500 [thread overview]
Message-ID: <CAGN11+2S=G8-dex-JG8Gqnb9vfsQv+4zhMeXWpEgr00Fk+XRJQ@mail.gmail.com> (raw)
In-Reply-To: <CAGN11+0fVPHZv3L8X3EjGHKTF687xdBFss7AsR+SQQvqLPbPuQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5552 bytes --]
UPDATE:
> I haven't tried org-lint yet (
http://steve.planetbarr.com/posts/2015-08-11-org-lint.html).
> That requires building org from a separate branch in git. That makes me
nervous --
> I'm a user, not a dev, and while I'm sort of familiar with git, it seems
like yet another layer of complexity.
1. OK, I got org-mode version 8.3.2 up and running using git.
The org-lint feature works -- very nice.
> The old way, namely just marking the problem link in the output file and
continuing with the export,
> made it very easy to search for the problem in the output file. That
approach was simple and worked quite well.
I still think that, but at least I'm up and running again.
Thanks to all for putting up with my lack of expertise, and especially to
the org-mode creator(s) and maintainers for a very-useful tool.
2. For background: I'm a lawyer and part-time law professor. I've been
using org-mode for several years now in building http:/www.CommonDraft.org
-- a free (Creative Commons) library of clauses for tech- and commercial
contracts, extensively annotated with citations, commentary, and links to
further reading. The long-term goal is to have a Common Draft reference
version of each substantive variation of each type of contract clause
that's typically seen in the wild. That will free up lawyers from always
having to draft detailed contract language, and from having to review other
people's detailed language --- instead, we can simply incorporate desired
Common-Draft clauses by reference. (It's analogous to a library of callable
functions in software development.) That will save time for both the
contract drafter and for the other side's legal reviewer, which in turn
will help the parties get a workable contract to signature sooner, at lower
cost.
In pitching the Common Draft concept, my latest metaphor for non-techies is
this: If you're ordering a meal in a Chinese-food restaurant, but you
don't want any monosodium glutamate (MSG) in your food, you're _not_ going
to hand your server a set of detailed recipes for the dishes you want and
ask that the kitchen staff use those recipes. No, you're simply going to
order from the menu --- hot-and-sour soup, kung-pao chicken, or whatever
--- but you'll say to your server, "no MSG, please," as a desired
variation. It's the same idea for the Common Draft project: A contract
drafter can "order from the menu" and specify any desired variations. The
Common Draft project is starting to get some attention in the
contract-management community; the International Association for Contract
and Commercial Management (http://www.IACCM.com), which has around 35,000
members worldwide, is supporting it.
D. C. Toedt III
*(My last name is pronounced "Tate")*
Attorney & arbitrator -- tech contracts & IP
Common Draft <http://www.CommonDraft.org> toolkit for contract drafters
O: +1 (713) 364-6545
C: +1 (713) 516-8968
dc@toedt.com
www.OnContracts.com/About
Unless expressly stated otherwise,
this message is not intended to serve
as assent to an agreement or other document,
even if attached to this message.
On Fri, Oct 9, 2015 at 5:28 PM, D. C. Toedt <dc@toedt.com> wrote:
> >> Look at publishing instead of exporting to html which works with missing
> links.
>
>
> Apparently it doesn't.
> I'm still having the same problem of throwing a fatal error --- even when
> publishing, not exporting --- when encountering a missing (unresolvable)
> link. This was after doing a clean install of org-mode 8.3.2 (20151005,
> using the emacs package manager) on top of a clean install of the latest
> stable version of emacs (24.5) from EmacsForMacOSX. (I'm running the latest
> version of Mac OS X Yosemite; haven't gotten around to El Capitan.) I then
> set up publishing the way Rainer suggested in his email. Well, publishing
> likewise throws an error when it encounters a missing link target, just as
> does exporting.
>
> > You can use org-lint for this.
>
> I haven't tried org-lint yet (
> http://steve.planetbarr.com/posts/2015-08-11-org-lint.html). That
> requires building org from a separate branch in git. That makes me nervous
> -- I'm a user, not a dev, and while I'm sort of familiar with git, it seems
> like yet another layer of complexity.
>
> I don't mean to be a nag, but I genuinely don't understand why org-mode's
> former way of dealing with unresolvable links during export was disabled.
> The old way, namely just marking the problem link in the output file and
> continuing with the export, made it very easy to search for the problem in
> the output file. That approach was simple and worked quite well. It also
> allowed exporting a single .org file, instead of jumping through the hoops
> of publishing a project. The new way seems like a giant step backwards;
> it's likely to be a significant barrier to entry for non-expert users.
>
> Can the old way of dealing with unresolvable links be restored, at least
> as an option?
>
>
>
> D. C. Toedt III
> *(My last name is pronounced "Tate")*
> Attorney & arbitrator -- tech contracts & IP
> Common Draft <http://www.CommonDraft.org> toolkit for contract drafters
> O: +1 (713) 364-6545
> C: +1 (713) 516-8968
>
>
> dc@toedt.com
> www.OnContracts.com/About
>
> Unless expressly stated otherwise,
> this message is not intended to serve
> as assent to an agreement or other document,
> even if attached to this message.
>
>
>
[-- Attachment #2: Type: text/html, Size: 16495 bytes --]
next prev parent reply other threads:[~2015-10-10 10:32 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
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 [this message]
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+2S=G8-dex-JG8Gqnb9vfsQv+4zhMeXWpEgr00Fk+XRJQ@mail.gmail.com' \
--to=dc@toedt.com \
--cc=Rainer@krugs.de \
--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).