LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   typo in /etc/networks (https://www.linuxquestions.org/questions/slackware-14/typo-in-etc-networks-4175694034/)

tauon 04-21-2021 08:08 AM

typo in /etc/networks
 
Hello slackers,

just a minor issue (someone might think this is not an issue at all):

Code:

--- /etc/networks        2021-04-15 13:12:38.018986412 +0200
+++ /etc/networks.new        1999-10-07 07:21:02.000000000 +0200
@@ -1,6 +1,6 @@
 #
 # networks        This file describes a number of netname-to-address
-#                mappings for the TCP/IP subsystem. It is mostly
+#                mappings for the TCP/IP subsystem.  It is mostly
 #                used at boot time, when no name servers are running.

The new version has an extra space in front of "It".

enine 04-21-2021 08:30 AM

Hah, have the double space habit too, despite not ever having a formal typing class I learned somewhere that with typewriters your supposed to double space before the start of a new sentence and started doing that in the 80's and am still trying to break that habit today myself. I guess someone else did too.

drumz 04-21-2021 10:09 AM

Two spaces after a period is the One True Way. For American (US) English, that is - and that's the only English that matters, right? ;)

tauon 04-21-2021 10:11 AM

Quote:

Originally Posted by enine (Post 6243356)
Hah, have the double space habit too, despite not ever having a formal typing class I learned somewhere that with typewriters your supposed to double space before the start of a new sentence and started doing that in the 80's and am still trying to break that habit today myself. I guess someone else did too.

I wanted to find a story about a very long commit message of ~20 lines with a single character diff (changing one UTF-8 symbol which looks like white space to actual white space), but my google skills aren't good in this.

tauon 04-21-2021 10:16 AM

Quote:

Originally Posted by drumz (Post 6243386)
Two spaces after a period is the One True Way. For American (US) English, that is - and that's the only English that matters, right? ;)

God Save The Queen^W^WPat.

Jan K. 04-21-2021 12:13 PM

What is this about?


"someone might think this is not an issue at all"

Count me in. Way above my head...

allend 04-21-2021 12:21 PM

Needing to save a byte is a very old habit. :)

PS - Actually testing Firefox 88.0 on my 32-bit install. Please ignore.

enine 04-21-2021 12:26 PM

Quote:

Originally Posted by drumz (Post 6243386)
Two spaces after a period is the One True Way. For American (US) English, that is - and that's the only English that matters, right? ;)

Apparently that was the old way, back when we ran Slackware negative14.1 on the IBM Selectric.

tadgy 04-21-2021 12:46 PM

That was most probably a correction on my part when I modified netconfig during the rc.inet1 update - I can't see a period and single space without correcting it to proper English (read: British) typing standards :)

bassmadrigal 04-21-2021 01:00 PM

Quote:

Originally Posted by drumz (Post 6243386)
Two spaces after a period is the One True Way. For American (US) English, that is - and that's the only English that matters, right? ;)

False, and I'll fight you for it! :) The Air Force requires this in their internal writing guide and I HATE IT! It is a remnant from typewriters and has no place in modern usage since (almost) all fonts are using proportional spacing now.

BTW, I corrected your spacing in your post I quoted to the proper single space after a period ;)

tauon 04-21-2021 02:05 PM

Quote:

Originally Posted by allend (Post 6243428)
Needing to save a byte is a very old habit. :)

Like using KOI8 instead of Unicode...

Quote:

Originally Posted by allend (Post 6243428)
PS - Actually testing Firefox 88.0 on my 32-bit install. Please ignore.

Is it possible to use modern FF on an i686? I switched to seamonkey (to save some more bytes of RAM of course)

tauon 04-21-2021 02:17 PM

Quote:

Originally Posted by tadgy (Post 6243435)
That was most probably a correction on my part when I modified netconfig during the rc.inet1 update - I can't see a period and single space without correcting it to proper English (read: British) typing standards :)

It seems no one teaches "the correct typing" British pupils anymore (I asked).

Quote:

Originally Posted by drumz (Post 6243386)
Two spaces after a period is the One True Way. For American (US) English, that is - and that's the only English that matters, right? ;)

Apparently, this rule is not just for US English, but also for British English. What about other countries? Germany? Saudi Arabia? China?

enine 04-21-2021 02:23 PM

https://www.thesaurus.com/e/writing/...fter-a-period/

Though I did learn on a computer, a Commodore 64, I learned the old typewriter style.

tauon 04-21-2021 02:56 PM

Quote:

Originally Posted by enine (Post 6243458)
https://www.thesaurus.com/e/writing/...fter-a-period/

Though I did learn on a computer, a Commodore 64, I learned the old typewriter style.

In Russia pupils usually don't learn neither on a typewriter, nor on a computer, teachers demand only cursive handwriting, and after school this leads to Word documents filled with tons of white spaces between words for alignment, and in front of periods, commas, and so on.

Tonus 04-21-2021 03:02 PM

Quote:

Originally Posted by tauon (Post 6243465)
In Russia pupils usually don't learn neither on a typewriter, nor on a computer, teachers demand only cursive handwriting, and after school this leads to Word documents filled with tons of white spaces between words for alignment, and in front of periods, commas, and so on.

Same here :doh:

Btw we have rules : after period or comma one space, 2 pieces (?) symbols like ?!:; to be surrounded with spaces.


All times are GMT -5. The time now is 03:28 PM.