iamcco/markdown-preview.nvim

Implement a :MarkdownExport option

Open

#22 opened on Feb 28, 2019

View on GitHub
 (13 comments) (15 reactions) (0 assignees)JavaScript (5,538 stars) (246 forks)batch import
enhancementhelp wanted

Description

It would be really nice if there was a :MarkdownSave command that would save the HTML file, css/js in the current directory. Ie File > Save Page As... from the web browser.

It would be good if such a command made sure the paths were relative so that the HTML page could be opened and they would be sourced correctly.

It would be good to be able to read the files from a file:/// location.

Might also be worth having an option there to not optimize output (ie remove line feeds from source).

Contributor guide

Tech stack
javascriptnodejshtmlcss
Domain
toolingdeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Neovim plugin developmentJavaScriptNode.jsHTML/CSS basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
The issue requests a new :MarkdownExport command that saves the preview HTML with relative paths to assets, supports file:/// URLs, and optionally disables output optimization. Contributors should examine the preview generation in the server code (likely in the plugin's main JavaScript file) and ensure paths are made relative. The discussion in the comments may provide insight into desired behavior. No pull requests exist yet, so this is an open opportunity.