Re: WARNING: terminal is not fully functional
Sorry, I did not see your previous post TERM=rxvt-cygwin (X mode) termcap patch. You prefer to add an entry in termcap rather that altering the start menu shortcuts. Thanks, Frédéric -- 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/
WARNING: terminal is not fully functional
when I want to use man (for example $ man ls), I get this error message (with 1.5 and 1.7): WARNING: terminal is not fully functional - (press RETURN) I am using rxvt-x. This does not happen with rxvt-native. Frédéric -- 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/
Re: WARNING: terminal is not fully functional
2009/5/6 Frédéric Bron: WARNING: terminal is not fully functional - (press RETURN) So you have $TERM set to something that the system doesn't recognize. What does 'echo $TERM' return in each case (rxvt-x vs rxvt-native)? --Mark J. Reed markjr...@gmail.com -- 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/
Re: WARNING: terminal is not fully functional
So you have $TERM set to something that the system doesn't recognize. What does 'echo $TERM' return in each case (rxvt-x vs rxvt-native)? rxvt-x - TERM=rxvt-cygwin rxvt-native - TERM=rxvt-cygwin-native Frédéric -- 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/
Re: WARNING: terminal is not fully functional
2009/5/6 Frédéric Bron: rxvt-x - TERM=rxvt-cygwin rxvt-native - TERM=rxvt-cygwin-native That's the problem. /etc/termcap has an entry for rxvt-cygwin-native, but not for rxvt-cygwin. What you want in that case is just TERM=rxvt. Not sure where the bug is. Either rxvt is setting TERM wrong, or you have something in your shell initialization that's overriding it, or /etc/termcap is missing an alias for the entry. -- 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/
Re: WARNING: terminal is not fully functional
rxvt-x - TERM=rxvt-cygwin rxvt-native - TERM=rxvt-cygwin-native That's the problem. /etc/termcap has an entry for rxvt-cygwin-native, but not for rxvt-cygwin. What you want in that case is just TERM=rxvt. Not sure where the bug is. Either rxvt is setting TERM wrong, or you have something in your shell initialization that's overriding it, or /etc/termcap is missing an alias for the entry. Its a fresh new install! Nothing about TERM in .bashrc, nor in .bash_profile. I just have the following in my .Xdefaults: Rxvt*termName: rxvt Looks like it is ignored. So is it a bug? Frédéric -- 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/
Re: WARNING: terminal is not fully functional
Frédéric Bron wrote: rxvt-x - TERM=rxvt-cygwin rxvt-native - TERM=rxvt-cygwin-native That's the problem. /etc/termcap has an entry for rxvt-cygwin-native, but not for rxvt-cygwin. What you want in that case is just TERM=rxvt. Not sure where the bug is. Either rxvt is setting TERM wrong, or you have something in your shell initialization that's overriding it, or /etc/termcap is missing an alias for the entry. As the default termcap already includes an entry for rxvt-cygwin-native as a convenience for cygwin users, it should probably be updated to also include an entry for rxvt-cygwin. The three entries: rxvt rxvt-cygwin-native rxvt-cygwin differ only in their ACS (line draw) character string, which only works if you're using an OEM-recoded font...so, using TERM=rxvt is probably good enough for both variants, for most people. (I know of only one OEM-recoded font: Lucida ConsoleP) Its a fresh new install! Nothing about TERM in .bashrc, nor in .bash_profile. I just have the following in my .Xdefaults: Rxvt*termName: rxvt Looks like it is ignored. So is it a bug? Maybe, but maybe not. Rxvt looks for the .Xdefault using the following construction: getenv(HOME) + /.Xdefaults It does NOT use getpwent() to figure out your home directory from /etc/passwd. Therefore, if you start rxvt fron Windows (e.g. using a shortcut), then Rxvt can find ~/.Xdefaults ONLY if you have set %HOME% using the Windows Environment settings tool. My guess is that on your brand new installation, you haven't done this -- so the behavior is expected. -- Chuck -- 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/
Re: WARNING: terminal is not fully functional
As the default termcap already includes an entry for rxvt-cygwin-native as a convenience for cygwin users, it should probably be updated to also include an entry for rxvt-cygwin. The three entries: rxvt, rxvt-cygwin-native, rxvt-cygwin differ only in their ACS (line draw) character string, which only works if you're using an OEM-recoded font...so, using TERM=rxvt is probably good enough for both variants, for most people. (I know of only one OEM-recoded font: Lucida ConsoleP) $ TERM=rxvt man ls gives the good behaviour. I just have the following in my .Xdefaults: Rxvt*termName: rxvt Looks like it is ignored. So is it a bug? Maybe, but maybe not. Rxvt looks for the .Xdefault using the following construction: getenv(HOME) + /.Xdefaults It does NOT use getpwent() to figure out your home directory from /etc/passwd. Therefore, if you start rxvt fron Windows (e.g. using a shortcut), then Rxvt can find ~/.Xdefaults ONLY if you have set %HOME% using the Windows Environment settings tool. My guess is that on your brand new installation, you haven't done this -- so the behavior is expected. I have not defined HOME but I can confirm that rxvt is reading .Xdefault as I use it to define the window size, colors, font size... I have tried to add HOME in Windows env. var but it did not change anything (either with a DOS path or a Cygwin path). So there is something strange with this TERM thing and rxvt. Frédéric -- 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/
Re: WARNING: terminal is not fully functional
Frédéric Bron wrote: I have not defined HOME but I can confirm that rxvt is reading .Xdefault as I use it to define the window size, colors, font size... I have tried to add HOME in Windows env. var but it did not change anything (either with a DOS path or a Cygwin path). You'd use a DOS path. Cygwin autoconverts (some) environment variables into cygwin format; IIRC %HOME% - $HOME is one of them. So there is something strange with this TERM thing and rxvt. Have you customized /etc/X11/app-defaults/Rxvt ? Also, are you using the shortcuts in StartMenu/Cygwin/ that were created automatically, or ones that you created yourself? The auto-created one for rxvt-x has this command line: C:\cygwin-1.7\bin\run.exe /usr/bin/rxvt.exe -display 127.0.0.1:0 -tn rxvt-cygwin -e /bin/bash --login The -tn rxvt-cygwin command line argument always wins, no matter what is specified in /etc/X11/app-defaults/Rxvt or ~/.Xdefaults. -- Chuck -- 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/
Re: WARNING: terminal is not fully functional
Also, are you using the shortcuts in StartMenu/Cygwin/ that were created automatically, or ones that you created yourself? The auto-created one for rxvt-x has this command line: C:\cygwin-1.7\bin\run.exe /usr/bin/rxvt.exe -display 127.0.0.1:0 -tn rxvt-cygwin -e /bin/bash --login The -tn rxvt-cygwin command line argument always wins, no matter what is specified in /etc/X11/app-defaults/Rxvt or ~/.Xdefaults. You got it! I use the one from Cygwin menu and the -tn rxvt-cygwin is to be blamed. I changed it to rxvt only and it works perfectly. Before this brand new install, I used shortcuts that I wrote myself and there was possibly not this -tn thing. Can we correct the shortcut in the Start Menu/Cygwin so that nobody has the same problem in the future? Frédéric -- 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/
