On Sat, Feb 20, 2016 at 8:37 AM, David Macek <david.mace...@gmail.com>
wrote:
> On 18. 2. 2016 22:21, Greg Jung wrote:
> > I just tried it, and it is messing with my previously happy usage
> > of CMD.exe using target: C:\msys64usr\bin\bash.exe --login -i.
>
> Can you elaborate? I removed the `TERM=xterm` line, ran `cmd.exe`, inside
> ran `bash.exe --login -i`. Line editing worked fine. `echo $TERM` showed
> `cygwin`.
>
> > Without that TERM=xterm I don't even have line editing. However
> > I can unset TERM in the ./bashrc file and I get the line-edit
> > and completion behavior and benefits of an unset TERM.
>
>
>
> --
> David Macek
>
ok I start a "raw" CMD shell
Target: %windir%\system32\cmd.exe /F:ON /A
> Microsoft Windows [Version 6.1.7601]
>
> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
>
>
>> D:\cmd>C:\usr\bin\bash.exe --login -i
>
> C:\usr\bin\bash.exe: --: bad option
>
>
>> D:\cmd>C:\usr\bin\bash.exe -login -i
>
> bash$ echo $PATH
>
> D:\Tcl\bin:C:\ProgramData\Oracle\Java\javapath:C:\Program Files
>> (x86)\NVIDIA Corporation\PhysX
>
> ndowsPowerShell\v1.0\:C:\Windows\System32\WindowsPowerShell\v1.0\:C:\Program
>> Files\doxygen\bin
>
> on27:E:\python27\Tools\Scripts:C:\Program Files\Intel\DMIX:C:\Program
>> Files (x86)\Windows Kits
>
> x86)\gnuplot\bin:C:\ProgramData\Oracle\Java\javapath:C:\Program Files
>> (x86)\NVIDIA Corporation
>
> m32\WindowsPowerShell\v1.0\:C:\Windows\System32\WindowsPowerShell\v1.0\:C:\Program
>> Files\doxyg
>
> bash$ exit
>
> logout
>
>
>> D:\cmd>C:\msys64\usr\bin\bash.exe --login -i
>
> C:/msys64/home/greg/.bashrc invoked
>
> WINHOME=C:\Users\greg
>
> GDLHOME=D:/home/greg
>
>
>> greg@Homerw7 ~
>
> $ echo $TERM
>
>
>>
>> greg@Homerw7 ~
>
> Microsoft Windows [Version 6.1.7601]
>
> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
>
>
>> D:\cmd>C:\usr\bin\bash.exe --login -i
>
> C:\usr\bin\bash.exe: --: bad option
>
>
>> D:\cmd>C:\usr\bin\bash.exe -login -i
>
> bash$ echo $PATH
>
> D:\Tcl\bin:C:\ProgramData\Oracle\Java\javapath:C:\Program Files
>> (x86)\NVIDIA Corporation\PhysX
>
> ndowsPowerShell\v1.0\:C:\Windows\System32\WindowsPowerShell\v1.0\:C:\Program
>> Files\doxygen\bin
>
> on27:E:\python27\Tools\Scripts:C:\Program Files\Intel\DMIX:C:\Program
>> Files (x86)\Windows Kits
>
> x86)\gnuplot\bin:C:\ProgramData\Oracle\Java\javapath:C:\Program Files
>> (x86)\NVIDIA Corporation
>
> m32\WindowsPowerShell\v1.0\:C:\Windows\System32\WindowsPowerShell\v1.0\:C:\Program
>> Files\doxyg
>
> bash$ exit
>
> logout
>
>
>> D:\cmd>C:\msys64\usr\bin\bash.exe --login -i
>
> C:/msys64/home/greg/.bashrc invoked
>
> WINHOME=C:\Users\greg
>
> GDLHOME=D:/home/greg
>
>
>> greg@Homerw7 ~
>
> $ echo $TERM
>
>
>>
>> greg@Homerw7 ~
>
>
$ vi /etc/profile # remove the TERM= line
> greg@Homerw7 ~
$ # (good vi performance)
$ vi ./.bashrc # remove the "unset TERM" line
> greg@Homerw7 ~
> $ head -10 .bashrc
> # .bashrc for invoking msys directly
> #
> echo C:/msys64/home/greg/.bashrc invoked
> export WINHOME=${HOMEDRIVE}${HOMEPATH}
> export GDLHOME=D:/home/greg
> echo WINHOME=$WINHOME
> echo GDLHOME=$GDLHOME
> #unset TERM
> greg@Homerw7 ~
> $ exit
> logout
> 'unknown': I need something more specific.
>
back in CMD.exe: /etc/profile edited to leave TERM alone. also .bashrc
> D:\cmd>C:\msys64\usr\bin\bash.exe --login -i
> C:/msys64/home/greg/.bashrc invoked
> WINHOME=C:\Users\greg
> GDLHOME=D:/home/greg
> greg@Homerw7 ~
> $ env | grep TERM
> TERM=win32con
> GNUTERM=windows
>
greg@Homerw7 ~
$ 1234 then four backspaces$ then four backspaacesracesracesoaceswaces$
> then four backspa
bash: syntax error near unexpected token `then'
(and a few arrows. line goes crazy)
> greg@Homerw7 ~
>> $ vi .bashrc
> Unrecognized TERM type
>
> greg@Homerw7 ~
> $ sed 's;#unset TERM;export TERM=cygwin;' -i .bashrc
>
> greg@Homerw7 ~
> $ exit
> logout
> 'win32con': unknown terminal type.
>
> D:\cmd>C:\msys64\usr\bin\bash.exe --login -i
> C:/msys64/home/greg/.bashrc invoked
> WINHOME=C:\Users\greg
> GDLHOME=D:/home/greg
>
> greg@Homerw7 ~
> $ ls
> _viminfo gccver list run32 savetest/ stattest.c
> bashman.ls gvpd mainw.c run64 savetest.sh* test/
> echo.c htmlhelp.def pks savename/ Spoon-Knife/
>
# OK Now with TERM=cygwin editing and completion are working
> greg@Homerw7 ~
> $ alias vi
> alias vi='/c/usr/bin/vi.exe'
>
> (an old vi from unixutils)
> greg@Homerw7 ~
> $ vi .bashrc
> Unrecognized TERM type
>
> greg@Homerw7 ~
> $ /usr/bin/vim .bashrc
>
> greg@Homerw7 ~
>
Try it from the shortcut:
> greg@Homerw7 ~
>
> $ env | grep TERM
>
> TERM=cygwin
>
> GNUTERM=windows
>
>
> And this setting does a good vi session with /usr/bin/vim
>
so it was the win32con setting that messed me up. Which I see is set
in my Win7 environment.
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Msys2-users mailing list
Msys2-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/msys2-users
