Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Sep 2001 02:17:52 -0400
From:      Jason Vervlied <jvervlied@hway.net>
To:        freebsd-ports@freebsd.org
Subject:   probelem wiht Eterm 0.9.1
Message-ID:  <20010910061445.ECEFD37B405@hub.freebsd.org>

next in thread | raw e-mail | index | archive | help
I recently upgraded my port of Eterm to 0.9.1. Now whenever I launch Eterm, 
it is setting my TERM to Eterm instead of vt100 or vt102. This is causing 
some problems with a few apps such as vi, vim, and less. I can easily fix 
this by setting the TERM variable to vt102, but it is quite annoying. Is 
there a way to the port to set the default TERM to vt100 or vt102 or xterm or 
someting.

Here is a copy of a few of the errors I recieve in my apps.

vim
Cannot open termcap file
'Eterm' not known. Available builtin terminals are:
    builtin_gui
    builtin_ansi
    builtin_xterm
    builtin_iris-ansi
    builtin_dumb
defaulting to 'ansi'

(It works, but I have to use the old style fo moving the curser rather than 
being able to use the arrow keys)

vi
No terminal database found

less
WARNING: terminal is not fully functional

Here are descriptions of some other apps I have problems with. 

top
displays process information, but immediatly exits with no error message

more
displays one page of information and exits immediatly

man
up arrow does not work to scroll up and I recive a message at the bottom of 
the screen with the current byte of the file I am viewing.

--
Thank you for your help,

Jason

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010910061445.ECEFD37B405>