You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Supporting all of Sphinx's extensions may also get unwieldy pretty fast, especially with reserved keyword shortcuts for each. Perhaps this plugin can suggest an auto-completion when .. m (for example) has been typed. Also, if this method were used for all explicit markup constructs (like .. note::, .. danger::, etc.), there would be less conflict with the built-in word autocompletion provided by Sublime Text.
An example of the conflict I'm talking about:
If I want to write "admonition", and have typed it before, I could type:
admon<TAB>
but if I wanted the explicit markup construct, I could type:
.. ad<TAB>
Feel free to disagree with me; there are a lot of Sphinx extensions, it seems. (built-in extensions are listed and documented here)
The text was updated successfully, but these errors were encountered:
This plugin supports the main admonitions and things of the form:
that are defined in docutils documentation, but could it also support others e.g. the ones defined by Sphinx here or plugins for Sphinx like the mathjax/pngmath plugin that uses the syntax:
Supporting all of Sphinx's extensions may also get unwieldy pretty fast, especially with reserved keyword shortcuts for each. Perhaps this plugin can suggest an auto-completion when
.. m
(for example) has been typed. Also, if this method were used for all explicit markup constructs (like.. note::
,.. danger::
, etc.), there would be less conflict with the built-in word autocompletion provided by Sublime Text.An example of the conflict I'm talking about:
If I want to write "admonition", and have typed it before, I could type:
but if I wanted the explicit markup construct, I could type:
Feel free to disagree with me; there are a lot of Sphinx extensions, it seems. (built-in extensions are listed and documented here)
The text was updated successfully, but these errors were encountered: