search

wbond / package_control

The Sublime Text package manager
https://packagecontrol.io
4.8k stars 818 forks source link

Set syntax for Package Control Messages #238

Open du-song opened 12 years ago

du-song commented 12 years ago

It'll be nice to set syntax of Package Control Messages to Markdown automatically

wbond commented 12 years ago

This is a very interesting idea. I would obviously require informing package maintainers of the change, and the messages could no longer be indented by two spaces.

du-song commented 12 years ago

or you may detect syntax by /^(*\s+|===|---)/, then indent a tab (make it block quote) if it’s plain text.

On 2012-11-13, at 11:20, Will Bond notifications@github.com wrote:

This is a very interesting idea. I would obviously require informing package maintainers of the change, and the messages could no longer be indented by two spaces.

— Reply to this email directly or view it on GitHub.

Kristinita commented 8 years ago

+1.

I recently made a similar issue to the developer of plugin GitHub Issues. How he realized my request.

Thanks.

FichteFoll commented 7 years ago

Note that package control messages are indented by two sourcesspaces, which might put the markdown highlighting off, since four leading spaces designate a raw code block.

eugenesvk commented 3 years ago

Would love to see this as plain text is way too limiting for user communication Without going through the trouble of breaking all the plain text messages, would it make sense to switch to markdown so that install.md/2.0.0.md files would be properly highlighted, but then code-fence ```the contents of install.txt/2.0.0.txt files so that the whatever-spacing scheme they are using isn't tripping anything?