I experienced the same behavior as coreybeaumont, once I toggled the soft wrap option everything started wrapping either soft or hard, but I cannot utilize any options around soft wrap (preferred line length, soft wrap on/off) to return to the initial behavior of not wrapping lines.
Regardless of the oddness of this weird step function behavior where it seems like the max line length isn’t getting initialized until the soft wrap option is first toggled(and then you can’t get back to the state of not wrapping), I’m arguing that this needs to be configurable. From my read of the other issue where it was decided to do this hard coded internal maximum line length, the only vague reason against is it’ll give people crashes or performance issues that’ll come back as bugs. I think it would be much easier to provide a button that’ll spit out relevant troubleshooting information for people to submit in bugs(version, config, module versions etc) and have that understand performance and stability edges in the configuration like this (and spit out big red bold text or something) )rather than just sweeping this one under the rug of “the users are too stupid to be allowed to edit this value”.
'Wrapping, or the lack thereof, should be purely cosmetic and not affect the code or environment outside of how the text is currently displayed’
That’s more than half of what a good editor is supposed to do, display text in an easily human readable and customizable format. As a description of the issue I’m having, yes it’s purely cosmetic, but it feels like that’s minimizing the issue, as if we’re just looking for functionality in terms of accurately editing files and displaying text, we’d still be using pico/nano,vi,emacs etc; what Atom brings to the table is a highly configurable gui and contextual highlighting. I would rather have atom crash on me once a day than not be able to toggle wrapping on long lines.