On Thu, 3 Oct 2002, Kris Warkentin wrote:
> This has been bugging me for a while and I think I've finally got it to a
> repeatable case.
>
> Suppose I have a function in my .profile like so:
>
> vi(){
> /cygdrive/d/vim/vim60/gvim.exe `for file in $* ; do cygpath -w $file ; done` &
> }
>
> If I do something like 'vi /usr/include/std<tab>' (<tab> for command
> completion), as soon as it returns to the prompt (immediately because of the
> '&'), the terminal says 'logout'. As soon as I exit the last gvim running
> on this terminal, the terminal goes away. It seems more repeatable if the
> command completion didn't work the first time, that is, not enough had been
> typed to complete yet.
>
> Anyone else seen this behaviour?
>
> Kris
Kris,
I don't see this behavior on Win2k SP2, bash 2.05b-5... Try putting the
whole gvim invocation line (including the '&') in parentheses (it'll
force the invocation into a subshell), and see if this helps...
Otherwise, please post the version of Cygwin and bash you have, and which
OS you're running on...
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ [EMAIL PROTECTED]
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Water molecules expand as they grow warmer" (C) Popular Science, Oct'02, p.51
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
