Re: eterm: Home and End don't work
On Wed, May 16, 2001 at 05:27:37PM -0500, Daniel Jacobowitz wrote:
> Au contrair, it usually does.
Only when it tells how to actually fix the problem, not that the maintainer
plans to fix the problem in some later release. If the maintainer doesn't
plan to fix the problem until a later release, he should leave the bug open,
and close it after the problem is fixed.
> > As far as the Eterm terminfo entry, this is not sufficient for anyone who is
> > not running unstable on every box. Some of us actually need to be able to
> > login to machines of different architechtures and have things work. Just
> > because upstream did something braindead doesn't mean that Debian users
> > should have to suffer.
>
> Care to present an alternative? Documenting this problem seems to be
> the only reasonable solution, every time it appears, usually re xterm
> itself.
The problem here is that they are using their own terminal entry, one which
is not present in standard ncurses 5.2. The Eterm homepage mentions
something about the "new" ncurses, which will supposedly add support for
their terminal, but the current ncurses is almost a year old, so when is this
fabled new version coming out?
> It's in ncurses-term. Eterm will need to depend on ncurses-term, or
> request that it be moved to ncurses-base (which I'm not sure I want to
> do).
That still requires me to move Eterm terminfo entries over to every
non-Debian-sid system I wish to have a functional terminal on, or use the
broken xterm emulation.
Why is this so hard? There are plenty of other xterms on the market that
seem to have this figured out. Why is it necessary for Eterm to reinvent the
wheel?
--Adam
--
Adam McKenna <adam@debian.org> <adam@flounder.net>
Reply to: