From mboxrd@z Thu Jan 1 00:00:00 1970 From: "D. C. Toedt" Subject: Re: Exporter aborts upon encountering even one unresolvable link Date: Sat, 10 Oct 2015 05:32:05 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1134fd90e222d90521bd9de0 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40154) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZkrSL-0007Uc-Vk for emacs-orgmode@gnu.org; Sat, 10 Oct 2015 06:32:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZkrSH-000665-W5 for emacs-orgmode@gnu.org; Sat, 10 Oct 2015 06:32:49 -0400 Received: from mail-oi0-f54.google.com ([209.85.218.54]:35326) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZkrSH-00065v-PD for emacs-orgmode@gnu.org; Sat, 10 Oct 2015 06:32:45 -0400 Received: by oiao187 with SMTP id o187so7207343oia.2 for ; Sat, 10 Oct 2015 03:32:45 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Rainer M Krug Cc: emacs-orgmode@gnu.org --001a1134fd90e222d90521bd9de0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 toolkit for contract drafters O: +1 (713) 364-6545 C: +1 (713) 516-8968 =E2=80=8B=E2=80=8B 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 wrote: > >> Look at publishing instead of exporting to html which works with missi= ng > links. > =E2=80=8B=E2=80=8B > > 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 late= st > version of Mac OS X Yosemite; haven't gotten around to El Capitan.) I th= en > set up publishing the way Rainer suggested in his email. Well, publishin= g > likewise throws an error when it encounters a missing link target, just a= s > 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 nervo= us > -- I'm a user, not a dev, and while I'm sort of familiar with git, it see= ms > 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 i= n > the output file. That approach was simple and worked quite well. It also > allowed exporting a single .org file, instead of jumping through the hoop= s > 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 toolkit for contract drafters > O: +1 (713) 364-6545 > C: +1 (713) 516-8968 > =E2=80=8B=E2=80=8B > > 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. > > > --001a1134fd90e222d90521bd9de0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
UPDATE:

> I haven't tried org-lint yet (= http://steve.planetbarr.com/posts/2015-08-11-org-lint.html).=C2=A0=C2= =A0
> That requires building org from a separate= branch in git.=C2=A0 That makes me nervous --=C2=A0
> I'm a user, not a dev, and while I'm sort of familiar with g= it, it seems like yet another layer of complexity.
=
1.=C2=A0 OK, I got org-mode version 8.3.2 up a= nd running using git. =C2=A0

The org-lint feature works -- very nice.
<= br>
> The old way, namely just marking the probl= em link in the output file and continuing with the export,=C2=A0
> made it very easy to search for the problem in the outpu= t file. That approach was simple and worked quite well.=C2=A0

I still think that, but at least I&= #39;m up and running again.

Thanks to all for putting up with my lack of expertise, and especiall= y to the org-mode creator(s) and maintainers for a very-useful tool.

2.=C2=A0 For background:= I'm a lawyer and part-time law professor.=C2=A0 I've been using or= g-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 cita= tions, commentary, and links to further reading.=C2=A0 The long-term goal i= s 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 w= ill 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&= #39;s analogous to a library of callable functions in software development.= ) =C2=A0That 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 worka= ble contract to signature sooner, at lower cost.
In pitching the Common Draft concept, my latest = metaphor for non-techies is this: =C2=A0If you're ordering a meal in a = Chinese-food restaurant, but you don't want any monosodium glutamate (M= SG) in your food, you're _not_ going to hand your server a set of detai= led recipes for the dishes you want and ask that the kitchen staff use thos= e recipes.=C2=A0 No, you're simply going to order from the menu --- hot= -and-sour soup, kung-pao chicken, or whatever --- but you'll say to you= r server, "no MSG, please," as a desired variation.=C2=A0 It'= s the same idea for the Common Draft project: =C2=A0A contract drafter can = "order from the menu" and specify any desired variations. The Com= mon Draft project is starting to get some attention in the contract-managem= ent community; the International Association for Contract and Commercial Ma= nagement (http://www.IACCM.com), which= has around 35,000 members worldwide, is supporting it.




=
D. C.= Toedt III=C2=A0
(My last name is pronounced "Tate")=
Attorney & arbitrator -- tech con= tracts & IP
Common Draft toolkit for contract drafters
O: +1 (713) 364-6545=C2=A0 =C2=A0
C: +1 (713) 516-8968
=E2=80=8B=E2=80=8B
=C2=A0= =C2=A0

=
Unless expres= sly stated otherwise,
this message=C2=A0is not intended=C2=A0to serve
as assent to an agreement=C2=A0or other document,
eve= n if=C2=A0attac= hed to this message.


<= /div>

On Fri, Oct 9, 2015 at 5:28 PM, D. C. Toedt = <dc@= toedt.com> wrote:
>>=C2=A0Look at publishing instead of exporting to htm= l which works with=C2=A0missing links.
=E2=80=8B=E2=80=8B

Apparently it doesn't= . =C2=A0
I'm still having the same problem of throwing a fatal err= or --- even when publishing, not exporting --- when encountering a missing = (unresolvable) link.=C2=A0 This was after doing a clean install of org-mode= 8.3.2 (20151005, using the emacs package manager) on top of a clean instal= l 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 aroun= d to El Capitan.) =C2=A0I then set up publishing the way Rainer suggested i= n his email.=C2=A0 Well, publishing likewise throws an error when it encoun= ters a missing link target, just as does exporting.
<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif= ;font-size:small">
>=C2=A0You can use org-lint for this.

I haven't tried org-lint yet (= http://steve.planetbarr.com/posts/2015-08-11-org-lint.html).=C2=A0 That= requires building org from a separate branch in git.=C2=A0 That makes me n= ervous -- I'm a user, not a dev, and while I'm sort of familiar wit= h git, it seems like yet another layer of complexity.

I don't mean to be a nag, but I genuine= ly don't understand why org-mode's former way of dealing with unres= olvable links during export was disabled.=C2=A0 The old way, namely just ma= rking the problem link in the output file and continuing with the export, m= ade it very easy to search for the problem in the output file. That approac= h was simple and worked quite well.=C2=A0 It also allowed exporting a singl= e .org file, instead of jumping through the hoops of publishing a project.= =C2=A0 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 unresolvabl= e links be restored, at least as an option?


=
<= div dir=3D"ltr">

D. C. Toedt III=C2= =A0
(My last name is pronounced "Tate")
Attorney & arbitrator -- tech contracts & = IP
Common Draft= toolkit for contract drafters
O: +1 (713) 364-6545=C2=A0 =C2=A0
C: +1 (713) 516-8968
=E2=80=8B=E2=80=8B=
=C2=A0=C2=A0

Unless expressly stated otherwise,
this message=C2=A0= is not intended= =C2=A0to serve =
as assent t= o an agreement=C2=A0or other document,
even if=C2=A0attached to this message.


<= /div>
<= /div>

--001a1134fd90e222d90521bd9de0--