[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Thoughts: header/address parsing
From: |
Ken Hornstein |
Subject: |
Re: [Nmh-workers] Thoughts: header/address parsing |
Date: |
Sun, 17 Aug 2014 23:56:09 -0400 |
>1) Instead of callers allocating the space for the fmt_scan()
> output, have fmt_scan() do it. Callers would pass a **char
> instead of a char array and be responsible for free'ing the
> space when they're done.
>
>2) fmt_scan() would use some function of width as the initial
> size of the space and realloc by 2X as needed.
>
>3) To not break existing user scripts, width would continue to
> include the trailing newline. Add support for an optional
> profile setting to not include the trailing newline.
>
>4) Add support for 0 width indicating infinite width.
This all seems reasonable to me.
--Ken
- Re: [Nmh-workers] Thoughts: header/address parsing, (continued)
- Re: [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Lyndon Nerenberg, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Lyndon Nerenberg, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Lyndon Nerenberg, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Ralph Corderoy, 2014/08/05
Re: [Nmh-workers] Thoughts: header/address parsing, David Levine, 2014/08/09
Re: [Nmh-workers] Thoughts: header/address parsing, David Levine, 2014/08/09
Re: [Nmh-workers] Thoughts: header/address parsing, David Levine, 2014/08/10
Re: [Nmh-workers] Thoughts: header/address parsing, David Levine, 2014/08/10