Subject: Re: ox-publish: Some starting problems
Date: Wed, 09 Mar 2022 16:39:46 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
thank's a lot for your help and your patience with a newbie.
Am 09.03.2022 16:32 schrieb Max Nikulin:
>> 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.
> If you insist on setq than try
> (setq org-export-with-broken-links 'mark)
> without :with-broken-links. You can get correct value using easy
> customization interface. It does not matter for
> `org-export-with-broken-links', but some custom variables have :set
> property, so the following may be generally better
> '(org-export-with-broken-links 'mark))
Do you mean that (setq org-export-with-broken-links 'mark) is the same
as :with-broken-links mark? This are just two different ways to set the
How do I know as a newbie? ;)
Why using custom-set variables here? Is there something wrong with just
>> I tried to reproduce this in a minimal example with two new nodes. But
>> for them the links are generated.
> It seems, changing project options or global variables does not lead
> to updating of the files if the sources have not modified.
I do not understand. Do you a see a solution for the problem?
> There is a known problem with id links. They may be broken if they
> lead to another file:
> inkbottle. org-id with ox-html. Sat, 14 Aug 2021 00:28:35 +0200
Great to know. Is there a way to monitor (subscribe) to the "dashboard"?
A bugtracker where I can not track a bug is not a bugtracker. :D
OK, bugs going to the mailing list. But am I allowed to attach extra
files (zip) to my mails to the mailinglist? Some bug reports need
attached files. But I learned and agree that it is rude to attach files
to a mailing list.
Back to the bug.
The bug-thread is hard for me to understand because of a lot of internal
details. What is the current essence? Currently there is no way to use
ox-publish with org-roam-v2 generated org files which use IDs as links?
But as I told sometimes the links are generated.
Btw: Also in my minimal working example I was not able to surly
reproduce the problem. Sometimes it works sometimes not. I also deleted
~/.emacs.d/org-roam.db, ~/.org-timestamps and ~/.emacs-d/.orgid-indexes
(I forget the correct name for the latter).
> org-mode is a mode, ox-publish maybe a package (actually unsure).
I thought it was a separate thing because of "(require ox-publish)".
Again: How do I as a newbie know?
> That page specifies related global variable, so you can try
> `describe-variable' C-h v with the related name.
I know that and I did. But this is waste of time when I have to do this
for each of the variable in that big list.
>> Is there a way to integrated backlinks into output?
> Do you mean something specific to org-roam?
I am not sure but maybe yes. ;)
I can do C-c n l which invokes org-roam-buffer-toogle and shows me an
extra buffer with a list of all nodes (org-files?) which are linking to
the current open node.
next prev parent reply other threads:[~2022-03-09 16:41 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
2022-03-09 15:57 ` Max Nikulin
2022-03-09 15:32 ` Max Nikulin
2022-03-09 16:39 ` c.buhtz [this message]
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).