Re: [O] Latex strikethrough or cancel?

[Nick Dokos]

Lawrence Bottorff  writes:

> Actually I spoke too soon. Putting
>
> (setq org-html-mathjax-template (concat org-html-mathjax-template "
> 
> MathJax.Hub.Register.StartupHook(\"TeX Jax Ready\",function () {
>   MathJax.Hub.Insert(MathJax.InputJax.TeX.Definitions.macros,{
>     cancel: [\"Extension\",\"cancel\"],
>     bcancel: [\"Extension\",\"cancel\"],
>     xcancel: [\"Extension\",\"cancel\"],
>     cancelto: [\"Extension\",\"cancel\"]
>   });
> });
> 
> "))
> ​
> in my init didn't fly when I rebooted, although it seemed to work
> before when I stuck it in my init and did eval-buffer.
> ...
> Would appreciate any advice on how to incorporate the \cancel code
> into org-html-mathjax-template.
>

The code assumes that org-html-mathjax-template has been initialized
already, so either

(require 'ox-html)

beforehand or use eval-after-load:

(eval-after-load "ox-html"
 (setq org-html-mathjax-template ))

-- 
Nick

[O] [wish] Execute preparation-function before getting base files

[Arun Isaac]

In org-publish-projects, it would be good if the preparation-function is
executed before getting base files using org-publish-get-base-files.

In one of my use cases, my preparation-function generates some source
files which are then to be published by the publishing-function. But,
since the base filenames are collected before the preparation-function
is executed, the publishing-function does not see the generated source
files.

Right now, I'm calling my preparation-function manually before calling
org-publish-project, but it would be nice if I didn't have to do it this
way.

Thanks,
Arun Isaac.


signature.asc
Description: PGP signature

Re: [O] Latex strikethrough or cancel?

[Lawrence Bottorff]

Actually I spoke too soon. Putting

(setq org-html-mathjax-template (concat org-html-mathjax-template "

MathJax.Hub.Register.StartupHook(\"TeX Jax Ready\",function () {
  MathJax.Hub.Insert(MathJax.InputJax.TeX.Definitions.macros,{
cancel: [\"Extension\",\"cancel\"],
bcancel: [\"Extension\",\"cancel\"],
xcancel: [\"Extension\",\"cancel\"],
cancelto: [\"Extension\",\"cancel\"]
  });
});

"))
​
in my init didn't fly when I rebooted, although it seemed to work before
when I stuck it in my init and did eval-buffer. Going back to

#+begin_html

 MathJax.Hub.Config({
   TeX: {extensions: ["cancel.js"]},
   tex2jax: {
 inlineMath: [ ['$','$'], ['\\(','\\)'] ],
 processEscapes: true
   }
 });

#+end_html

Would appreciate any advice on how to incorporate the \cancel code
into org-html-mathjax-template.

Re: [O] Minning Org-files

[Doyley, Marvin M.]

Hi John,

It works like a charm. 

Thank you so so so much
cheers,
M
> On Oct 10, 2015, at 8:06 AM, John Kitchin  wrote:
> 
> sure, if you make an interactive function that takes a search argument.
> Something like this
> 
> (defun some-name (search-arg)
> (interactive "sQuery: ")
> ; insert code below and change "TODO=\"DONE\"" to search-arg
> )
> 
> 
> Doyley, Marvin M. writes:
> 
>> Is there anyway of making the search term a variable ?
>> 
>>> On Oct 9, 2015, at 1:24 PM, John Kitchin  wrote:
>>> 
>>> You can do something like this:
>>> 
>>> By TODO keyword to grab the DONE entries.
>>> 
>>> #+BEGIN_SRC emacs-lisp
>>> (let ((entries (org-map-entries
>>>   (lambda ()
>>> (save-restriction
>>>   (org-narrow-to-subtree)
>>>   (buffer-string)))
>>>   "TODO=\"DONE\"")))
>>> (switch-to-buffer (get-buffer-create "new"))
>>> (org-mode)
>>> (mapcar 'insert entries))
>>> #+END_SRC
>>> 
>>> 
>>> 
>>> Doyley, Marvin M. writes:
>>> 
 Hi there,
 
 I have a huge org-file with notes I have taken on various topics (my 
 commonplace org file). Is there an easy way to grab all the entires with a 
 given tag or keyword to a new org-file ?
 
 Thanks,
 M
 
 ---
 Marvin Doyley Ph.D.
 University of Rochester
 Associate Professor of Electrical and Computer Engineering
 Associate Professor of Biomedical Engineering
 333 Hopeman Engineering Building
 Rochester NY 14627
>>> 
>>> --
>>> Professor John Kitchin
>>> Doherty Hall A207F
>>> Department of Chemical Engineering
>>> Carnegie Mellon University
>>> Pittsburgh, PA 15213
>>> 412-268-7803
>>> @johnkitchin
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__kitchingroup.cheme.cmu.edu&d=BQIBAg&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=T41F_5QsIVBGYhPPUkgYHUp9iPHgs2rOCjs7rfKaTMU&m=ZjP3xZzVOvLNMInBTkxBhV_-2rP9uP3owADCIadxXxk&s=ry0y4fD4NMUUCHUpPSK5djnyUZWt57fxbXHuhqUfSls&e=
> 
> --
> Professor John Kitchin
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> https://urldefense.proofpoint.com/v2/url?u=http-3A__kitchingroup.cheme.cmu.edu&d=BQIBAg&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=T41F_5QsIVBGYhPPUkgYHUp9iPHgs2rOCjs7rfKaTMU&m=hnMwDGuA_hdr-MPhQEOOEcDQ7Wd1eLgQFHotHKPOM2Y&s=KAVoqsDi0jWRU6Ilqh5eq16troIjU6lPlk-AQ99ZTv8&e=
>  

Re: [O] Minning Org-files

[Doyley, Marvin M.]

Awesome,

I really appreciate this. I must teach myself how to code in lisp :)
cheers,
M
> On Oct 10, 2015, at 8:06 AM, John Kitchin  wrote:
> 
> sure, if you make an interactive function that takes a search argument.
> Something like this
> 
> (defun some-name (search-arg)
> (interactive "sQuery: ")
> ; insert code below and change "TODO=\"DONE\"" to search-arg
> )
> 
> 
> Doyley, Marvin M. writes:
> 
>> Is there anyway of making the search term a variable ?
>> 
>>> On Oct 9, 2015, at 1:24 PM, John Kitchin  wrote:
>>> 
>>> You can do something like this:
>>> 
>>> By TODO keyword to grab the DONE entries.
>>> 
>>> #+BEGIN_SRC emacs-lisp
>>> (let ((entries (org-map-entries
>>>   (lambda ()
>>> (save-restriction
>>>   (org-narrow-to-subtree)
>>>   (buffer-string)))
>>>   "TODO=\"DONE\"")))
>>> (switch-to-buffer (get-buffer-create "new"))
>>> (org-mode)
>>> (mapcar 'insert entries))
>>> #+END_SRC
>>> 
>>> 
>>> 
>>> Doyley, Marvin M. writes:
>>> 
 Hi there,
 
 I have a huge org-file with notes I have taken on various topics (my 
 commonplace org file). Is there an easy way to grab all the entires with a 
 given tag or keyword to a new org-file ?
 
 Thanks,
 M
 
 ---
 Marvin Doyley Ph.D.
 University of Rochester
 Associate Professor of Electrical and Computer Engineering
 Associate Professor of Biomedical Engineering
 333 Hopeman Engineering Building
 Rochester NY 14627
>>> 
>>> --
>>> Professor John Kitchin
>>> Doherty Hall A207F
>>> Department of Chemical Engineering
>>> Carnegie Mellon University
>>> Pittsburgh, PA 15213
>>> 412-268-7803
>>> @johnkitchin
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__kitchingroup.cheme.cmu.edu&d=BQIBAg&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=T41F_5QsIVBGYhPPUkgYHUp9iPHgs2rOCjs7rfKaTMU&m=ZjP3xZzVOvLNMInBTkxBhV_-2rP9uP3owADCIadxXxk&s=ry0y4fD4NMUUCHUpPSK5djnyUZWt57fxbXHuhqUfSls&e=
> 
> --
> Professor John Kitchin
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> https://urldefense.proofpoint.com/v2/url?u=http-3A__kitchingroup.cheme.cmu.edu&d=BQIBAg&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=T41F_5QsIVBGYhPPUkgYHUp9iPHgs2rOCjs7rfKaTMU&m=hnMwDGuA_hdr-MPhQEOOEcDQ7Wd1eLgQFHotHKPOM2Y&s=KAVoqsDi0jWRU6Ilqh5eq16troIjU6lPlk-AQ99ZTv8&e=
>  

Re: [O] PROPERTIES and LOGBOOK order

[John J Foerch]

Marco Wahl  writes:

> Hello John,
>
> John J Foerch  writes:
>
>> After a recent upgrade to org 8.3.2 (elpa 20150929) some of my org files
>> were broken with respect to drawers.  They include headlines that have
>> both attachments in a PROPERTIES drawer, and a LOGBOOK drawer.
>> Sometimes the LOGBOOK was before PROPERTIES, and sometimes the other way
>> around.
>>
>> In cases where LOGBOOK was before PROPERTIES, the command to view the
>> attachments directory (C-c C-a f) would not recognize the existing
>> PROPERTIES drawer, and create a new one instead with a new ID and a new
>> empty attachments directory.  After I manually changed the order of the
>> drawers so that PROPERTIES was first, the existing PROPERTIES drawer was
>> again recognized and it worked as expected.
>
> AFAICS you found an incompatible change of org 8.3.  See
> http://orgmode.org/Changes.html or in etc/ORG-NEWS of a respective org
> source tree.

Thanks!

--
John Foerch

Re: [O] PROPERTIES and LOGBOOK order

[Marco Wahl]

Hello John,

John J Foerch  writes:

> After a recent upgrade to org 8.3.2 (elpa 20150929) some of my org files
> were broken with respect to drawers.  They include headlines that have
> both attachments in a PROPERTIES drawer, and a LOGBOOK drawer.
> Sometimes the LOGBOOK was before PROPERTIES, and sometimes the other way
> around.
>
> In cases where LOGBOOK was before PROPERTIES, the command to view the
> attachments directory (C-c C-a f) would not recognize the existing
> PROPERTIES drawer, and create a new one instead with a new ID and a new
> empty attachments directory.  After I manually changed the order of the
> drawers so that PROPERTIES was first, the existing PROPERTIES drawer was
> again recognized and it worked as expected.

AFAICS you found an incompatible change of org 8.3.  See
http://orgmode.org/Changes.html or in etc/ORG-NEWS of a respective org
source tree.

-- 
Marco Wahl
GPG: 0x49010A040A3AE6F2

Re: [O] [RFC] Draft mode

[Nicolas Goaziou]

Rasmus  writes:

> While I agree that options such as 't:·', '^:·', 'h:·' are bad, I think
> 'barf:·' is nice.  It's short and precise, much like 'num:·'.
>
> Something like 'barf-on-invalid-link' is very easy to mistype or forget.
> And yes, I mostly type options by hand.

Here's another take on this, which is quite different from the original
draft mode. Now, behaviour on broken links is controlled with
`org-export-with-broken-links' or its OPTIONS counterpart
"broken-links".

It is possible to either error on a broken link, ignore it, or mark it
with an obnoxious string in the output.


Feedback welcome.


Regards,

>From 0508461b2d57629e1c391c57a7326093f61b07e6 Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou 
Date: Sat, 10 Oct 2015 16:03:05 +0200
Subject: [PATCH] ox: Add an option to ignore broken links

* lisp/ox.el (org-export-with-broken-links): New variable.
(org-export-options-alist): Add new OPTIONS item.
(broken-link): New error type.
(org-export-resolve-coderef):
(org-export-resolve-fuzzy-link):
(org-export-resolve-id-link): Raise appropriate error symbol when a link
cannot be resolved.
(org-export-data): Handle new error type.
---
 lisp/ox.el | 221 -
 1 file changed, 132 insertions(+), 89 deletions(-)

diff --git a/lisp/ox.el b/lisp/ox.el
index d140f17..d74f48b 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -112,6 +112,7 @@
 (:time-stamp-file nil "timestamp" org-export-time-stamp-file)
 (:with-archived-trees nil "arch" org-export-with-archived-trees)
 (:with-author nil "author" org-export-with-author)
+(:with-broken-links nil "broken-links" org-export-with-broken-links)
 (:with-clocks nil "c" org-export-with-clocks)
 (:with-creator nil "creator" org-export-with-creator)
 (:with-date nil "date" org-export-with-date)
@@ -797,6 +798,27 @@ is nil.  You can also allow them through local buffer variables."
   :package-version '(Org . "8.0")
   :type 'boolean)
 
+(defcustom org-export-with-broken-links nil
+  "Non-nil means do not raise an error on broken links.
+
+When this variable is non-nil, broken links are ignored, without
+stopping the export process.  If it is set to `mark', broken
+links are marked as such in the output, with a string like
+
+  [BROKEN LINK: path]
+
+where PATH is the un-resolvable reference.
+
+This option can also be set with the OPTIONS keyword, e.g.,
+\"broken-links:mark\"."
+  :group 'org-export-general
+  :version "25.1"
+  :package-version '(Org . "8.4")
+  :type '(choice
+	  (const :tag "Ignore broken links" t)
+	  (const :tag "Mark broken links in output" mark)
+	  (const :tag "Raise an error" nil)))
+
 (defcustom org-export-snippet-translation-alist nil
   "Alist between export snippets back-ends and exporter back-ends.
 
@@ -1851,91 +1873,106 @@ string.  INFO is a plist holding export options.
 
 Return a string."
   (or (gethash data (plist-get info :exported-data))
-  (let* ((type (org-element-type data))
-	 (results
-	  (cond
-	   ;; Ignored element/object.
-	   ((memq data (plist-get info :ignore-list)) nil)
-	   ;; Plain text.
-	   ((eq type 'plain-text)
-		(org-export-filter-apply-functions
-		 (plist-get info :filter-plain-text)
-		 (let ((transcoder (org-export-transcoder data info)))
-		   (if transcoder (funcall transcoder data info) data))
-		 info))
-	   ;; Secondary string.
-	   ((not type)
-		(mapconcat (lambda (obj) (org-export-data obj info)) data ""))
-	   ;; Element/Object without contents or, as a special
-	   ;; case, headline with archive tag and archived trees
-	   ;; restricted to title only.
-	   ((or (not (org-element-contents data))
-		(and (eq type 'headline)
-			 (eq (plist-get info :with-archived-trees) 'headline)
-			 (org-element-property :archivedp data)))
-		(let ((transcoder (org-export-transcoder data info)))
-		  (or (and (functionp transcoder)
-			   (funcall transcoder data nil info))
-		  ;; Export snippets never return a nil value so
-		  ;; that white spaces following them are never
-		  ;; ignored.
-		  (and (eq type 'export-snippet) ""
-	   ;; Element/Object with contents.
-	   (t
-		(let ((transcoder (org-export-transcoder data info)))
-		  (when transcoder
-		(let* ((greaterp (memq type org-element-greater-elements))
-			   (objectp
-			(and (not greaterp)
- (memq type org-element-recursive-objects)))
-			   (contents
-			(mapconcat
-			 (lambda (element) (org-export-data element info))
-			 (org-element-contents
-			  (if (or greaterp objectp) data
-;; Elements directly containing
-;; objects must have their indentation
-;; normalized first.
-(org-element-normalize-contents
- data
- ;; When normalizing contents of the
- ;; first paragraph in an item or
- ;; a footnote definition, ignore
- ;; first line's indentation: there is
- ;; none and it might be misleading.
- (when (eq type 'pa

[O] org-attach-directory

[John J Foerch]

Hello,

I have a collection of org files in a git repository, and am using
git-annex for attachments.  I had an idea for a feature related to
org-attach-directory that would improve the usability of git-annex in a
case like this.

Since all attachments from all org files in the repo go into the same
data directory, there isn't a simple way to operate on the attachments
related to a single org file in bulk.  For instance, if one wants to
git-annex-get all of the attachments for one org file, but not others,
one must git-annex-get each file individually.

One solution would be for each org file to live in its own subdirectory,
thus each org file would have its own data directory:

org-file: org/work/work.org
attachemts-in: org/work/data/

I don't especially like this solution because it adds a lot of
unnecessary structure to the repo.

Another solution would be for each org file to have its own data
directory alongside it:

org-file: org/work.org
attachments-in: org/work.org.data/

I don't especially like this one either because it makes a mess of the
repository root.

The solution I like best is to store attachments in data/, but to
introduce a subdirectory per org file:

org-file: org/work.org
attachments-in: org/data/work.org/

It keeps the repository root uncluttered, but attachments are grouped by
the file that owns them, so can be operated on in bulk by git-annex or
other tools.

I can set up this configuration with org-mode-hook, but I liked the idea
so well that I wanted to pass it along as something that org-mode might
want to provide itself as an option.  Perhaps org-mode could check for
the existence of data/{filename} and when it exists, set the local value
of org-attach-directory to that instead of to "data/".  If it were
automatic like this, then org files that used this feature would remain
portable.  Perhaps a file-local variable or an org directive would be a
better option.

Any thoughts?

Thank you,

John Foerch

[O] PROPERTIES and LOGBOOK order

[John J Foerch]

Hello,

After a recent upgrade to org 8.3.2 (elpa 20150929) some of my org files
were broken with respect to drawers.  They include headlines that have
both attachments in a PROPERTIES drawer, and a LOGBOOK drawer.
Sometimes the LOGBOOK was before PROPERTIES, and sometimes the other way
around.

In cases where LOGBOOK was before PROPERTIES, the command to view the
attachments directory (C-c C-a f) would not recognize the existing
PROPERTIES drawer, and create a new one instead with a new ID and a new
empty attachments directory.  After I manually changed the order of the
drawers so that PROPERTIES was first, the existing PROPERTIES drawer was
again recognized and it worked as expected.

Thank you,

John Foerch

Re: [O] First steps in customizing org-mode

[Thomas S . Dye]

Giulio Petrucci  writes:

> Hi Eric,
>
> thanks for your reply.
>
> On Fri, Oct 9, 2015 at 6:02 PM, Eric Abrahamsen  
> wrote:
>> Google's not the place to look! For once. One of the main principles of
>> Emacs, and thus of Org mode, is that it is self-documenting. You'll get
>> a better sense of what `org-agenda-custom-commands' does, and how to use
>> it, by hitting "C-h v org-agenda-custom-commands" than you will from any
>> other source. There's even a clickable link to customize it.
>
> In some sense I strongly disagree with this idea.
> Let me explain: it is true that reading the docs for
> 'org-agenda-custom-commands' helps me more than googling here and
> there.
> But *first* I have to know that such a variable exists.
> So my actual problem is the following: which is the easiest entry
> point for the org universe?

There are likely many answers to this question, depending on your goals
and computer skill level.

Worg says the Tutorials page is your best starting point:

http://orgmode.org/worg/org-tutorials/index.html

Carsten Dominick put together the Org guide (later translated into
Spanish) for this purpose:

http://orgmode.org/guide/index.html

I find the helm interface super useful for finding Org mode variables
and functions.  Type in a couple of key words and the list of candidates
is usually short enough to browse helpfully.  In a way, it is like
Google for the emacs universe.

hth,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: [O] Minning Org-files

[John Kitchin]

sure, if you make an interactive function that takes a search argument.
Something like this

(defun some-name (search-arg)
 (interactive "sQuery: ")
 ; insert code below and change "TODO=\"DONE\"" to search-arg
 )


Doyley, Marvin M. writes:

> Is there anyway of making the search term a variable ?
>
>> On Oct 9, 2015, at 1:24 PM, John Kitchin  wrote:
>>
>> You can do something like this:
>>
>> By TODO keyword to grab the DONE entries.
>>
>> #+BEGIN_SRC emacs-lisp
>> (let ((entries (org-map-entries
>>(lambda ()
>>  (save-restriction
>>(org-narrow-to-subtree)
>>(buffer-string)))
>>"TODO=\"DONE\"")))
>>  (switch-to-buffer (get-buffer-create "new"))
>>  (org-mode)
>>  (mapcar 'insert entries))
>> #+END_SRC
>>
>>
>>
>> Doyley, Marvin M. writes:
>>
>>> Hi there,
>>>
>>> I have a huge org-file with notes I have taken on various topics (my 
>>> commonplace org file). Is there an easy way to grab all the entires with a 
>>> given tag or keyword to a new org-file ?
>>>
>>> Thanks,
>>> M
>>>
>>> ---
>>> Marvin Doyley Ph.D.
>>> University of Rochester
>>> Associate Professor of Electrical and Computer Engineering
>>> Associate Professor of Biomedical Engineering
>>> 333 Hopeman Engineering Building
>>> Rochester NY 14627
>>
>> --
>> Professor John Kitchin
>> Doherty Hall A207F
>> Department of Chemical Engineering
>> Carnegie Mellon University
>> Pittsburgh, PA 15213
>> 412-268-7803
>> @johnkitchin
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__kitchingroup.cheme.cmu.edu&d=BQIBAg&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=T41F_5QsIVBGYhPPUkgYHUp9iPHgs2rOCjs7rfKaTMU&m=ZjP3xZzVOvLNMInBTkxBhV_-2rP9uP3owADCIadxXxk&s=ry0y4fD4NMUUCHUpPSK5djnyUZWt57fxbXHuhqUfSls&e=

--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

Re: [O] Exporter aborts upon encountering even one unresolvable link

[D. C. Toedt]

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
​​

d...@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 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 pronoun

Re: [O] First steps in customizing org-mode

[Giulio Petrucci]

Hi Eric,

thanks for your reply.

On Fri, Oct 9, 2015 at 6:02 PM, Eric Abrahamsen  wrote:
> Google's not the place to look! For once. One of the main principles of
> Emacs, and thus of Org mode, is that it is self-documenting. You'll get
> a better sense of what `org-agenda-custom-commands' does, and how to use
> it, by hitting "C-h v org-agenda-custom-commands" than you will from any
> other source. There's even a clickable link to customize it.

In some sense I strongly disagree with this idea.
Let me explain: it is true that reading the docs for
'org-agenda-custom-commands' helps me more than googling here and
there.
But *first* I have to know that such a variable exists.
So my actual problem is the following: which is the easiest entry
point for the org universe?

Thanks,
Giulio

--