Timeline for answer to Min-Reprex: a less awkward name for MCVE by user247702
Current License: CC BY-SA 4.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 16, 2019 at 7:06 | comment | added | user692942 | @Barrosy I know, I'm agreeing with you. :) | |
| May 16, 2019 at 6:43 | comment | added | Barrosy | It does not make sense at all if you compare the it to the description of MCVE and the reason for it being abbreviated. @Lankymart It does not make sense because MCVE for as far as I know worked perfectly fine and like I said, why fix something that ain't broken? | |
| May 15, 2019 at 19:21 | comment | added | user692942 | @Barrosy "I mean I got to agree that at first sight when you would look at the abbreviation, it looks a bit strange and you would require to look it up to understand its meaning" - and reprex doesn't? | |
| May 15, 2019 at 8:50 | comment | added | Barrosy | I mean I got to agree that at first sight when you would look at the abbreviation, it looks a bit strange and you would require to look it up to understand its meaning, but once looked up, makes sense. Simply replacing the text with e.g. "example" with an anchor leading to the definition of MCVE would suffice. Even easier would be, adding a tool/button which could generate this automatically for an author of a given answer, question and/or comment. But why change things if those work just fine? | |
| May 15, 2019 at 7:13 | history | answered | user247702 | CC BY-SA 4.0 |