Fix: Don't do buffer pre-processing for file exports #590
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes #589. Add internal helper function `org-hugo--buffer-has-valid-post-subtree-p`. Clean up the `org-hugo-export-wim-to-md` docstring.
kaushalmodi
force-pushed
the
dont-preprocess-for-file-exports
branch
from
da94c0e
to
63c87ee
Compare
kaushalmodi
added a commit
that referenced
this pull request
Mar 15, 2022
Fixes this minor interactive use regression introduced in #590.
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The buffer pre-processing is needed only when exporting subtrees to resolve links that a subtree might have to another subtree in the same Org file.
File exports don't need that as the entire file scope is exported.
Fixes #589.