Unfortunately, this is an ambiguity in the Markdown specification. This markdown source:
42. list item
can mean two things. One of them is the one you're expecting: more text is following a blank line and indented by four spaces, making it a top-level (i.e. not part of the list) code block.
The second possible meaning is this:
List items ...
This would be awesome.
I think it should function something like the current flag system with reasons. The "to do" flags would go into a personal queue. Some examples:
Questions could be flagged to answer
Answers could be flagged to edit
Answers could be flagged to change vote if edited/corrected
The flag queue could function much like moderators handle ...
This could easily be fixed by using a max-width: 100% on images rather than the current 640px.
Is there any specific reason why they opted to use an exact pixel size instead? If they're not going to change it, I might just add this style to my custom user styles because I think it actually makes the display of images better overall.
The workaround which is to add 8 spaces instead of simply 4 is actually written in the markdown editing help:
Preformatted text in a list item:
Skip a line and indent eight spaces.
That's four spaces for the list
and four to trigger the code block.
I needed this kind of numbering the list items, so that's how I solved it:
* 1\. item
* 1.1\. item
* 1.2\. item
* 2\. item
and the result:
I know how it looks but I really needed this kind of numbering and presented solutions ware not what I was looking for.
The current parser is unlikely to get any incremental new features like paren-delimited list numbering. Rather than updating the current parser to add a new feature here or there and risking repeatedly breaking things, SE is planning to switch to the CommonMark standard all at once, eventually:
Regarding the question "will it break too many posts?", what ...
This is fixed in the next build (client-side change, server-side change).
Tim Stone's analysis is absolutely correct. The problem (once again) was this Markdown behavior:
If list items are separated by blank lines, Markdown will wrap the items in <p> tags in the HTML output.
So you have this:
You simply need to indent those code lines a bit (8 spaces) more:
// code here, 8 spaces
element 3, this has subelements
sub element 1
sub element 2 this one has a code block
#!Shell, 12 spaces
line of code 1
line of code 2
line of code 3
And four more for here:
# a whole bunch of spaces
sub element 3
You can't. Markdown sucks like that. The best you can do is circumvent the auto-numbering functionality by putting a backslash before the periods (and also tossing in some line-ending spaces to get newlines without new paragraphs):
1\. You could get a cat
2\. Or you could get a dog
Or some less legal options
3\. A tiger
4\. A bald eagle
And of ...
If you want to start a list item with a block of code, rather than text, you need to add at least a space character after the bullet or number, then make two line breaks before starting to indent the code block with 8 spaces.
In the following examples, line breaks are denoted by the ↵ symbol.
I have never seen anyone use parentheses to avoid a numbered list. It's always been the case that the author intends to create a numbered list of some kind.
Now, if HTML and CSS are incapable of producing a list with parentheses, then by all means use dots. But I'm getting a little tired of editing questions that use parentheses.
We have talked about this internally a number of times. It is the consensus that once you add enough of any particular item to a section in your profile, ordering them can be somewhat cumbersome. Here are some ideas we have come up with and why we have repeatedly thrown them out:
Exactly what you have shown
In this case, there are too many buttons to ...
I wouldn't have a problem with the second example in your question (at least the first part of it). It has a definitive answer, and that short list is never going to change. This is rarely the case for technology "list of X" questions on Stack Overflow and several related SE sites.
Note: If you removed the second part of the question ("and were they as ...
You have to consider this in terms of element hierarchy. Inside your second list item, your full content is as follows:
`[b i g]`
That entire block of text has to be rendered through Markdown before it can be placed back inside the parent list item as completed HTML. In markdown, a line-break below a line of text will start a new paragraph. So the ...
Eh. Using plain HTML within posts is mostly supported, but not really encouraged - especially not when there are Markdown equivalents. If you choose to use HTML instead anyway, it's on you to make sure it's actually correct.
In other words, "garbage in, garbage out" is the expected behaviour here.
The reason these questions are closed network-wide across all Stack Exchange sites is that questions that attract/demand a "big list" of answers are not a good fit for the Q&A format that we follow.
Thus, it's hard to imagine how we could utilize a "Stack Exchange-like interface" to support these types of questions and answers. Trying to fit everything ...
This has been fixed. Now, the numbering follows from the first item in the list. If the first item in your list is 42, the numbering will follow from that. If the next item in your list is 1037, it will still show up as 43. So the first number in your numbered list is now respected; the others still aren’t.
This is a demonstration list.
This item is ...
As mentioned in the comments, the issue here is the malformed HTML produced by the blockquote-in-list syntax used in the original post. This happens when the parser considers the content of the list item to be inline and doesn't run the inner content through the block gamut, leaving the > ... to be matched by the top-level blockquote parser.
I see a lot of users trying to post item lists using Alpha characters instead of Numerals. like
like they were choices. I think that it would be a good idea to include these in the formatting. We already have the option of using either numbers or bullets but I think that all sites could definitely benefit from also ...
If questions are closed
If questions are negative (downvoted)
Not possible with the search. You can search for score ≥ 0 or any positive integer. You might be able to write a feature request to have that changed, although I honestly don't ...
The problem with your examples aren't that they're list questions, it's that their answers are primarily someone's opinion.
That's the problem that list questions produce: From an objective standpoint, all answers are equally valid. More over, each answer is filled with a subjective answer that is supported primarily by opinion.
Example of objectively ...