-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow exporting with broken links if broken-links: t
#587
Comments
The issue stems from the fact that the broken link errors are not masked using the broken_links:t option when pre-processing the buffer. See #447 (comment) |
Update: This workaround is not needed any more; fixed in #596. @Codeberg-AsGithubAlternative-buhtz This is not a proper fix. Please undo the following workaround once this issue is fixed. For now, I think that if you set this internal variable to nil, this issue can be bypassed. Put this in your emacs config: (with-eval-after-load 'ox-hugo
(setq org-hugo--preprocess-buffer nil)) |
That is the reproducing org-file :PROPERTIES:
:ID: 0ee70e23-8aec-44a6-abd1-8ed1935b58e8
:END:
#+title: SSH-key for Codeberg.org
+date: [2022-02-05 Sa 22:02]
#+filetags: Wiki
* Ziel
SSH-Key for Codeberg.org erstellen, um ohne Passwort [[roam:git]] nutzen zu können.
Hinweis: Jede Maschine sollte einen eigenen Key haben. From the first view it looks like that the workaround with (use-package ox-hugo
:config
(setq org-hugo-base-dir "~/tab-cloud/my.org-html")
(setq org-hugo--preprocess-buffer nil)
)
Everything is exported (over 100 files) and the last message is "Done!".
I did not understand that comment. I do not know |
They are Org built-in exporters. But that's alright, given that that workaround worked, this issue is definitely in ox-hugo. |
Unrelated: I think you are missing a
|
IMHO I do not. Some orgroam folks told me that this is editors decision if someone use |
I have personally never used or seen keywords begin with a plain See the Org manual: https://orgmode.org/manual/In_002dbuffer-Settings.html
If you see this again, I think you should report that issue. I am actually surprised if the keywords starting with just "+" are even getting parsed for you. |
Add a broken link test. Fixes #587
Add a broken link test. Fixes #587
@Codeberg-AsGithubAlternative-buhtz If you don't do subtree-based export (which I believe would be the case if you have only org-roam files), this issue is fixed for you indirectly by the nature of fixing #589. I'll leave this issue open until it truly gets fixed. |
You can remove this workaround now. |
Buffer pre-processing is enabled by default when doing subtree exports. Ref: #587 This doesn't entirely fix this issue. Broken link exports now work only if `#+options: broken-links:t` is set globally. Still `:EXPORT_OPTIONS: broken-links:t` doesn't work.. wip
Buffer pre-processing is enabled by default when doing subtree exports. Ref: #587 This doesn't entirely fix this issue. Broken link exports now work only if `#+options: broken-links:t` is set globally. Still `:EXPORT_OPTIONS: broken-links:t` doesn't work.. wip
broken_links: t
broken-links: t
…ons-parsing Fix broken links export options parsing. Fixes #587.
Status
broken-links:t
setting when set using global keyword#+options:
- Fixed in Respect thebroken-links:t
option during the buffer pre-processing as well #588broken-links:t
setting when set using heading properties:EXPORT_OPTIONS:
--TBD Gated by this possible bug in upstream- Fixed in Fix broken links export options parsing #596.ox-el
Discussed in #586
Originally posted by Codeberg-AsGithubAlternative-buhtz March 12, 2022
Hello I am getting the message
Unable to resolve link; aborting: "roam:git"
when usingorg-hugo-export-wim-to-md
. See the full debug output at the end.In the context of org-roam especially when used for Zettelkasten it is usual to have dead links. A dead link is not an error just an information because it will remind you that there is something to do ("thinking further").
From
ox-publish
I know the variable(setq org-export-with-broken-links t)
. It seems to me that this is not relevant forox-hugo
, correct?I did
M-x customize-group RET ox-hugo
but couldn't see an option like that there.Can ox-hugo export such links? It could just replace them with the string
ERROR
or whatever it wants. But it shouldn't stop the export process.The text was updated successfully, but these errors were encountered: