Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Will Senn <will.senn@gmail.com>
Cc: coff@tuhs.org
Subject: [COFF] Re: [TUHS] Algol rules: was something about Rust is not C++
Date: Wed, 01 Feb 2023 21:00:42 +0100	[thread overview]
Message-ID: <20230201200042.D6ytp%steffen@sdaoden.eu> (raw)
In-Reply-To: <20230201192938.ozV2d%steffen@sdaoden.eu>

Steffen Nurpmeso wrote in
 <20230201192938.ozV2d%steffen@sdaoden.eu>:
 |Will Senn wrote in
 | <3808a35c-2ee0-2081-4128-c8196b4732c0@gmail.com>:
 ||Well, I just read this as Rust is dead... here's hoping, but seriously, 
 ...

Talking about dead, i suddenly had the braindead desire to
reformat all my actively maintained things (sh,perl,python,C) in
the Christian Christmas time.  Quite sudden i was looking at the
about 30 percent of my laptop screen that i actually use
(COLUMNS=191 LINES=55, but that only after libxft-2.3.7 introduced
a bug that is still not fixed, it was more more before (i was
using Xft.embolden with LiberationMono which i had forgotten, but
otherwise with Xft.antialias it looks terrible still .. with that
many lines)), and was thinking "widescreen will never disappear
again".

Thus i dropped my yet always used attitude of 79 columns no matter
what, went back to tabulator indentation, and now use 120 columns,
without being strict (but max of about 140, as rarely as possible).
(Some old legacy sources still use the old style, but anything
planned to remain was converted.)

If that is not stupid and brain dead, i do not know.
Welcome back tabulators (it saved a lot of bytes!), and welcome
new widescreen world.  I do not regret it.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

      reply	other threads:[~2023-02-01 23:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAP6exY+_YKkJ2vHpz2sk-yjoDCnyx8g4jW_Lk3qynGV1cCuEOg@mail.gmail.com>
     [not found] ` <CALMnNGiXVeqBznYwhPmwR-jUtq2OMO64HHc2A4F0o+PFJMu3Fw@mail.gmail.com>
     [not found]   ` <RHhaWnWrWHJ6A5gopXMwP3kldg6f7uUUNFlrrJOKh_mTUzzdRTC-2SrEFcKcuI5WjX-1QXP_1YMRox50YRGzCqCze8PB3dvi5DR6cIiKE-o=@protonmail.com>
     [not found]     ` <CAP6exYJ8S--bhw6wm88JMeJKYiTW0tx_JD-au8NACaoAkQjiOA@mail.gmail.com>
     [not found]       ` <e90436d2-f730-bee6-f229-3cc75b1c06a8@gmail.com>
     [not found]         ` <CAEoi9W4nT-cwe2GJreO_xTt=YGfrgTDa5bHfiGf1Fo4bYocziw@mail.gmail.com>
     [not found]           ` <CAP6exY+Qz2Oe4gC4D1Fqy22JKKDaanTOYpc0gxugBv485JUknQ@mail.gmail.com>
     [not found]             ` <20230201004023.rHE9j%steffen@sdaoden.eu>
     [not found]               ` <20230201004939.GB6988@mcvoy.com>
     [not found]                 ` <b68b1bdb-695d-9d80-0b2d-4c0bdc11b183@makerlisp.com>
2023-02-01  1:50                   ` [COFF] Re: [COFF from TUHS] Re: yet another C discussion (YACD) and: " segaloco via COFF
2023-02-01 13:41                     ` Brad Spencer
     [not found]               ` <3808a35c-2ee0-2081-4128-c8196b4732c0@gmail.com>
2023-02-01 19:29                 ` [COFF] Re: [TUHS] Algol rules: was something about " Steffen Nurpmeso
2023-02-01 20:00                   ` Steffen Nurpmeso [this message]

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=20230201200042.D6ytp%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    --cc=coff@tuhs.org \
    --cc=will.senn@gmail.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 NNTP newsgroup(s).