Added AsciiDoc backend #15
No reviewers
Labels
No Label
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: tec/org-pandoc-import#15
Loading…
Reference in New Issue
No description provided.
Delete Branch "declantsien/asciidoc"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
See Convert documents from AsciiDoc to Org . Need some extra effort to work.
Might be a good idea to include this.
At a glance this looks reasonable, you'll want to add
org-pandoc-export-to-asciidoc
here though:d3cd2b0519/org-pandoc-import-transient.el (L37-L39)
I wouldn't try to edit asciidoc source files from the Internets. It's properly result in some formatting changes.
I use this primarily to read files in Org mode, since I am more comfortable with it.
But still it's a valid use case for asciidoc files which are produced using
ox-pandoc
though. Made the change.Also
org-pandoc-import-transient-mode
is buggy. Reported it here #16Thanks for that.
Looking at the updated PR, I'm a tad wary though about
.txt
being dedicated as an asciidoc extension, since its use is far more general.I added it cause it's used by
ox-pandoc
andorg-asciidoc
. I wouldn't worry too much about it.Currently there is only on backend associated with
txt
. Later if there are mroe backends providetxt
, maybe we can add a prompt fororg-pandoc-import-[as,to]-org
to choose which backend to use?Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Forgejo.