On Saturday 9 July 2005 18:54, Urs Janßen wrote: > I don't think readers should break !format=flowed long lines between > words (and format=flowed messages shouldn't have long lines).
Oh, I didn't realise there was this format=flowed thing. I studied RFC 2646 and am now better aware of the subject. My original wish seems more or less pointless now :) I just point that... > - - and breakin long lines in between words is not what I would expect > from a pager (e.g. more(1) and less(1) don't work that way). ...pagers are a different thing. They are used to display all kinds of text files. Newsreaders (almost) always display human languages and therefore it makes sense to break between words when window is not wide enough to show the whole line. But yes.. if format=flowed messages are generated correctly there aren't any lines exceeding 79 characters. There is a small issue related to this though. tin generates a warning when a line in a composed message exceeds 78 characters. It's good feature but actually it counts bytes not characters. I use UTF-8 locale and messages often contain multibyte characters. Even when I save my message with no longer lines than 72 characters I get this warning from lines which contain enough multibyte characters to exceed the limit of 78 bytes per line. I want to thank you and the team for this great newsreader! I think no other readers come even close in usability and speed. - TL
