You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an example I was looking at the admc package and the deps_amd64 line is 431 characters long which in my eyes is absurd; not only do you have to scroll a lot horizontally on any device but you absolutely need wordwrap in a text editor to even see it all at a glance!
What would be a fine limit? I think 80 might be a bit too much and would cause many "unnecessary" line breaking everywhere, so maybe 100+ characters limit before lines should be wrapped with a newline, so maybe 120? 160?
Just having some character limit (for situations where it's possible to wrap with newlines) which everything follows would be great to have for the sake of readability :)
The text was updated successfully, but these errors were encountered:
There is no reason. These scripts are parsed by https://github.com/mvdan/sh. I agree. These massive arrays can and should be wrapped to separate lines.
I don't see a problem if the line fits on one screen without scrolling, after all the main purpose is to install the package, not to watch the code. Besides, if someone wants to make changes, no one bothers him, the form is absolutely not important to me, the essence is important.
As an example I was looking at the
admc
package and thedeps_amd64
line is 431 characters long which in my eyes is absurd; not only do you have to scroll a lot horizontally on any device but you absolutely need wordwrap in a text editor to even see it all at a glance!What would be a fine limit? I think 80 might be a bit too much and would cause many "unnecessary" line breaking everywhere, so maybe 100+ characters limit before lines should be wrapped with a newline, so maybe 120? 160?
Just having some character limit (for situations where it's possible to wrap with newlines) which everything follows would be great to have for the sake of readability :)
The text was updated successfully, but these errors were encountered: