Hello,
this is a question about answers.splunk.com. Whenever I ask a question or write an answer, I try to format everything nicely with the help of the preview. That is, I insert links with [link text][1]
and [1]: http://adress
some lines below the text, and I surround code with grave accents (code
). But in the answer that is then posted, the links don't work like in this question:
http://answers.splunk.com/answers/221370/splunk6-group-visualization-elements-horizontally.html
and the code is sometimes messed up like in this question:
http://answers.splunk.com/answers/221730/layout-in-html-why-do-my-charts-resize-to-50.html
Furthermore, the code between grave accents has been lost completely, as in the first question above - before my edit that is, for those who can see revisions.
Am I doing something wrong, or is this something I can prevent? I would find it very helpful if the preview was a true preview of how the actual post looked later.
Thanks
Hi Johannes -
Thanks for your feedback. Indeed I can see that preview is different from your actual message. Let me take it offline and follow up with the team for a fix.
If you have any questions, happy to answer them - email op at splunk.com.
Hi Johannes -
Thanks for your feedback. Indeed I can see that preview is different from your actual message. Let me take it offline and follow up with the team for a fix.
If you have any questions, happy to answer them - email op at splunk.com.
Great, I can confirm that the links now work in the answers as they do in the preview, thanks!
Also, by now I figured out how and when to use the two methods to include code in a post (I think): an empty line and four space indentation for anything that contains formatting or angled brackets, and two grave accents to surround simpler code or keywords. If this is generally the right way to do it, maybe it would be a good idea to display this info somewhere for new users when they first use the "code" button, or something like they do on Stack Overflow to show you the way it's supposed to be done?