Re: TERM (was Cursors)

On 2022-06-15, 'Grant Taylor' via vim_use wrote:
> On 6/15/22 2:43 PM, Gary Johnson wrote:
> >Yeah, but...
>
> IMHO there's no but about it.

[...]

Points well made and well taken.

> >HP had this problem about 40 years ago when they introduced
> >a successor to the 2645 terminal. Its ID string was something like
> >"HP2647" and customers raised Cain that their systems did work right
> >with the new terminal, so HP changed it to report itself as an
> >"HP2645".
>
> IMHO HP made the wrong choice. It sounds like they bowed to
> marketing pressure and made their new HP2647 terminal lie and say
> that it was an HP2645. Maybe the marketing / support types have more
> clout than the technical types.

I think they did. That was true for HP-UX as well.

> >I use [termresponse] when it matters what the terminal really is.
>
> I often find that the answer back is unset / null or that the
> terminal (emulator) completely fails / ignores it.

Fortunately, all the terminals I use support it. My Chromebook's
Crosh Window uses the same termresponse string as an Xterm 256
emulating a vt100, but I don't have any of those Xterms, so it
works.

Regards,
Gary

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20220615213452.GF20513%40phoenix.