"Blacklist" directives which are not in docutils?

[rduivenvoorde]

Hi, thanks for the plugin!

I'm trying it out to check if I can make it easier for people to write some documentation (written for Sphinx in rst)..
Looks promissing!

Opening one of the rst files I get an error about the 'toctree' Sphinx directive... :

If I'm right the issue here is that this is a sphinx directive and not a docutils directive?
Which is reasonable.
So I'm coining the idea here to have some list of directives to be ignored during parsing. So the plugin should "preflight" the text and remove the directives that are on that 'blacklist'.
Not sure if this is easy to do, or there are other ways to do this? Is there something like that in docutils maybe?

In the Preview-window one could either ignore it and show nothing, OR add some small message "ignored directive" or so?

[bittner]

The plugin is simply running a conversion to HTML. Hence, if anything goes wrong in the conversion this typically produces output in HTML that looks like above in your screenshot.

I'm not sure if it makes sense to hold a blacklist of directives. I think the conversion topic is too complex. However, I agree this could be made more robust.

Currently, any result is directly stored in the html variable and then used to update the HTML view. This is obviously "wrong" or at least "too simple".

It would be nice to keep the content in the last working state (not always trivial; what if the very first compile of the source file fails when opening the document?) and show an appropriate, helpful error message in the status bar or footer of the editor window. In this context it would also be helpful to know whether publish_parts can yield some error status or something similar.

Do you happen to know? A PR is always welcome!