Enable Markdown support in comments

Bug #1261771 reported by Lars Kellogg-Stedman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Community Project
Fix Released
Wishlist
Stefano Maffulli

Bug Description

I guess this is more of an RFE than a bug, but it seems that Markdown is not enabled for comments on ask.openstack.org. This makes it frustrating when trying to reference commands paths (`/etc/foo.cfg`) or provide named links ([this document](http://example.com/)) in comments.

Revision history for this message
Evgeny Fadeev (evgeny-fadeev) wrote :

It's possible to turn on via online settings console. When turned on, the comments box will receive the same editor as the ask/answer pages.

Revision history for this message
Stefano Maffulli (smaffulli) wrote :

Comments are not very readable in general and people already seem to use it too much instead of editing questions or even to provide answers. I don't think we should give incentives to use them.
Lars: can you give a couple of examples where a comment should include rich formatting that should not be part of a question or an answer?

Changed in openstack-community:
status: New → Opinion
Revision history for this message
Lars Kellogg-Stedman (larsks) wrote :

Sure.

I often want to provide links to documentation in comments. Telling someone to "take a look at [this document](http://some/url)]" would be a rotten answer, but makes a perfectly fine comment. This is probably the most common use, and may include providing supporting documentation to someone else's answer, or links to information to help someone transform a bad question into a good question.

Having access to `backticks` in comments is invaluable for differentiating filenames and command literals from surrounding text; doubly so since a comment is by nature a single line so one cannot use empty lines for this sort of distinction.

I think the inability to do these sort of simple things makes people (especially those familiar with the StackExchange suite of sites, which do permit Markdown in comments) occasionally throw up their hands and go elsewhere, rather than participating in the ask.o.o community and making it a better place.

Revision history for this message
Rich Bowen (rbowen) wrote :

Adding a +1 to Lars' request. This would indeed be helpful, for the reasons that Lars mentions.

Revision history for this message
Stefano Maffulli (smaffulli) wrote :

I'm convinced, thanks. I have enabled the setting so now comments accept the same editor as the answers.

Changed in openstack-community:
status: Opinion → Fix Released
importance: Undecided → Wishlist
assignee: nobody → Stefano Maffulli (smaffulli)
Revision history for this message
Arash Kaffamanesh (d-ak) wrote :

This would very helpful, I'd like to add +1 to Lars's request too.

Revision history for this message
Kashyap Chamarthy (kashyapc) wrote :

Thanks Stefano! I felt the need for it too a few times, and was frustrated by the poor formatting in comments.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.