**** BEGIN LOGGING AT Sun Jun 04 03:00:02 2017 Jun 04 04:10:00 Fringe theme is an interesting one. Besides being blue, instead of yellow, it has different transitions, and even different size of thumbnails in window-switcher? Will see how it looks after reboot, because currently there may be bits and pieces of previous theme. Jun 04 04:34:05 Also, is it Modest or something else that decides, when replying to an email, split paragraph into short lines, each of them prefixed with '>' ? I don't mind the '>', but I would prefer to have only one such symbol per paragraph. Given differing screen sizes, it makes no sense to split paragraph into short lines. Jun 04 04:41:39 Albeit, I have an unusually long email on my hands, courtesy of Turnitin. Jun 04 11:22:39 I still don't understand why left-right (aka previous-next) scroll gestures don't work in Photos. I think they worked fine ... before Fringe theme was installed. Jun 04 12:08:59 ((I don't mind the '>', but I would prefer to have only one such symbol per paragraph)) this is a standard that goes like "no line longer 72(?) chars, then a cr/newline. And in a quote ("XY wrote:...") each line starts with one ">" for each level of quote nesting Jun 04 12:09:35 this "standard" is like 20 or more years old Jun 04 12:15:19 https://www.ietf.org/rfc/rfc3676.txt page9 "Quoting" - first hit I ran into Jun 04 12:18:02 >> All lines of a paragraph MUST be unquoted, or else they MUST all be quoted and have the same quote depth << Jun 04 12:19:18 it's arguable if nowadays all clients obey the even older line length (72?) maximum Jun 04 12:25:21 they *SHOULD* (~2119), by using flowed lines (" CR LF") after each 72(?) chars incl quote (">>> ") Jun 04 12:25:27 ~2119 Jun 04 12:25:27 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Jun 04 12:27:35 to answer wikiwide's question: yes it's modest that is responsible to implement RFC3676 Jun 04 12:28:55 note how modest also is responsible to reformat flowed quoted lines according to screen width Jun 04 12:30:19 that's the whole purpose of flowed lines, and one of the major objectives of RFC3676 Jun 04 12:32:30 in times of HTML emails (what a bullshit idea, they all still end in spam here, unless they are multipart/alternative with plaintext) it seems it's getting less popular to support plaintext properly and taking care about stuff like the above explained Jun 04 12:39:09 see "3.1. Paragraph Text" in https://www.ietf.org/rfc/rfc2646.txt (dated 1999) for flowed text and paragraphs Jun 04 12:50:27 in former days programs (now apps) took pride in supporting RFCs and they listed on sales package all the specific RFCs they obeyed. Now developers don't even know what's a IETF-RFC Jun 04 13:03:46 on a sidenote: even some wiki markup languages adopted flowed text concept, ending lines with a " cr" instead a plain cr to make a difference Jun 04 23:49:24 Dust... Does Modest have a limit on Draft-message length somewhere? Number of lines or something? Because I have the unfortunate task of forwarding a very long email, and editing it before clicking 'Send' (removing personal information from text), which means going through all the text (and I remove excessive > breaklines on the way, too, given how they make paragraphs less readable). **** ENDING LOGGING AT Mon Jun 05 03:00:01 2017