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: Some starting problems
Date: Wed, 09 Mar 2022 09:41:39 +0000	[thread overview]
Message-ID: <109f0b7f9d53af31a5e1ab00c7384c58@posteo.de> (raw)
In-Reply-To: <4f18b7eac091dd14cfaf5ed10e7c63ed@posteo.de>

Some additional information.

Am 09.03.2022 09:55 schrieb c.buhtz@posteo.jp:
> 2.
> Because ox-publish is skipping "unmodified files"
> [..]
> nothing is generated anymore.

Doing this forces ox-publish to generated everything
     M: (org-publish "projectname" t)

> 3.
> [..]
> 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.
> [..]

I need to correct myself here. After forcing new generation of HTML 
content the links in the new test nodes also gone.
I am confused. I need to do further investigation here and create a 
minimal reproducible setup to find out the steps to reproduce this 
Should I then open a bug report? Do I understand 
https://orgmode.org/worg/org-issues.html correct that there is no 
"usual" bug tracker but just he mailing list where I have to post bugs?

> 4.
> ox-publish ignores newlines. Two short lines in the org-file becomes
> one line in the HTML content.

I am still not sure but it looks like that this does fix that problem.
     (setq org-export-preserve-breaks t)

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09  8:55 ox-publish: Some starting problems c.buhtz
2022-03-09  9:41 ` c.buhtz [this message]
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

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=109f0b7f9d53af31a5e1ab00c7384c58@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).