public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Macek <david.macek.0@gmail.com>
To: cygwin@cygwin.com
Subject: Re: format=flowed issues [Was: gawk 4.1.4: CR separate char for CRLF files]
Date: Fri, 11 Aug 2017 07:15:00 -0000	[thread overview]
Message-ID: <e22bad8c-f17f-d9f7-baa3-e64392238fa5@gmail.com> (raw)
In-Reply-To: <598cf369.c534ca0a.c1f7.9f20@mx.google.com>

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]

On 11. 8. 2017 1:59, Steven Penny wrote:
> On Thu, 10 Aug 2017 16:48:47, Brian Inglis wrote:
>> Many archives and sites display lines off the right margin instead of allowing
>> them to wrap as normal in HTML. Possibly using pre format style without
>> horizontal scrollbars instead of just specifying a monospace font style. That
>> makes it a site or converter design issue!
> 
> Nope. Wrong. David has been doing this for over 2 years:
> 
> http://cygwin.com/ml/cygwin/2015-01/msg00232.html
> 
> So it is a user issue. The user must hard wrap because Cygwin site does not.

"""
Nope. Wrong. Cygwin site has been doing this for over 2 years:

http://cygwin.com/ml/cygwin/2015-01/msg00232.html

So it is a site issue. The site must wrap because David does not.
"""

In other words, why do you think your argument is correct?  Format=flowed is
not a new thing<https://www.ietf.org/rfc/rfc2646.txt> and it would be nice
if the archives site could display it correctly.  I can cooperate on this
with the maintainer(s) if they're interested.  Essentially, one line of CSS
should fix it, judging by my quick test.

-- 
David Macek


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3715 bytes --]

  reply	other threads:[~2017-08-11  7:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 23:16 gawk 4.1.4: CR separate char for CRLF files Jannick
2017-08-08 23:23 ` Steven Penny
2017-08-09  0:49   ` Jannick
2017-08-09  7:03     ` AW: " Roger Krebs
2017-08-09  8:38       ` Jannick
2017-08-09 11:03         ` Eric Blake
2017-08-09 19:09           ` Eric Blake
2017-08-10 12:04             ` cyg Simple
2017-08-10 12:31               ` David Macek
2017-08-10 14:46                 ` cyg Simple
2017-08-10 18:35                   ` Steven Penny
2017-08-10 21:34                     ` Brian Inglis
2017-08-10 21:49                       ` cyg Simple
2017-08-10 22:49                         ` Brian Inglis
2017-08-11 12:47                           ` cyg Simple
2017-08-11 16:54                             ` Brian Inglis
2017-08-11 17:06                               ` cyg Simple
2017-08-10 22:22                       ` Steven Penny
2017-08-10 22:49                         ` Brian Inglis
2017-08-10 23:59                           ` Steven Penny
2017-08-11  7:15                             ` David Macek [this message]
2017-08-11 13:25                               ` format=flowed issues [Was: gawk 4.1.4: CR separate char for CRLF files] Corinna Vinschen
2017-08-11 16:51                                 ` Brian Inglis
2017-09-19  2:32                                 ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e22bad8c-f17f-d9f7-baa3-e64392238fa5@gmail.com \
    --to=david.macek.0@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).