| delorie.com/archives/browse.cgi | search |
On Tue, Jan 6, 2009 at 10:51 AM, Larry Hall (Cygwin) <reply-to-list-only-lh AT cygwin DOT com> wrote: > OK, sounds like an environment problem then. You could probably spot > the issue by comparing the environment you get in bash with the one > you get in cmd.exe. I did that already and that was how I came to know I could solve the original problem by modifying %path%. PATH is the only variable whose contents differed - %path% was prefixed with Cygwin bin directories. Also there were new variables inherited from bash which were: EDITOR=env -u DISPLAY vim FIGNORE=.svn:.o:~ HOME=h:\ HOSTNAME=blr-win-217 INFOPATH=/usr/local/info:/usr/share/info:/usr/info: MAKE_MODE=unix MANPATH=/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man OLDPWD=/cygdrive/e/Symbian/M04765_Symbian_OS_v9.5/src/CEDAR/GENERIC/base/bsp/hwip_arm/rvemuboard/falcon PRINTER=Microsoft Office Document Image Writer PS1=e[22;31mHe[00m [e[22;32mwe[00m]n! $ PS3=> PWD=/cygdrive/h SHLVL=1 SVN_EDITOR=env -u DISPLAY vim "+set tw=100" TERM=cygwin USER=jeevis01 _=/cygdrive/c/WINDOWS/system32/cmd But, I don't see anything harmful here. -- :J -- 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/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |