emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: <c.buhtz@posteo.jp>
To: emacs-orgmode@gnu.org
Subject: Re: ox-publish: no HTML output but no errors
Date: Sun,  6 Mar 2022 09:05:01 +0000	[thread overview]
Message-ID: <4KBFzQ06YSz9rxF@submission02.posteo.de> (raw)
In-Reply-To: <svaujd$5lr$1@ciao.gmane.io>

Dear Max,

thank you for the hint.

On 2022-02-25 23:02 Max Nikulin <manikulin@gmail.com> wrote:
> Some users may consider a broken link as a fatal error. If you need 
> different behavior, you can get it. See info "(org) Export Settings" 
> https://orgmode.org/manual/Export-Settings.html for "broken-links".

From the manual it is not clear for me how to set that option.
In-buffer is not an option for me. I tried to set it like this

(require 'ox-publish)
(setq org-publish-project-alist
       :base-directory "~/tab-cloud/my.org-roam/"
       :base-extension "org"
       :publishing-directory "~/tab-cloud/_transfer/html"
       :recursive t
       :publishing-function org-html-publish-to-html
       :headline-levels 4             ; Just the default for this
project. :auto-preamble t
       :base-directory "~/tab-cloud/my.org-roam/"
:publishing-directory "~/tab-cloud/_transfer/html" :recursive t
       :publishing-function org-publish-attachment
      ("org" :components ("org-notes" "org-static")
       :broken-links "mark"

But this has no effect.
I also tried to "(setq org-export-with_broken-links t)". But the
message keeps the same.

  reply	other threads:[~2022-03-06  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 14:14 ox-publish: no HTML output but no errors c.buhtz
2022-02-25 16:02 ` Max Nikulin
2022-03-06  9:05   ` c.buhtz [this message]
2022-03-07 14:59     ` Max Nikulin

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:

  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=4KBFzQ06YSz9rxF@submission02.posteo.de \
    --to=c.buhtz@posteo.jp \
    --cc=emacs-orgmode@gnu.org \


* 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


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).