Date: Wed, 11 Sep 2019 15:46:03 -0700
On Wednesday, 11 September 2019 14:31:07 PDT Steve Downey wrote:
> And stdout is not rich enough for dealing with rendering issues. The
> program producing text is entirely decoupled from details of how the
> terminal renders.
True, but you can make sufficiently educated guesses. Aside from obscure EGCs,
recently-standardised codepoints, unassigned codepoints and broken fonts, the
renderer and the producer should be able to agree on what the width should be.
Let's standardise on that.
We ned to be able to produce this with std::format:
5630f4785000-5630f4787000 r--p 00000000 00:2f 11621326 cat
5630f4787000-5630f478b000 r-xp 00002000 00:2f 11621326 cat
> And stdout is not rich enough for dealing with rendering issues. The
> program producing text is entirely decoupled from details of how the
> terminal renders.
True, but you can make sufficiently educated guesses. Aside from obscure EGCs,
recently-standardised codepoints, unassigned codepoints and broken fonts, the
renderer and the producer should be able to agree on what the width should be.
Let's standardise on that.
We ned to be able to produce this with std::format:
5630f4785000-5630f4787000 r--p 00000000 00:2f 11621326 cat
5630f4787000-5630f478b000 r-xp 00002000 00:2f 11621326 cat
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel System Software Products
Received on 2019-09-12 00:46:07