Timeline for Double backslashes disappear from code
Current License: CC BY-SA 3.0
15 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 18, 2017 at 11:55 | comment | added | LCarvalho | @NickCraver Was your profile inspired by this image? | |
Jun 18, 2017 at 1:12 | comment | added | Nick Craver Mod | @ShreevatsaR We're not refusing to fix anything, we just haven't had the time to get to this. My team is responsible for many things and this is one of a sea of them. I also get pinged at a minimum of dozens of times a day across the network and chat...I don't get to every message (there aren't enough hours in the day). I'm really glad the community is stepping up here, but I'd be lying if I said I'll have time to assist in the near future. There's a lot in progress and all of it higher priority - that's the no-BS status of things at the moment. | |
Jun 18, 2017 at 0:48 | comment | added | ShreevatsaR | @NickCraver BTW, I hope you have noticed that because you refused to fix it automatically, members of the community have been manually going through thousands of post and editing them: tex.meta.stackexchange.com/questions/7317/… -- this is thankless work and I've seen such volunteer efforts lead to burnout in other communities. | |
May 27, 2017 at 10:20 | comment | added | egreg | @NickCraver Can we hope for the queue to be activated? | |
May 11, 2017 at 15:23 | comment | added | Werner Mod |
@NickCraver: Just like the \\ -gone-missing, this Unicode character shows it's presence from the first post. I doubt I've seen that before, so just wonder whether this is related.
|
|
May 11, 2017 at 15:17 | comment | added | Paulo Cereda | @NickCraver: Please, please, take a look at this: chat.stackexchange.com/transcript/message/37326048#37326048 Looks like a DB collation error. | |
Apr 26, 2017 at 15:14 | comment | added | barbara beeton | @DavidCarlisle -- although there are probably some places where the code legitimately has a backslash followed by multiple spaces, i think your proposed automatic fix, with "quick review", is feasible and a good idea. there are also some instances of backslash + tab + lost line ending, though many fewer than the four-space instances. (tab apparently works nicely as a substitute for four spaces to identify code. sigh.) | |
Apr 26, 2017 at 13:52 | comment | added | David Carlisle | .. Especially if you could put any affected documents in a review queue for quick review by volunteers after an automated fix. (egreg's "fix button" suggestion would also work, either way is quicker than actually making the replacement in the existing browser edit interface, or copying the text to emacs, fixing and copying back. | |
Apr 26, 2017 at 13:52 | comment | added | David Carlisle | The special review list would be helpful but data.stackexchange.com/tex/revision/646030/806504/corruption suggests there are still thousands of these so it will take a while in the web interface. In practice the likelihood of a single backslash followed by four spaces is so small for TeX code that I think you do in fact have the data to fix this in the back end. If you changed all single backslash followed by four spaces to double backslash newline four spaces, it is theoretically possible that you corrupt a couple of answers but you will have fixed over 6000, so a net win. .. | |
Apr 26, 2017 at 13:15 | comment | added | egreg | Thanks, I appended some details to the question | |
Apr 26, 2017 at 12:46 | comment | added | barbara beeton | thank you for doing the research and 'fessing up. | |
Apr 26, 2017 at 12:44 | comment | added | barbara beeton | to echo @egreg, that would be very appealing! we've found another condition that resulted in corrupted code, and i think it's mentioned in a comment somewhere on this page. so we can come up with some additional patterns to search, to populate your database. and not bumping would be really beneficial. some of us will be at the tex users group meeting next week, and i can probably conscript some (reasonably willing) volunteers. | |
Apr 26, 2017 at 12:42 | comment | added | Nick Craver Mod | @egreg That's a perfectly valid requirement - adding that to the discussion list, we should be able to do that. | |
Apr 26, 2017 at 12:39 | comment | added | egreg | The option is appealing! Would it be possible that edits to those posts aren't bumped to the top page? | |
Apr 26, 2017 at 12:36 | history | answered | Nick CraverMod | CC BY-SA 3.0 |