Subject: ox-publish: Some starting problems
Date: Wed, 09 Mar 2022 08:55:09 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
I was able to generate HTML files of my org-roam (v2) nodes. But I have
some problems and need to be pointed into the right direction.
Is this mailing list the right place to discuss ox-publish related
topics? The ox-publish.el only contains two e-mail addresses?
Because ox-publish is skipping "unmodified files" I deleted all HTML
files between the publish-runs just to be sure that there are no side
effects. But now when my output directory is totally empty ox-publish
still keeps saying that it is skipping the unmodified files. So nothing
is generated anymore. How can I handle that? Maybe resetting the
"unmodified" flag somewhere? Or shouldn't ox-publish not only check for
modifications but if there is something earlier generated content exist?
I use (setq org-export-with-broken-links t) with and without
":with-broken-links "mark"" to prevend ox-publish stopping when there
are broken links. I swear and I also checked that there are only a few
of them. But in the HTML output all links are gone. No links. No text
for the links.
I tried to reproduce this in a minimal example with two new nodes. But
for them the links are generated.
The links (of all nodes!) are working very well inside of org-roam.
Any idea how could go on with diagnosis here?
First I thought ox-publish has a problem with org-roam-v2 id-links. But
the two new created nodes just for testing where working well. The older
nodes (just 2 months old) also using id-links and where created with the
same Emacs and org-roam version.
ox-publish ignores newlines. Two short lines in the org-file becomes one
line in the HTML content.
I am not totally new to Emacs but quit fresh. So I have two questions
about how to handle the documentation and help informations here.
a) I tried to "descrbie" the mode "ox-publish". But Emacs only offers me
an "describe-mode" which describe all currently existing nodes. There is
nothing like "describe-mode MODENAME". How can I handle that?
b) I another thread I was pointed to
https://orgmode.org/manual/Publishing-options.html . There is no
description about the options they are only listed. This does not help
me. Maybe there are some useful options that could solve some of my
problems. But without description I am not able to decide or know.
Is there a way to integrated backlinks into output?
next reply other threads:[~2022-03-09 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 8:55 c.buhtz [this message]
2022-03-09 9:41 ` ox-publish: Some starting problems c.buhtz
2022-03-09 15:57 ` Max Nikulin
2022-03-09 15:32 ` Max Nikulin
2022-03-09 16:39 ` c.buhtz
2022-03-11 19:21 ` chris
2022-03-15 13:04 ` Max Nikulin
2022-03-10 21:49 ` Nick Dokos
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 \
* 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).