Timeline for How to overcome "Edits must be at least 6 characters"
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2023 at 0:36 | comment | added | OOPS Studio | Also, "There is a general consensus that single-character errors in sentences are highly unlikely to matter." And this is according to who? From what I can see, the "general consensus" is that every single person in this thread disagrees with this statement. Is there really such a small difference between "closest positioned" and "closest, positioned" ? | |
| Apr 10, 2023 at 0:33 | comment | added | OOPS Studio | Is it just me or is it laughable that this post is recommending people create and delete 400 answers rather than make one single-character edit? Or is it meant to be satire and I'm just missing the joke? "To avoid the inconvenience of having to review a single-character edit, why don't you just type a 300-character answer instead and then monitor this post so you can come back and delete it when it's no longer relevant? Isn't that much simpler?" | |
| Dec 9, 2020 at 0:20 | comment | added | benjimin | A single character can break code, can make a math formula wrong, can misspell a word (sometimes changing its meaning), and can break formatting. Even if that character is whitespace. We should encourage such critically-important small edits while discouraging weakly-motivated extensive edits. (Nobody likes seeing their own contributions substantially rephrased for no real reason.) What if the reviewer overlooks the small change and objects to the superfluous changes that must be bundled with it? | |
| Jun 3, 2016 at 12:12 | comment | added | Alan Macdonald | @KateGregory in my rage at the 6 character edit rule I never read what you were saying properly. I understand now thanks. | |
| Jun 3, 2016 at 12:01 | comment | added | Kate Gregory | a file path is not a sentence. It's more like code, @AlanMacdonald. Other than typing now/not in "this is now possible" words in sentences tend to be pretty typo proof. | |
| Jun 3, 2016 at 10:06 | comment | added | Alan Macdonald | "there is a general consensus that single-character errors in sentences are highly unlikely to matter", have you got a source for that claim on consensus? I've just ended up here because someone's answer included a file path with a missing backslash somewhere in the middle of the long path that took me time to figure out the right place. And so it will for the next person. | |
| Jan 29, 2015 at 18:52 | comment | added | endolith | @codetaku: Can you show an example? Flag them as "not an answer". | |
| Jul 28, 2014 at 17:57 | comment | added | codetaku | But then there are the idiots who get upvotes for /answers/, rather than comments, that achieve nothing other than pointing out the typo. How do we mark those as obsolete? | |
| Nov 23, 2012 at 2:22 | comment | added | endolith | @KateGregory: That's why you can flag comments as "obsolete" and have them removed. One of the big things that makes Stack Exchange better than forums is that you don't need to wade through pages of discussion to get the information you need. Users have a discussion about some point in an answer, the outcome of the discussion is edited back into the answer, and then the obsolete discussion is deleted. Distill out the important content and delete the chaff. | |
| Jun 9, 2011 at 20:18 | comment | added | Kate Gregory | @Grace - Thanks. I still feel people who edit typos out of the code in their questions should, if there are answers or comments referring to the typo, add explanatory text identifying the typo as a red herring. | |
| Jun 9, 2011 at 18:06 | comment | added | Grace Note StaffMod | If it's your own question, then there is no 6 character limit. | |
| Jun 9, 2011 at 18:03 | history | edited | Kate Gregory | CC BY-SA 3.0 |
added 239 characters in body; added 1 characters in body
|
| Jun 9, 2011 at 17:27 | history | post merged (destination) | |||
| Jun 8, 2011 at 15:28 | history | answered | Kate Gregory | CC BY-SA 3.0 |