From owner-freebsd-questions@freebsd.org Fri Jun 12 06:14:07 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CE20E32FEA4 for ; Fri, 12 Jun 2020 06:14:07 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.130]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49jr5p5hk6z41G8 for ; Fri, 12 Jun 2020 06:14:06 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([178.8.39.138]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPA (Nemesis) id 1MODeL-1jYOYt2Njd-00OTrU; Fri, 12 Jun 2020 08:14:02 +0200 Date: Fri, 12 Jun 2020 08:14:01 +0200 From: Polytropon To: Kurt Hackenberg Cc: freebsd-questions@freebsd.org Subject: Re: freebsd vs. netbsd Message-Id: <20200612081401.f5a5c95b.freebsd@edvax.de> In-Reply-To: References: <171506d5-19aa-359e-c21d-f07257c52ebd@freenetMail.de> <6a4f6a15-ec43-03f6-1a41-a109e445f026@anatoli.ws> <00225a04-237d-9051-9aea-12c192106a20@anatoli.ws> <373EDB20-C750-42E2-A41B-EA61F6E49807@kicp.uchicago.edu> <20200609120136.00005b3c@seibercom.net> <2393a1e0-b073-950a-78be-9f57d8e9934b@anatoli.ws> <20200610063555.00003707@seibercom.net> <82F57D0D-E0EC-49F7-824E-20A296C9F549@kicp.uchicago.edu> <250b853a-b436-0e99-b05c-9abd6b6019ef@panix.com> <20200611070630.2cb42786.freebsd@edvax.de> <20200611075658.1dd841a9.freebsd@edvax.de> <20200611082443.0000187a@seibercom.net> <2e6c6baf-9d87-2a02-00c3-578c6630f97f@kicp.uchicago.edu> <20200611172537.2f7cdc07@archlinux> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:a2h3iztLADKfwmqSmtBzvipxv+u1ceQSaBI+RcxSoQhgXNHM0/d 6J5RgTEd2s1YhQgSXriKc5z76zoMVg+Vc7nv2IFX1iadMPbAZ38zQ2c5Cz/H9PSfReG3kfZ DLA2G6xYbNUy6G6Lg1+BZg5UsQz3OxEDBYEnd1hatcC5Vc2cQedfoCfEuBK6wQx+2Bk5kXS Qrrrl5VL7hPbXZfLGWyxw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:aIzz0xu3K+8=:26nkWX4q2bhHC2GCvyzgx1 vphf+Ct68LmVQ7JrfnJdJc2HXhc+EJ+6cgJUZ+nxBau6Z9C7KFvZK709t+awQ7GERicO10wQg jfE7hqfKPdGLFn1n51XzV7Le44p2D+g+YKBP/PMrnInxjPlvTm3rngmy9IXD5X39mP1mWD/BL ePburXDhu1obpxqqws/dHgzy7+9zjXV1tr+W+riePeE8F4c/P4XEJKBLdWfCMwEs9blDLvfXM 7bEnhb5dWD1dFQmHqcTdbTTblhylu2QFLWKiOm+vd/UZ6uNq3ehfPWMf7Jhf9QXIFboudbTlU mqLf2PEYaOwSfAkAf85VqjwH6SwguRhDVTx6PRKjClS9kauuoOPKJOX95k1CadDbTTaX6dLNG 4SkQZxQW4Q7qOipAuLUivX1lgMUxQEveq7E7Z3yf0FK4FuNfei2OSrSts/Dl2nTHGVLh4lStT muSzW1XFzt01miSynLEmi2QxeNcQVZGbkKv7yzdNjVM1Zd9KOUi220YZWjvudfXlaJ9ELe8bf MndtXAQ+93hw+R9vl0xlgnEZaLOJtcCJeXdigZ0+YB+L9hu5TboonQX5nErXgSkeL061zRnEA bJ4iIwu0mOkOg0wAu34TZeWgJ1+Hs+OOqTnqjDOsOGc8UU5doC5Ok4OryyWkhQoOAH26ZOwhe EZQXMbFzLt+dQgUpKfOfh1dshXOQvDUREnMIKu/2QRP9gfOKr0SfOq25ryug3LZaCrNs+Aet0 olO7U9aIAd2BFpd2b5SZRo9gfoOO7sSoSing1M941/JDTONY8z9TbGU/rXLCMpt5npp6SIbgj a15BKs+7JORmianZapFzYT38swSBJmArx6GJ2FVUkcQ8sy6Af8= X-Rspamd-Queue-Id: 49jr5p5hk6z41G8 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@edvax.de has no SPF policy when checking 212.227.126.130) smtp.mailfrom=freebsd@edvax.de X-Spamd-Result: default: False [2.95 / 15.00]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; NEURAL_HAM_SHORT(-0.56)[-0.558]; RCPT_COUNT_TWO(0.00)[2]; RECEIVED_SPAMHAUS_PBL(0.00)[178.8.39.138:received]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.58)[0.581]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.53)[0.527]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[212.227.126.130:from]; R_SPF_NA(0.00)[no SPF record]; RWL_MAILSPIKE_POSSIBLE(0.00)[212.227.126.130:from]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2020 06:14:07 -0000 On Thu, 11 Jun 2020 18:42:11 -0400, Kurt Hackenberg wrote: > On 2020-06-11 11:25, Ralf Mardorf via freebsd-questions wrote: > > > There's still the issue with line wrapping. Due to the small screens of > > mobile phones and unwillingness to change the orientation of the > > phones, we suffer from the dispute of wrapping lines at around 70 or 80 > > chars vs endless lines. > Small screens, small windows on big screens, windows much wider than 80 > characters, variable-size windows. That's a real problem, and solved > cleanly, for text in some human languages, by software that > automatically fills and word-wraps text to use whatever width is available. > > But it's often done by redefining the ASCII characters carriage return > and line feed. Originally they meant, respectively, move the print head > to the left margin, and roll the paper up a line. Erm... no. The carriage return returns the _carriage_ to the first position (here: to the right), that's why it is called carriage return and not print head return. :-) On older electrical typewriters, you will see the following: +--> | | | which means exactly what you're describing: move the carriage, advance the paper. On traditional teletypes, there are distinct keys for each task, often labeled --- --- --- (three horizontal bars) for line feed, and < (chevron pointing to the left) for carriage return. With the advance of computers and video terminal units, the key symbol became | | | <---+ which describes what the _cursor_ does. Yes, I am old. ;-) > Fill-and-wrap software > often redefines the two-character sequence CRLF to mean end of > paragraph. And, of course, nothing in the text tells other software that > those characters have been redefined. And there are authors who "embed" things in paragraphs, sometimes intendedly, which leads to all this "smart logic" to collapse. In the end, you have messages with one line containing everything (including quoting prefixes). Even the best logic and heuristic approach can be fooled. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...