Re: 4855 does not work in all cases

[Oliver Kiddle <opk@xxxxxxxxxxxxxxx>]

Andrej Borsenkow wrote:
> 
> > Variable            Cap Name  I. Code  Description
> > eat_newline_glitch  xenl      xn       Ignores new-line character after 80
> >                                        columns
> Unfortunately, it is not defined for dtterm (at least on our system). It seems
> to be defined for xterm and one more terminal type that do have the feature. But
> this is the general problem - how can you be sure that terminfo/termcap reflect
> the truth? Users are free to modify settings on the fly :-(

I'm no terminfo expert so correct me if I'm wrong but I'm assuming that
this xenl can either be set to true or false or can be not defined? If
this is correct then we should be all right as long as we can make a
good assumption in the case of not defined (the xterm behaviour I
suppose). Is xenl correct in the case of aixterm? When you say 'users
are free to modify settings on the fly', does this include xenl or just
things like am which are on the various mouse menus? If users are
modifying xenl, then surely they deserve everything they get so I
wouldn't see that as a problem. If terminfo/termcap entries are
occasionally wrong it might be better to mention how to fix them in the
FAQ than to write a load of nasty hacks to the code.

> if (!am || xenl) puts("\r\n");
> Not sure, that "\r\n" looks much better than " \n", but this works without
> auto-margin as well. Funnily enough, it will work even on my dtterm (that is
> configured for am but with terminfo that does not list this :-)

What doesn't it work for - only incorrect terminfo/termcap?

Thanks

Oliver Kiddle