Repository navigation
Conversation
The org reader stores #+TITLE, #+DATE and #+DESCRIPTION as document metadata, which the fragment writer never emits, so a reflow deleted them. Shield each contiguous run of org file keywords like a pragma. The org reader also gives every heading an identifier and the org writer prints each as a :PROPERTIES: drawer. Clear identifiers the source did not set with :CUSTOM_ID:, for both the FFI and the CLI reader.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
v0.11.9. Pandoc org output keeps file keywords (
#+TITLE,#+DATE,#+DESCRIPTION,#+FILETAGS) and no longer writes aCUSTOM_IDdrawer onto every heading.Version pins match
scripts/check_release_ready.sh. The conda sha256 stays until the tag exists.After merge: tag
v0.11.9on the merge commit once its CI is green, then the post-tag steps inRELEASING.md.