From: "D. C. Toedt" <dc@toedt.com>
To: emacs-orgmode@gnu.org
Subject: Re: Exporter aborts upon encountering even one unresolvable link
Date: Wed, 7 Oct 2015 06:51:59 -0700 [thread overview]
Message-ID: <CAGN11+26eZeydkKSSQeBUx+6kSm-2oQc9aEczqyYduCVLi6Uow@mail.gmail.com> (raw)
In-Reply-To: <m2si63dloi.fsf@krugs.de>
[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]
To the org-mode maintainers (all praise and thanks to them, incidentally):
Is there any chance that this can be made into a per-file configuration
#+OPTION? No doubt the publishing approach suggested by Rainer (thanks
also to him for suggesting it) would work, but it would take some effort to
get it set up; I've looked into publishing on previous occasions and
concluded it was easier just to do a simple HTML export. Other things
being equal, #+OPTION options would be easier for non-expert users such as
me to work with, than fiddling with the .emacs file.
D. C. Toedt III
*(My last name is pronounced "Tate")*
Attorney & arbitrator -- tech contracts & IP
Common Draft <http://www.CommonDraft.org> contracts project
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, Sep 25, 2015 at 12:04 AM, Rainer M Krug <Rainer@krugs.de> wrote:
[portions omitted]
>
> Look at publishing instead of exporting to html which works with
>
> missing links.
>
>
>
> I have the following in my emacs.org which makes it possible to publish
> all org files to html in the folder ./pubHTML/ which is equivalent to
> exporting.
>
> #+begin_src emacs-lisp
> (setq org-publish-project-alist
> '(
> ("local"
> :base-directory "./"
> :base-extension "org"
> :publishing-directory "./pubHTML/"
> :recursive t
> :publishing-function org-html-publish-to-html
> :headline-levels 6
> :auto-preamble t)
> ))
> #+end_src
>
>
>
[-- Attachment #2: Type: text/html, Size: 6373 bytes --]
next prev parent reply other threads:[~2015-10-07 13:52 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 [this message]
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+26eZeydkKSSQeBUx+6kSm-2oQc9aEczqyYduCVLi6Uow@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).