"While we are talking about conventions, would you mind keeping lines in your mail shorter than 79 columns to avoid wraparounds in quoted text? Unlike your proposal, that one actually _is_ a common convention..."
It is about making quote of long line and fit it to one's convention, right?
Complaining about any conventions, especially to a man, who do not understand your language, for example, is even more silly. Everything works somehow, just like kernel does, just try to complain.
Real life Linux example.
They complain about whitespace damage or coding style in sources only after the fact -- `checkpatch.pl` on all levels other than text editor for a developer. This is kind of struggle against consequences, not causes.
Fix your text editor once and for all, so any developer who uses it will not produce any crap. Yet, it's is as always: userspace sucks. Not saying about more comprehensive source processing tools, like static (security, API usage) analysis, based on pure textual annotations and basic text processing tools.
This situation even more dramatic, because they (kernel developers) use MUAs and text editors most of the development time. Do they use ad-hoc crap all those years? And kernel janitors (a priori without much clues) must clean it all the time?
(i'm too upset, as you can see, but this is a key thing)
______
fix your text editor
Even with long quoted lines, in `jed`(mail_mode) it's just Alt+q, and quotation is wrapped and prefixed as needed.
It's just as silly as 8 (C)VGA colors in *modern* text mode/terminal emulators (oh, xterm's 256 is even more silly ''design'').
_____
why?
Designs might be silly, conventions just are. Either you follow them or not.
The existence of some jed email_mode does not change the lowest common denominator.
just because it (making good quote) must be very easy
It is about making quote of long line and fit it to one's convention, right?
Complaining about any conventions, especially to a man, who do not understand your language, for example, is even more silly. Everything works somehow, just like kernel does, just try to complain.
Real life Linux example.
They complain about whitespace damage or coding style in sources only after the fact -- `checkpatch.pl` on all levels other than text editor for a developer. This is kind of struggle against consequences, not causes.
Fix your text editor once and for all, so any developer who uses it will not produce any crap. Yet, it's is as always: userspace sucks. Not saying about more comprehensive source processing tools, like static (security, API usage) analysis, based on pure textual annotations and basic text processing tools.
This situation even more dramatic, because they (kernel developers) use MUAs and text editors most of the development time. Do they use ad-hoc crap all those years? And kernel janitors (a priori without much clues) must clean it all the time?
(i'm too upset, as you can see, but this is a key thing)
______