This is the mail archive of the cygwin-xfree mailing list for the Cygwin XFree86 project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Sorry for the crosspost - I posted this on the Cygwin list last week, but didn't get a response, and realized that it probably belonged better on this list, so I'm trying again.
I'm sorry if there's an easy solution that I haven't found yet, but I'm wondering if anyone else is experiencing the same problem with Cygwin/X's xterm as I am. xterm -tn doesn't seem to properly set up the TERM variable.
For example: xterm -tn xterm-16color -e bash -c 'echo TERM=$TERM; read x'
pops up a Cygwin/X xterm window containing TERM=xterm
Whereas rxvt -tn xterm-16color -e bash -c 'echo TERM=$TERM; read x'
pops up a Cygwin/X rxvt window containing TERM=xterm-16color
Can anyone else confirm this behavior, or offer a suggestion on how to deal with this behavior? I want to use xterm, since I couldn't get the same level of unicode support in rxvt cygwin native, rxvt cygwin x unicode, or rxvt cygwin. I also don't want to explicitly set TERM in one of my dot files, since I use the same ones on many computers.
Thanks in advance for any help! ~Matt Wozniski
Attachment:
cygcheck.txt
Description: Text document
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |