[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Thoughts: header/address parsing
From: |
Ralph Corderoy |
Subject: |
Re: [Nmh-workers] Thoughts: header/address parsing |
Date: |
Sun, 10 Aug 2014 17:16:59 +0100 |
Hi David,
> > OK, so we're normally after columnar output. How about `-columns
> > C', where the string is output, as measured by wcwidth(), until
> > either the string ends or C would be exceeded.
>
> How about -outsize, to be consistent with fmttest(1):
>
> The -outsize switch controls the maximum number of printable
> characters that the format engine will produce. Characters marked
> as non-printing by the format engine with `%(zputlit)', characters
> with zero width, and extra bytes that are part of a multibyte
> character are not counted against this total. Two special values
> are supported: “max”, which will set the value to the size of the
> output buffer, and “width”, which will set the value to the width
> of the terminal.
I know there are few nmh programmers that haven't coded assember, but
-outsize is something only a programmer could like. :-)
The functionality sounds OK, though it needs to know `Foo' is 2+1+1;
there's no mention of wider-than-one runes above AFAICS. Also, is
`width' the value of `tput cols' this time, or one less again?
> > Then pad with ASCII space until C is met.
>
> I don't think that we should add trailing space. The output need not
> be columnar.
No, you're right. I was confusing it with `%42(decode{subject})'.
Cheers, Ralph.
Re: [Nmh-workers] Thoughts: header/address parsing, David Levine, 2014/08/10
Re: [Nmh-workers] Thoughts: header/address parsing, David Levine, 2014/08/10
Re: [Nmh-workers] Thoughts: header/address parsing, David Levine, 2014/08/16
Re: [Nmh-workers] Thoughts: header/address parsing, David Levine, 2014/08/24