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
And both of those are important because the first prevents unicode NONBREAK-SPACE (0xA0) from being wrapped on, and the second prevents long tokens ( like URI's ) from being uselessly snapped in two.
The last one I do personally is localise
$Text::Wrap::columns = 120
Because under 80 columns I find far too restrictive for any serious amount of text.
And this ability has been clobbered by 087f3b7 , where it localises it at a scope closer than I can access.
The text was updated successfully, but these errors were encountered:
For now, I've backed out the change to force wrapping at 78 characters. I'm intending to replace the entire internal implementation though, and currently it doesn't use Text::Wrap at all. So we still should figure out a better way to handle this.
Until now I've abused the fact wrapping is implemented in terms of Text::Wrap, and coerced Text::Wrap to have some less insane defaults.
Some of those are outlined here: https://rt.cpan.org/Ticket/Display.html?id=95736
And both of those are important because the first prevents unicode
NONBREAK-SPACE
(0xA0
) from being wrapped on, and the second prevents long tokens ( like URI's ) from being uselessly snapped in two.The last one I do personally is localise
$Text::Wrap::columns = 120
Because under 80 columns I find far too restrictive for any serious amount of text.
And this ability has been clobbered by 087f3b7 , where it localises it at a scope closer than I can access.
The text was updated successfully, but these errors were encountered: