-
-
Notifications
You must be signed in to change notification settings - Fork 69
max_line_length
property
#12
Comments
+1 |
1 similar comment
+1 |
this would help? |
After thinking a little bit about its implementation i wonder how this should be implemented? The editorconfig claims:
This means at any point in the editing process the editorconfig-plugin should insert a hard-wrap? I currently can't imagine that this might be any helpful, since it takes a additional operation (deleting the inserted newline) to fix a wrong wrap. The second question would be when should the break being introduced, at save of the document or on the fly, while editing the document? Even though i currently don't see any practical use of a hard wrap over a soft wrap, and i'd expect this rule to be detected by a linter or being done by a "smart" plugin estimating the correct position of a hard wrap i expect to implement this in a few weeks, in order to fulfill the editorconfig-specs. |
@florianb Isn't this the equivalent of setting: atom.config.set('editor.preferredLineLength', <max_line_length>)
atom.config.set('editor.softWrapAtPreferredLineLength', true) At least according to this page a soft wrap at the set value is acceptable, it looks like the other page only lists a hard wrap as acceptable though, so it seems there is some confusion there. Personally I would say the forced soft wrap is the more reasonable choice, for the difficulties and potentials to introduce confusion that you outline above for forcing an arbitrary line break at the set value. |
@Arcanemagus - thank you very much, the link is very helpful. These config-settings seem to be the responsible settings (i had them in mind, too) - i have to check how they are implemented and how we may realize a per editor-config. 🍻 |
+1 |
🎺 The implementation of |
The current implementation of |
The
max_line_length
property would be nice.The text was updated successfully, but these errors were encountered: