Skip to content
This repository

Turn functionality on and off #22

gkatsev opened this Issue January 22, 2013 · 4 comments

4 participants

Gary Katsevman Brant Bobby Darcy Parker suan
Gary Katsevman

I think it would be even better if it was possible to disable and enable the instantinaity of this plugin via a command.

:InstantMarkdownEnable     " enable instant markdown functionality
:InstantMarkdownDisable    " disable instant markdown functionality

Or something other API. Basically, after :InstantMarkdownEnable is called, it'll check to see if current file is a markdown file and then open up the instant preview and then whenever a markdown buffer is navigated to the instant preview is opened. After :InstantMarkdownDisable, the plugin should never open instant previews for markdown files.

Brant Bobby

I share my .vim/ directory across Windows and Mac/Linux systems. Since the plugin doesn't work at all on Windows (throwing errors whenever I edit a markdown file), a way to globally disable it would be essential.

Darcy Parker

I also vote for this capability. I'd like to have something like this in my .vimrc to disable vim-instant-markdown on windows.

if has("win32") || has("win64") || has("win16")

I'd also like to create a map to toggle. So an :InstantMarkdownToggle command would also be useful.

By default, I'd actually like the instant preview to be disabled. So when I open a markdown file, it doesn't always open a web page. Then if I want it on, I would run the command :InstantMarkdownToggle. The first time, it would start up the server and open the web page to preview. Then later if I :InstantMarkdownToggle, it would just stop the live preview... I am okay if the server stays up and the browser keeps the page up.

Or something like that... hope these thoughts help when deciding how to implement.

Darcy Parker

Looks like some of what I want is already implemented by #30


#30 Has been merged, and should handle everything apart from disabling the preview after it has been activated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.