On Mon, 27 Feb 2017 20:33:28 +0200 Alexandru Elisei <alexandru.eli...@gmail.com> wrote:
> I was working on emerge --sync and my test repo configuration > generated several warning messages. Finding the exact location where > the warnings was generated was surprisingly difficult because the > message string was split across three lines due to the 80 character > line limit and I had to grep for different patterns until I found one > that matched part of a line. > > I propose that messages that are visible to the user never be split > across multiple lines. This is also the coding style convention used > by the linux kernel: > https://www.kernel.org/doc/html/latest/process/coding-style.html#breaking-long-lines-and-strings > > If accepted, this could go in the DEVELOPING file. > That could be pretty hard to do for all messages. Especially messages with embedded data eg: "%s is missing %s required use flag..." % ('sys-apps/foo', 'bar') I know I don't always enforce the line length for a few characters, also when clarity is more important than line length. We could also increase the max. line length to something like 120 or 130. -- Brian Dolbec <dolsen>
