Steffen Nurpmeso wrote:
> You know the entire thread is moot as i think bapt@ has thrown
> away the BSD termcap years ago, if i recall correctly (i think
> i spoke up by then).
> I only answered because of the "great it is gone" thing.
Maybe I should have rephrased that as "it's great that we
Hello Thomas Dickey.
Thomas Dickey wrote in
:
|On Thu, Nov 02, 2023 at 06:58:55PM +0100, Steffen Nurpmeso wrote:
|> I do understand that a bit. Other than that plain termcap was so
|> small and i would assume essentially unchanged for decades, that
|> i do not. Termcap entries, yes. I
On Thu, Nov 02, 2023 at 06:58:55PM +0100, Steffen Nurpmeso wrote:
> I do understand that a bit. Other than that plain termcap was so
> small and i would assume essentially unchanged for decades, that
> i do not. Termcap entries, yes. I could imagine vt220, xterm,
> screen-256color, and take one
Steffen Nurpmeso wrote:
> Why?
> (That is to say: why -- if it is a *real* termcap? If it is only
> a translation layer to terminfo, i am with you. But otherwise
> not, i think a real termcap is much, much smaller, while offering
> anything a (simple) console program needs.)
> That is not to
Baptiste Daroussin wrote:
> If you don't install (terminfo-db which nothing should pull in by default),
> then
> you are on the default behaviour which is termcap, this has been made like
> this
> on purpose, by default you have the behaviour you have always expected, and if
> you want another
On Wed, Nov 01, 2023 at 03:49:33AM +, Jamie Landeg-Jones wrote:
> Thomas Dickey wrote:
>
> > actually it probably does affect "xterm"
> >
> > Checking the source, tcsh is expecting a termcap string, while data read
> > from the terminfo database is going to be in terminfo format -- even if
Thomas Dickey wrote:
> actually it probably does affect "xterm"
>
> Checking the source, tcsh is expecting a termcap string, while data read
> from the terminfo database is going to be in terminfo format -- even if
> read via tgetent/tgetstr
>
> tcsh is expecting a termcap string, and in its
On Tue, Oct 31, 2023 at 10:59:48PM +, Jamie Landeg-Jones wrote:
> Jamie Landeg-Jones wrote:
>
> > switch to tcsh, and reinitialise terminal information:
> >
> > % setenv TERM dumb
> > % setenv TERM xterm
>
> % setenv TERM xterm-256color
>
> Apologies, it seems this doesn't affect plain
Jamie Landeg-Jones wrote:
> switch to tcsh, and reinitialise terminal information:
>
> % setenv TERM dumb
> % setenv TERM xterm
% setenv TERM xterm-256color
Apologies, it seems this doesn't affect plain "xterm", but it does at least
affect xterm-16color and xterm-256color.
Is this,
