Re: multi-line field issues

[Sentinel]

On Sun, 12 Oct 2008, Thomas Dickey wrote:

> On Fri, Oct 10, 2008 at 10:33:49PM +0530, Sentinel wrote:
> > I believe I had earlier reported that a multi-line field will not display
> > anything if there are newlines in the string passed to it through
> > set_field_buffer.
> >
> > Today, I was testing one program which was displaying a file created
> > using:
> >
> > >     ls -ltr | nl > test.t
> >
> > I found 2 new issues:
> >
> > It will not display anything if:
> >
> > 1. TAB is present ("nl" places a tab)
> > 2. Any non-print characters. (my "ls" uses colors which introduces ansi
> > escape characters).
>
> that _sounds_ like a bug report (I did not get far enough this weekend
> to investigate this, since I was clearing out backlog...)
>
> > I am wondering if this feedback could be incorporated, or is ncurses only
> > looking at bug-fixes.
>
> ...it's on my to-do list...
>
> --
> Thomas E. Dickey <address@hidden>
> http://invisible-island.net
> ftp://invisible-island.net
That's wonderful. It would be nice if people could use the multiline edit 
just like any other textarea/editor. I have been studying some apps that 
use 
ncurses and found that none of them use multiline. Most just invoke vim or 
write their own.

Thus, at the time of set_field_buffer and field_buffer if data 
transformation can be done so a file can be read and set in, and then 
saved out, and it remains as is, it would be great.

This data transformation would not be required if FIELD did not pad the 
line with spaces but actually inserted a newline when the user presses 
enter. Similarly, if it toook in newlines and used them to set individual 
lines.

Thanks a lot for your effort.