screen-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (no subject)


From: Jeremy Chadwick
Subject: Re: (no subject)
Date: Wed, 12 Jan 2005 10:45:28 -0800
User-agent: Mutt/1.5.6i

I was just educated by hop of EPIC fame that it's common for software
authors to use ncurses for termcap and/or terminfo support, as on BSD
platforms -lncurses is much preferred over -ltermcap.

Seems ldd isn't a very good choice for determining what features
software relies on.  My apologies for snapping.

-- 
| Jeremy Chadwick                                 jdc at parodius.com |
| Parodius Networking                        http://www.parodius.com/ |
| UNIX Systems Administrator                   Mountain View, CA, USA |
| Making life hard for others since 1977.                             |

On Wed, Jan 12, 2005 at 07:05:53PM +0100, Michael Schroeder wrote:
> On Tue, Jan 11, 2005 at 10:19:36AM -0800, Jeremy Chadwick wrote:
> > I'd like to see all nethack references removed, as they have zero
> > relation to screen.  If this isn't acceptable, I'd like to see "nethack
> > off" in .screenrc actually get loaded by screen before attaching to a
> > terminal (i.e. for error messages screen prints out, etc.).  I'd even be
> > willing to accept an #ifdef NETHACK_CRUFT around appropriate pieces of
> > code.
> 
> Just #undef NETHACK in config.h.
> 
> > I'd also like to see screen not pad the width of the terminal with
> > spaces.  I've seen numerous arguments about this in the past (re:
> > terminfo, termcap, etc.) but all changes I've tried in the past still
> > result in whitespace-padded lines.  BCE on/off had no effect.
> 
> It doesn't do this for me. I don't know why screen is doing this in
> your case. Does anybody else on the list have the same problem?
> 
> > NCURSES_NO_PADDING also had no effect.
> 
> No surprise here, as screen doesn't use curses.
> 
> Cheers,
>   Michael.
> 
> -- 
> Michael Schroeder           address@hidden
> main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}




reply via email to

[Prev in Thread] Current Thread [Next in Thread]