Disable line truncation

[OrangeDog]

trafficstars

All output appears to be truncated to the terminal width and replaced with e.g. ...(and 132 more) This causes vital debugging information to be lost.

It should be possible to disable this and allow the terminal to wrap itself, especially if the output is to a pipe or file.

[1m[INFO][0m:    [90m->[0m running find /home/me/project/.buildozer/android/platf...(and 102 more)[0m
[0m
           working: /home/me/project/.buildozer/android/platform/build-armeab...(and 133 more) [0m
[1m[INFO][0m:    [90m->[0m running mv /home/me/project/.buildozer/android/platfor...(and 349 more)[0m

[HyTurtle]

https://github.com/kivy/buildozer/blob/f2aefa895697d6dadf3f9ab428a4738a7f1de55c/buildozer/default.spec#L376

[OrangeDog]

@HyTurtle yes, that's the log level. That has no effect on the horizontal truncation.

[HyTurtle]

If you're sure - then would be a p4a issue rather than a buildozer one, https://github.com/kivy/python-for-android/blob/8336cea09c572c2a234ddda211226a1eb8b2ad1d/pythonforandroid/logger.py#L156 it shouldn't be shortened if log level is higher than debug

[OrangeDog]

Or buildozer has the log values the wrong way around, because debug (2) is the highest.

[HyTurtle]

Info is higher than debug (in logging hierarchy); that does seem to be a bug though - if that is where the shortening is coming from that is - misspoke a touch it shouldn't shorten if its set as debug (which probably shouldn't be the default), do you get less output setting that to info or the same?

Regardless would probably need to move to the p4a repo and can you check which branch you are using?

[OrangeDog]

Setting it to info (log_level = 1) gives significantly less output.