globelblade / mobileterminal

Automatically exported from code.google.com/p/mobileterminal
1 stars 3 forks source link

Error opening terminal: network #37

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install mobileterminal from installer.app
2. Install NateTrue's binarykit
3. Install BSD Subsystem
4. Install OpenSSH from installer.app
4. Open up terminal
5. Type any of the following vt100 commands: pico, top, nano, vim, (etc..)

What is the expected output? What do you see instead?
With pico & nano i get:
 Unknown terminal type network!
With top i get:
 Error opening terminal: network
With vim i got:
 E559: Terminal entry not found in termcap
 'network' not known.  Available builtin
 terminals are:
  builtin_ansi
  builtin_xterm
  builtin_iris-ansi
  builtin_dumb
defaulting to 'ansi'

Then vim kinda worked.  But when i delete i delete characters that I
shouldn't be deleting (aka characters that make up the program).

What version of the product are you using? On what operating system?
I installed the latest version from Installer.app.  svn113

Please provide any additional information below.
I realize I may have shunned myself a n00b by posting this, but it wasn't
posted anywhere and I decided to be brave.

Oh, and one more thing:  when I start up my terminal.app it says:
Last login: Thu Aug 16 14:44:17 on ttyp0
# #

Why two number signs?  And when I hit the delete key it deletes the number
signs and continues to delete the login date & time & "ttyp0" !  Are all
these problems related?

Original issue reported on code.google.com by Dimitri....@gmail.com on 16 Aug 2007 at 6:52

GoogleCodeExporter commented 9 years ago
Thanks for the detailed bug report; Please don't shy away from bugs in the 
future,
and hopefully they will be responded to directly faster in the future :)

These are a few different problems going on here.  Some are at the "BSD 
Subsystem"
level, which defaults the terminal to "network".  We can fix that by passing in 
some
environment variables to set the terminal (in progress in the vt100 and 
vt100-iterm
branches).

The second problem is from lack of vt100 support and a zsh shell.  This should 
get
better when vt100 is built into the main branch.

Original comment by allen.po...@gmail.com on 21 Sep 2007 at 1:06

GoogleCodeExporter commented 9 years ago
I am closing this bug, as vt100 is now stable enough and has been integrated 
into the
"trunk" and should be contained in the next binary release.

We also pass in an environment variable setting TERM to vt100, but most people 
are
using the BSD subsystem package which by default sets the terminal to vt102.

Original comment by allen.po...@gmail.com on 1 Oct 2007 at 8:26

GoogleCodeExporter commented 9 years ago

Original comment by allen.po...@gmail.com on 1 Oct 2007 at 8:27