No entry for terminal type "vt100" ??
 

Downloaded and installed Mutt for OSX today, booted up Terminal and it gives me this message:

Last login: Mon Oct 20 20:07:42 on console
Welcome to Darwin!
tcsh: No entry for terminal type "vt100"
tcsh: using dumb terminal settings.
[emac:~] me%

tried to remove all the bits and pieces from Mutt...but still getting the same message. Googled all day and followed several suggestions, but none of them worked.

Tell me there's an easy newbie way to fix this ... please?

Thanks

Have you created and been in your ~/.tcshrc or ~/.cshrc?

No I haven't touched them...but terminal worked fine before...?

Even though you haven't changed your "dot" files, the installer for mutt might have changed them.
In fact, it seems that it must have chnaged something in your "dot" files to have caused this problem in Terminal.
If you are using Fink, you probably have a line in your ~/.tcshrc file that says
source /sw/bin/init.csh
This means that any change to /sw/bin/init.csh (or the files it uses) will affect your Terminal as well.
You need to trace the various "dot" files, perhaps by adding "echo" statements in them to see where the problem arises.

I don't know what Fink is, so I guess I'm not using it (!)
What should I be looking for in my 'dot' files?

As far as I recall, the default "dot" files supplied with OS X are empty, so anything in there is a result of something you installed or your editing.
So maybe just show us the complete contents of the following files:
~/.login
~/.cshrc
~/.tcshrc
(Not all of these necessarily exist)
Easiest is to go into a Terminal window and do:

cat ~/.login

and then copy I paste back into a response here.
Do the same with the otehr files.

Here they are:

Last login: Wed Oct 22 12:20:30 on ttyp1
Welcome to Darwin!
tcsh: No entry for terminal type "vt100"
tcsh: using dumb terminal settings.
[emac:~] me% cat ~/.login
source /usr/share/tcsh/examples/login
[emac:~] me% cat ~/.cshrc
cat: /Users/me/.cshrc: No such file or directory
[emac:~] me% cat ~/.tcshrc
source /usr/share/tcsh/examples/rc

Does this help?
Should I just edit those files to be empty?

Thanks for your speedy help so far!

to the source...
 

what is the result of:

[emac:~] me% find /usr/share/terminfo/ -name "vt100"
/usr/share/terminfo//76/vt100

note the double slash before 76....is that right?

yeah, that's okay.

blubbernaut,

Maybe you look at the files installed by Mutt:

Mutt system configuration file is probably in /usr/local/share/mutt/Muttrc or /etc/Muttrc. Also, look look for a file named .muttrc in your home directory. Or in .mutt/muttrc.

Check what they source, for example 'source /usr/local/share/Mutt.aliases' , 'source ~/.mail_aliases' etc...etc...

If your terminal was working before, we might get to know why it is not working now.

Unfortunately I have deleted all the Mutt files. To clarify, terminal was working before installing Mutt, vt100 error immediately after installing Mutt, and continues after deleting Mutt.

Is there a way to reinstall the necessary bits for Terminal without doing a full system install, or is that wishful thinking?

You could reinstall Terminal from the Install CD and then re-apply the various updates again.

But it seems to me that your problem is not with the Terminal executable itself but rather with some configuratiion file. And so this problem would likely persist even after a reinstall since the configuration file is likely under your home folder.

You need to find out what configuration has been changed.

Your ~/.tcshrc file sourced the file /usr/share/tcsh/examples/rc
so you need to check what is in that file (looking especially for other 'source' commands which reference other files) and so on. As an experiment you could try moving the ~/.tcshrc file out of your home folder and then opening a new Terminal window to see if that makes a difference.

Look also at the Preferences for Terminal.
Check if you have it configured to open a .term file at startup, check if it is configured to run a command in a new window.

Try creating a new user and see (after logging in as that user) if that user has the problem. If not, that confirms that the problem is with some configuration file in your home folder.

Tried the new user, and the problem is still there?!? any clues...?

Please show us the complete contents of the following files for that new user (as you did earlier for your normal user account):
~/.login
~/.cshrc
~/.tcshrc

This is a long shot, but the problem described sounds like what was happening to people when they "double logged in" under Jaguar. That is, they would enter "login" in a terminal window rather than just, well, *use it*.

Just to be sure, blubbernaut, does this error occur when you first open the terminal, or are you "logging in" to the terminal? (Apologies if this sounds like I'm asking dumb questions: maybe I am!) If so, there's no need. If you're not running "login" in a terminal window then my troubleshooting skills are exhausted.

Cheers, and good luck,
Paul

Hayne: it's weird...the new user doesn't have those dot files.

Paul: this is happening the moment I open Terminal, not using login, or any new preferences for Terminal or anything.

Will restoring the directories that Mutt wrote to from an old backup cause me lots of pain do you think?

Thanks guys

blubbernaut,

Please, could you check in the files /etc/profile and /etc/csh.login if you have any reference to:

TERM=vt100;export TERM

or

set term=vt100

Contents of /etc/profile is:

# System-wide .profile for sh(1)

PATH="/bin:/sbin:/usr/bin:/usr/sbin"

export PATH

and contents of /etc/csh.login is:

# System-wide .login file for csh(1).

setenv PATH "/bin:/sbin:/usr/bin:/usr/sbin"

so no vt100 reference....I'm really stumped!

thanks again guys

what does:
look like over there?

it gave me the same output as you've got:

[emac:~] me% toe | grep "^vt100 "
vt100 dec vt100 (w/advanced video)
[emac:~] me%

(I assume the $ symbol is not to be entered? ...remember...unix newbie...learning fast:rolleyes: )

blubbernaut,

Could you try running in terminal.app:

% setenv TERM xterm

then close terminal.app and open it again.

Do you get the same message?

Immediately after entering that command, I get No entry for xterm. Then the same stuff when restarting terminal!

Sorry I currently don't have net access from home, so this isn't the exact wording. (OMG, I've turned into one of those people I hate, who ring me and say "it gave me an error" "what did it say" "I dunno, something about can't do something....umm....")

can you run the tack command?

% tack


something very squirrelly here. is there anything in any terminal pref that is questionable? have you toggled any of the prefs?

fs_usage
 

Hmm, since you don't seem to be able to track down what the problem is by the usual methods (looking at the contents of the various "dot" files, etc), maybe it is time to bring out the big guns.

The command 'fs_usage' shows you what files are being accessed and by what program.
To use it to diagnose your problem,
run the following command in one Terminal window:

sudo fs_usage > ~/my_output.txt

(call the output file anything you like)

and then open up a new Terminal window
and then go to the window where fs_usage is running and type control-C to stop it.
Examine the output file with your favourite editor and look for files refererenced by Terminal or any of the shells.

Well, this is what tack brought up:
Terminal reset (rs2)
init
Using terminfo from: /usr/local/share/terminfo/v/vt100

Name: vt100|vt100-am|dec vt100 (w/advanced video)
\r ^M (cr) = ^M
\n ^J (ind) = ^J
\b ^H (cub1) = ^H
\t ^I (ht) = ^I
(clear) = ^[[H^[[J$<50>
(home) = ^[[H
ENQ (u9) = *** missing ***
ACK (u8) = *** missing ***

Terminal size: 80 x 24. Baud rate: 9600. Frame size: 10.0

Main Menu
b) display basic information
m) change modes
t) tools
n) begin testing
l) start logging
q) quit
?) help

tack [n] >



I dunno what any of this means...its all Greek to me!

Also ran fs_usage, there were no references to Terminal in the output. I won't post the contents here as its very very long, but there didn't seem to be any errors or anything...not that I really know what I'm looking for. There was a reference to private/etc/csh.login that I will look at when I get home.

You wouldn't expect to see any errors in fs_usage output. What you are looking for is what files are read by Terminal when it opens a new window.
The file you mention would be /private/etc/csh.login which is the same as /etc/csh.login
You should definitely look to see what is in that file.

Just an update if anybody is still following this thread: as I am a newbie at unix stuff, and didn't have any special stuff installed in that area to lose, I decided to cut my losses and reinstall.

On a whim I just opened up the jag install cd and additional stuff and just double-clicked install BSD subsystem, which all went very smoothly...but unfortunately didn't fix the prob.
Then did archive and install of jag and reinstalled 10.2.6 combo (I'm still scared of .8!)....problem fixed, and it only took half an hour and a little bit of pissing around updating a few things like quicktime and stuffit that were downgraded with the archive and install.

thanks to all your help guys!