Timeline for How should I paste from my terminal?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 11, 2022 at 17:05 | comment | added | NotTheDr01ds | @ArturMeinild Exactly! And good plan pointing out the multi-line approach for entering long commands like that as well in your answer. | |
| Nov 11, 2022 at 16:56 | comment | added | Artur Meinild | More users would probably have caught the error in this post, if the first quote was done in the way you suggested. I spotted it anyway, but I guess most people didn't (including the one that voted to close). 😉 | |
| Nov 10, 2022 at 21:44 | history | edited | NotTheDr01ds | CC BY-SA 4.0 |
added 1 character in body
|
| Nov 10, 2022 at 21:42 | comment | added | NotTheDr01ds | @BeastOfCaerbannog "It is not very often that you get a single-line error output" -- I have to disagree. I've seen it quite frequently across the Stack sites I frequent, which is why I've arrived at this method. Perhaps more so on Stack Overflow, where it seems to be commonly agreed that block-quotes without backticks is the best method. But do agree that it's a clearly matter of personal preference. | |
| Nov 10, 2022 at 21:34 | comment | added | BeastOfCaerbannog | It is not very often that you get a single-line error output and you didn't explicitly mentioned that your suggestion is for this case only, thus my comment. Usually error outputs span multiple lines. In a case of a long single-line error, I would leave the error output exactly as presented, without violating Nmath's rule. If I would decide to have it in multiple lines though, I would break it manually (also adding a note in the post), instead of using the method you describe in your third example. That's a matter of personal preference I guess, that's why I haven't voted your post. | |
| Nov 10, 2022 at 21:24 | comment | added | NotTheDr01ds | Also, edited to disambiguate the "code-fences". | |
| Nov 10, 2022 at 21:23 | comment | added | NotTheDr01ds | Regarding, "I would very much prefer manual line breaks of a long error output inside code fences." -- Sure, an alternative is to manually add line-breaks in a code-block, but that violates Nmath's rule to "not make any alterations to the text you just pasted." And I agree with that. It's better to paste the output exactly as it has been generated to avoid inserting any errors, but then it may be unreadable with standard code-blocks or inline. | |
| Nov 10, 2022 at 21:21 | history | edited | NotTheDr01ds | CC BY-SA 4.0 |
Changed "code-fence" to "inline" since there's disagreement on the meaning there. This is less ambigous.
|
| Nov 10, 2022 at 21:19 | comment | added | NotTheDr01ds | @BeastOfCaerbannog "Would only work for a single error line. If the error spans multiple lines, these get lost." - Yes, as I said, this is only for long single-line output. If the output has line-breaks already, then it shouldn't be needed. | |
| Nov 10, 2022 at 18:55 | comment | added | BeastOfCaerbannog | Hmmm... Your last example does not use code fences (triple backticks) but inline code formatting (single backticks). And I'm not sure I agree with this usage. I would very much prefer manual line breaks of a long error output inside code fences. The method you propose (blockquote+single backticks) would only work for a single line error. If the error spans multiple lines, these get lost. Even worse, if the error has empty lines, the code formatting completely breaks and only the quote formatting gets applied. | |
| Nov 10, 2022 at 17:33 | history | answered | NotTheDr01ds | CC BY-SA 4.0 |