Hi,
Philip Guenther wrote on Tue, Jan 05, 2016 at 12:17:13AM -0800:
> On Mon, Jan 4, 2016 at 11:15 PM, Michal Mazurek wrote:
>> On 01:24:35, 5.01.16, Ingo Schwarze wrote:
>>> +If an output line would be broken after a non-blank character but
>>> +contains at least one blank character, break the
On Mon, Jan 4, 2016 at 11:15 PM, Michal Mazurek wrote:
> On 01:24:35, 5.01.16, Ingo Schwarze wrote:
>> +If an output line would be broken after a non-blank character but
>> +contains at least one blank character, break the line earlier,
>> +after the last blank character.
>> +This is useful to av
On 01:24:35, 5.01.16, Ingo Schwarze wrote:
> +If an output line would be broken after a non-blank character but
> +contains at least one blank character, break the line earlier,
> +after the last blank character.
> +This is useful to avoid line breaks in the middle of words, if
> +possible.
After
Hi,
Michal Mazurek wrote on Mon, Jan 04, 2016 at 08:27:50PM +0100:
> Fold line after the last blank character within the first
> .Ar width
> column positions (or bytes).
> +If a blank character does not exist within the width, then
> +a longer line will still be split at the width.
> The firs
The first diff explains what happens to a word longer than 'width'. This
diff comes from NetBSD and FreeBSD. The explanation is quite
complicated and I couldn't understand what this flag does at first, the
source code makes it much clearer (the variable is called split_words).
But I didn't change t
