Custom pandoc export command
Open
Nobody has claimed this yet.
:unicorn: feature request
🔭 area/ui
- Dominant language
- TypeScript
- Stars
- 61.6k
- Forks
- 4.6k
- Avg merge
- 23h 49m
- Merged PRs (30d)
- 89
Description
Describe your feature request
I would like having a setting for custom export tasks that call a user-provided pandoc command, instead of using the export menu.
What problem does this feature solve? [optional]
- Allows to export to pandoc-supported formats without adding specific menu items
- Allows to reuse custom pandoc export commands used in other contexts
- Allows specifying a pdf engine in pandoc in case the default one causes problems
Additional context [optional]
- Abricotine does this by the way of having a "tasks" array in their settings.json file in which one can specify tasks with a given title and command, with %inputFilepath% and %outputFilepath% as variables that get replaced with the input and output filenames
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no MarkText files, tests, or entry points. Start by locating the export menu and settings handling, then compare them with the proposed tasks array and filepath placeholders; done means users can configure and run custom pandoc export commands without separate menu items.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100