On 6/5/2009 11:58 AM, David Karr wrote: >>>> C:\cygwin\bin\bash.exe --login -c "C:/cygwin/bin/emacs.exe" >>> emacs: Terminal type cygwin is not defined. >>> If that is not the actual type of terminal you have, >>> use the Bourne shell command `TERM=... export TERM' (C-shell: >>> `setenv TERM ...') to specify the correct type. It may be necessary >>> to do `unset TERMINFO' (C-shell: `unsetenv TERMINFO') as well. >> Again, why run bash first then run emacs? >> Again, so I get a login shell. In any case, this has no effect on the > symptom. I tried doing this without bash, and it fails in exactly the same > way. I have a few other suggestions if you want to keep trying to track this down: 1. Send cygcheck output (as an attachment) as requested at http://cygwin.com/problems.html 2. Try emacs -q to make sure there's nothing in your initialization file(s) causing the problem. 3. Try emacs 23: http://sourceware.org/ml/cygwin/2009-05/msg00475.html http://sourceware.org/ml/cygwin/2009-05/msg00635.html Ken -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/