[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] colorized/highlighted scan output?
From: |
David Levine |
Subject: |
Re: [Nmh-workers] colorized/highlighted scan output? |
Date: |
Fri, 02 Nov 2012 16:52:22 -0500 |
Oliver wrote:
> Multiplying maximum width by MB_CUR_MAX is one way to determine a
> suitable buffer size though that doesn't allow for escape seqences for
> colours. Is it too ugly to have the function allocate the buffer and
> rely on the caller to free it?
fmt_compile() does that, but not fmt_scan().
In scan, at least, the caller of fmt_scan() allocates the
buffer but doesn't bother to free it. So, no, I don't think
it'd be too ugly.
> The same code change could also address the following request which is
> for -width 0 to be unlimited:
> http://savannah.nongnu.org/bugs/?15274
I had noticed that a while ago but wondered if there's
really a need for -width 0. Though getting rid of fixed
size buffers would be helpful.
David
- Re: [Nmh-workers] colorized/highlighted scan output?, (continued)
Re: [Nmh-workers] colorized/highlighted scan output?, David Levine, 2012/11/02
Re: [Nmh-workers] colorized/highlighted scan output?, David Levine, 2012/11/02
Re: [Nmh-workers] colorized/highlighted scan output?,
David Levine <=
Re: [Nmh-workers] colorized/highlighted scan output?, David Levine, 2012/11/03
Re: [Nmh-workers] colorized/highlighted scan output?, David Levine, 2012/11/04
Re: [Nmh-workers] colorized/highlighted scan output?, David Levine, 2012/11/05
Re: [Nmh-workers] colorized/highlighted scan output?, David Levine, 2012/11/06