Computer Old Farts Forum
 help / color / mirror / Atom feed
From: steffen at sdaoden.eu (Steffen Nurpmeso)
Subject: [COFF] Was [TUHS] tabs vs spaces - entab, detab
Date: Fri, 12 Mar 2021 01:31:30 +0100	[thread overview]
Message-ID: <20210312003130.L6HcL%steffen@sdaoden.eu> (raw)
In-Reply-To: <CAC0cEp93762jEt4BAed-tQ7-vi1YGVEket=B8Z-F-3finWUHbw@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2283 bytes --]

John P. Linderman wrote in
 <CAC0cEp93762jEt4BAed-tQ7-vi1YGVEket=B8Z-F-3finWUHbw at mail.gmail.com>:
 |On Thu, Mar 11, 2021 at 4:18 PM Steffen Nurpmeso <steffen at sdaoden.eu> \
 |wrote:
 |> John P. Linderman wrote in
 |>  <CAC0cEp9GVsYbjYhsYk2Hjjj90FxYFAia2Luy_vg854NTrV3Hww at mail.gmail.com>:
 |>|The tab/detab horse was still twitching, so I decided to beat it a little
 |>|more.
 |>|
 |>|Doug's claim that tabs saving space was an urban legend didn't ring true,
 |>|but betting again Doug is a good way to get poor quick.
 |
 |> Not really.  I mean, i do not insist of this, but i looked at the
 |> numbers.  And despite col(1) 2.36.2 giving the wrong line when
 |> failing to dig a LATIN1 in UTF-8 (should be 7, gave 11), when
 |> i sum up the total of 8: in an old project with tests,
 |> documentation etc. here the output is 1044401.  This is without
 |> generated data.
 |
 |I'm not certain what you are referring to by "Not Really". But there is a

I am sorry.  It must have been bad english and a misunderstanding.
Especially surrounding the dead horse that was mentioned in the
original message of yours.

 |general issue about the ability of historical commands (like "ed") to
 |properly handle unicode. I would expect that many early commands do very
 |poorly. -- jpl

Yes.  Of course.  It is one of these days were whatever i do
i stumble over errors in my own as well as in other peoples
software, and then this script of years was a nice try (i never
actually did that test), and then the find(1) i did spit out
masses of errors, and it took quite some trials to get it done.
I apologise.  Just one of these days.

  $ echo Müßig | iconv -f utf8 -t latin1 | LC_ALL=C col -x
  col: failed on line 1: Invalid or incomplete multibyte or wide character

This should not happen.  (Now also clarified by POSIX standard.)

  #?1|kent:tmp$ cat <<_EOT | iconv -f utf8 -tlatin1 | LC_ALL=C col -x
  one
  two
  three
  four
  five
  älter
  _EOT
  col: failed on line 11: Invalid or incomplete multibyte or wide character
  one
  two
  three
  four
  five

No fun for me today.

--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:[~2021-03-12  0:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 20:02 jpl.jpl
2021-03-11 21:18 ` steffen
2021-03-11 23:31   ` jpl.jpl
2021-03-12  0:31     ` steffen [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=20210312003130.L6HcL%steffen@sdaoden.eu \
    --to=coff@minnie.tuhs.org \
    /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).