Skip to main content
Bumped by Community user
Commonmark migration
Source Link

At the moment, we have these choices when providing error messages / logs:

  1. Use code-blocks

    Use code-blocks

    This preserves the formatting of the error message, though it uses spurious highlighting and disables line-wrapping (both the latter are seldom appropriate)

  2. Use code-blocks with <!-- language: none -->

    Same as #1, but at least no inappropriate highlighting.

  3. Use <pre>...</pre>

    Same as #2, but html works and thus must be escaped.

  4. Use quote-marks

    Markdown and HTML work and must be escaped, no fixed-width font and whitespace-collapsing, but at least line-wrapping works

  5. Insert as normal text

    None of the advantages of either previous option and all the drawbacks, though still popular with new users who do not know better or cannot be bothered.

This preserves the formatting of the error message, though it uses spurious highlighting and disables line-wrapping (both the latter are seldom appropriate) 2. Use code-blocks with <!-- language: none -->

Same as #1, but at least no inappropriate highlighting. 3. Use <pre>...</pre>

Same as #2, but html works and thus must be escaped. 4. Use quote-marks

Markdown and HTML work and must be escaped, no fixed-width font and whitespace-collapsing, but at least line-wrapping works 5. Insert as normal text

None of the advantages of either previous option and all the drawbacks, though still popular with new users who do not know better or cannot be bothered.

None of those is really good for logs/errors which easily get just too wide.

What I propose is introducing an alternative, which is especially appropriate for logs and error-messages:

Add something like <!-- language: log --> which makes code-blocks use no highlighting and word-wrap their lines to avoid horizontal scrolling.

This SO question shows which style would have to be applied to code-blocks marked as log: How do I wrap text in a pre tag?

At the moment, we have these choices when providing error messages / logs:

  1. Use code-blocks

This preserves the formatting of the error message, though it uses spurious highlighting and disables line-wrapping (both the latter are seldom appropriate) 2. Use code-blocks with <!-- language: none -->

Same as #1, but at least no inappropriate highlighting. 3. Use <pre>...</pre>

Same as #2, but html works and thus must be escaped. 4. Use quote-marks

Markdown and HTML work and must be escaped, no fixed-width font and whitespace-collapsing, but at least line-wrapping works 5. Insert as normal text

None of the advantages of either previous option and all the drawbacks, though still popular with new users who do not know better or cannot be bothered.

None of those is really good for logs/errors which easily get just too wide.

What I propose is introducing an alternative, which is especially appropriate for logs and error-messages:

Add something like <!-- language: log --> which makes code-blocks use no highlighting and word-wrap their lines to avoid horizontal scrolling.

This SO question shows which style would have to be applied to code-blocks marked as log: How do I wrap text in a pre tag?

At the moment, we have these choices when providing error messages / logs:

  1. Use code-blocks

    This preserves the formatting of the error message, though it uses spurious highlighting and disables line-wrapping (both the latter are seldom appropriate)

  2. Use code-blocks with <!-- language: none -->

    Same as #1, but at least no inappropriate highlighting.

  3. Use <pre>...</pre>

    Same as #2, but html works and thus must be escaped.

  4. Use quote-marks

    Markdown and HTML work and must be escaped, no fixed-width font and whitespace-collapsing, but at least line-wrapping works

  5. Insert as normal text

    None of the advantages of either previous option and all the drawbacks, though still popular with new users who do not know better or cannot be bothered.

None of those is really good for logs/errors which easily get just too wide.

What I propose is introducing an alternative, which is especially appropriate for logs and error-messages:

Add something like <!-- language: log --> which makes code-blocks use no highlighting and word-wrap their lines to avoid horizontal scrolling.

This SO question shows which style would have to be applied to code-blocks marked as log: How do I wrap text in a pre tag?

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

At the moment, we have these choices when providing error messages / logs:

  1. Use code-blocks

This preserves the formatting of the error message, though it uses spurious highlighting and disables line-wrapping (both the latter are seldom appropriate) 2. Use code-blocks with <!-- language: none -->

Same as #1, but at least no inappropriate highlighting. 3. Use <pre>...</pre>

Same as #2, but html works and thus must be escaped. 4. Use quote-marks

Markdown and HTML work and must be escaped, no fixed-width font and whitespace-collapsing, but at least line-wrapping works 5. Insert as normal text

None of the advantages of either previous option and all the drawbacks, though still popular with new users who do not know better or cannot be bothered.

None of those is really good for logs/errors which easily get just too wide.

What I propose is introducing an alternative, which is especially appropriate for logs and error-messages:

Add something like <!-- language: log --> which makes code-blocks use no highlighting and word-wrap their lines to avoid horizontal scrolling.

This SO question shows which style would have to be applied to code-blocks marked as log: How do I wrap text in a pre tag?How do I wrap text in a pre tag?

At the moment, we have these choices when providing error messages / logs:

  1. Use code-blocks

This preserves the formatting of the error message, though it uses spurious highlighting and disables line-wrapping (both the latter are seldom appropriate) 2. Use code-blocks with <!-- language: none -->

Same as #1, but at least no inappropriate highlighting. 3. Use <pre>...</pre>

Same as #2, but html works and thus must be escaped. 4. Use quote-marks

Markdown and HTML work and must be escaped, no fixed-width font and whitespace-collapsing, but at least line-wrapping works 5. Insert as normal text

None of the advantages of either previous option and all the drawbacks, though still popular with new users who do not know better or cannot be bothered.

None of those is really good for logs/errors which easily get just too wide.

What I propose is introducing an alternative, which is especially appropriate for logs and error-messages:

Add something like <!-- language: log --> which makes code-blocks use no highlighting and word-wrap their lines to avoid horizontal scrolling.

This SO question shows which style would have to be applied to code-blocks marked as log: How do I wrap text in a pre tag?

At the moment, we have these choices when providing error messages / logs:

  1. Use code-blocks

This preserves the formatting of the error message, though it uses spurious highlighting and disables line-wrapping (both the latter are seldom appropriate) 2. Use code-blocks with <!-- language: none -->

Same as #1, but at least no inappropriate highlighting. 3. Use <pre>...</pre>

Same as #2, but html works and thus must be escaped. 4. Use quote-marks

Markdown and HTML work and must be escaped, no fixed-width font and whitespace-collapsing, but at least line-wrapping works 5. Insert as normal text

None of the advantages of either previous option and all the drawbacks, though still popular with new users who do not know better or cannot be bothered.

None of those is really good for logs/errors which easily get just too wide.

What I propose is introducing an alternative, which is especially appropriate for logs and error-messages:

Add something like <!-- language: log --> which makes code-blocks use no highlighting and word-wrap their lines to avoid horizontal scrolling.

This SO question shows which style would have to be applied to code-blocks marked as log: How do I wrap text in a pre tag?

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

At the moment, we have these choices when providing error messages / logsproviding error messages / logs:

  1. Use code-blocks

This preserves the formatting of the error message, though it uses spurious highlighting and disables line-wrapping (both the latter are seldom appropriate) 2. Use code-blocks with <!-- language: none -->

Same as #1, but at least no inappropriate highlighting. 3. Use <pre>...</pre>

Same as #2, but html works and thus must be escaped. 4. Use quote-marks

Markdown and HTML work and must be escaped, no fixed-width font and whitespace-collapsing, but at least line-wrapping works 5. Insert as normal text

None of the advantages of either previous option and all the drawbacks, though still popular with new users who do not know better or cannot be bothered.

None of those is really good for logs/errors which easily get just too wide.

What I propose is introducing an alternative, which is especially appropriate for logs and error-messages:

Add something like <!-- language: log --> which makes code-blocks use no highlighting and word-wrap their lines to avoid horizontal scrolling.

This SO question shows which style would have to be applied to code-blocks marked as log: How do I wrap text in a pre tag?

At the moment, we have these choices when providing error messages / logs:

  1. Use code-blocks

This preserves the formatting of the error message, though it uses spurious highlighting and disables line-wrapping (both the latter are seldom appropriate) 2. Use code-blocks with <!-- language: none -->

Same as #1, but at least no inappropriate highlighting. 3. Use <pre>...</pre>

Same as #2, but html works and thus must be escaped. 4. Use quote-marks

Markdown and HTML work and must be escaped, no fixed-width font and whitespace-collapsing, but at least line-wrapping works 5. Insert as normal text

None of the advantages of either previous option and all the drawbacks, though still popular with new users who do not know better or cannot be bothered.

None of those is really good for logs/errors which easily get just too wide.

What I propose is introducing an alternative, which is especially appropriate for logs and error-messages:

Add something like <!-- language: log --> which makes code-blocks use no highlighting and word-wrap their lines to avoid horizontal scrolling.

This SO question shows which style would have to be applied to code-blocks marked as log: How do I wrap text in a pre tag?

At the moment, we have these choices when providing error messages / logs:

  1. Use code-blocks

This preserves the formatting of the error message, though it uses spurious highlighting and disables line-wrapping (both the latter are seldom appropriate) 2. Use code-blocks with <!-- language: none -->

Same as #1, but at least no inappropriate highlighting. 3. Use <pre>...</pre>

Same as #2, but html works and thus must be escaped. 4. Use quote-marks

Markdown and HTML work and must be escaped, no fixed-width font and whitespace-collapsing, but at least line-wrapping works 5. Insert as normal text

None of the advantages of either previous option and all the drawbacks, though still popular with new users who do not know better or cannot be bothered.

None of those is really good for logs/errors which easily get just too wide.

What I propose is introducing an alternative, which is especially appropriate for logs and error-messages:

Add something like <!-- language: log --> which makes code-blocks use no highlighting and word-wrap their lines to avoid horizontal scrolling.

This SO question shows which style would have to be applied to code-blocks marked as log: How do I wrap text in a pre tag?

corrected what <pre> does
Source Link
Deduplicator
  • 1.7k
  • 15
  • 24
Loading
edited title
Source Link
Deduplicator
  • 1.7k
  • 15
  • 24
Loading
Friday night they claimed down the beach side, towels and buckets in head. Ready as they were, they scooped up the shells, sand and buried the beached whale. In the morning they roasted the exposed fin, the heat burial cooking the rest.
Source Link
random
  • 53.3k
  • 18
  • 146
  • 227
Loading
deleted 2 characters in body; edited title
Source Link
Deduplicator
  • 1.7k
  • 15
  • 24
Loading
edited title
Link
Deduplicator
  • 1.7k
  • 15
  • 24
Loading
edited title
Link
Deduplicator
  • 1.7k
  • 15
  • 24
Loading
Source Link
Deduplicator
  • 1.7k
  • 15
  • 24
Loading