2

You get 640 pixels across already. That's actually a lot if used properly. A better answer is therefore to properly trim and otherwise edit or compose the image. Of course this should be done anyway. All too often we see sloppily designed images dumped on us. These include schematics with lots of unnecessary white space, way too thin lines, etc. A ...


2

You might do it in markdown like this: [![][2]][1] [1]: http://about.keysight.com/en/newsroom/imagelibrary/library/seminarAplus_images/image003_high.jpg [2]: http://i.stack.imgur.com/DrDAP.jpg With the following result: You can also use the "add image" button in the editor, and just change the link target afterwards.


2

Just a guess, but this may be deliberate to keep the abuse of comments to a minimum. They are supposed to be comments, not answers. If you are showing code in a response, then it's a strong clue it should be a answer instead of a comment. Comments are already abused. Allowing pretty formatting would only invite more abuse. Pretty formatting shouldn't be ...


1

I think the issue is that Markdown considers any indented line to be part of the previous list item; this is a feature, not a bug. It gets indented to match the list indentation, but it doesn't get rendered in code font. A horizontal rule can fix this, and probably looks better than other options: List item Second paragraph for list item #1 List item ...


Only top voted, non community-wiki answers of a minimum length are eligible