bash 2.05a.0(2) console "misbehaving" on w2k

bash 2.05a.0(2) console "misbehaving" on w2k

[Greg Fenton]

I recently upgraded BASH (don't know the previous version I had...).

Now when I run some programs, BASH misbehaves.

In particular, I have two programs which stand out:

Using the command-line P4 to submit, P4 calls vim to edit my
submission entry.  Prior to the upgrade, everything worked flawlessly.
Now, when in VIM, the console is all messed up.  VIM does not
appear in Command Mode at all.  I start off in what appears to
be Insert Mode, but hitting ESC does not take me into Command Mode.

At first I thought that it might be VIM, but switching my P4EDITOR
value to another VI (Watcom VI), I get the exact same (bad) behaviour.

A second program is one I wrote myself.  I have code which clears
the console (works fine on the W2K "command prompt" consoles), and
it used to work fine in bash.  Since the upgrade, bash now seems
to have some type of buffering problem.  The screen clears, but
calls to printf(), fflush(stdout) and getch() get all confused.
Again, the program works fine in the W2K command shell.

The code I use to clear the screen is below.  I need to use code
which will work in the NT command shell as well as Cygwin's.

----
void ConsoleClear( void )
{
    HANDLE handle;
    CONSOLE_SCREEN_BUFFER_INFO info;
    COORD coord;
    DWORD dwTemp;

    SECURITY_ATTRIBUTES attr;
    attr.nLength = sizeof( attr );
    attr.lpSecurityDescriptor = NULL;
    attr.bInheritHandle = TRUE;

    coord.X = 0;
    coord.Y = 0;

    handle =  CreateFile( TEXT("CONOUT$"),
                          GENERIC_READ|GENERIC_WRITE,
                          FILE_SHARE_READ|FILE_SHARE_WRITE,
                          &attr,
                          OPEN_EXISTING,
                          (DWORD)0,
                          (HANDLE)0 );

    if( handle != INVALID_HANDLE_VALUE )
    {
        if( GetConsoleScreenBufferInfo( handle, &info ) )
        {
            // Fill the console with the space character starting from
0,0
            FillConsoleOutputCharacter( handle, (TCHAR)' ',
                                        info.dwSize.X * info.dwSize.Y,
                                        coord, &dwTemp );
            // Put the cursor back the 0,0 position
            SetConsoleCursorPosition( handle, coord );
        }

        CloseHandle( handle );
    }
}

----

Suggestions as to what might be causing this?

Thanks in advance,
greg_fenton.

=====
Greg Fenton
greg_fenton@yahoo.com

__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/

--
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/

Re: bash 2.05a.0(2) console "misbehaving" on w2k

[Larry Hall (RFK Partners, Inc)]

At 11:00 AM 1/8/2002, Greg Fenton wrote:
>I recently upgraded BASH (don't know the previous version I had...).
>
>Now when I run some programs, BASH misbehaves.
>
>In particular, I have two programs which stand out:
>
>Using the command-line P4 to submit, P4 calls vim to edit my
>submission entry.  Prior to the upgrade, everything worked flawlessly.
>Now, when in VIM, the console is all messed up.  VIM does not
>appear in Command Mode at all.  I start off in what appears to
>be Insert Mode, but hitting ESC does not take me into Command Mode.
>
>At first I thought that it might be VIM, but switching my P4EDITOR
>value to another VI (Watcom VI), I get the exact same (bad) behaviour.
>
>A second program is one I wrote myself.  I have code which clears
>the console (works fine on the W2K "command prompt" consoles), and
>it used to work fine in bash.  Since the upgrade, bash now seems
>to have some type of buffering problem.  The screen clears, but
>calls to printf(), fflush(stdout) and getch() get all confused.
>Again, the program works fine in the W2K command shell.
>
>The code I use to clear the screen is below.  I need to use code
>which will work in the NT command shell as well as Cygwin's.
>
>----
>void ConsoleClear( void )
>{
>     HANDLE handle;
>     CONSOLE_SCREEN_BUFFER_INFO info;
>     COORD coord;
>     DWORD dwTemp;
>
>     SECURITY_ATTRIBUTES attr;
>     attr.nLength = sizeof( attr );
>     attr.lpSecurityDescriptor = NULL;
>     attr.bInheritHandle = TRUE;
>
>     coord.X = 0;
>     coord.Y = 0;
>
>     handle =  CreateFile( TEXT("CONOUT$"),
>                           GENERIC_READ|GENERIC_WRITE,
>                           FILE_SHARE_READ|FILE_SHARE_WRITE,
>                           &attr,
>                           OPEN_EXISTING,
>                           (DWORD)0,
>                           (HANDLE)0 );
>
>     if( handle != INVALID_HANDLE_VALUE )
>     {
>         if( GetConsoleScreenBufferInfo( handle, &info ) )
>         {
>             // Fill the console with the space character starting from
>0,0
>             FillConsoleOutputCharacter( handle, (TCHAR)' ',
>                                         info.dwSize.X * info.dwSize.Y,
>                                         coord, &dwTemp );
>             // Put the cursor back the 0,0 position
>             SetConsoleCursorPosition( handle, coord );
>         }
>
>         CloseHandle( handle );
>     }
>}
>
>----
>
>Suggestions as to what might be causing this?



Sounds like something or someone reset your TERM variable.



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/

Re: bash 2.05a.0(2) console "misbehaving" on w2k

[Greg Fenton]

"Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> wrote:
> 
> 
> Sounds like something or someone reset your TERM variable.
> 

$ echo $TERM
cygwin


That's the right value, correct?

greg_fenton.

=====
Greg Fenton
greg_fenton@yahoo.com

__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/

--
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/

Re: bash 2.05a.0(2) console "misbehaving" on w2k

[Larry Hall (RFK Partners, Inc)]

At 06:57 PM 1/8/2002, Greg Fenton wrote:
>"Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> wrote:
> > 
> > 
> > Sounds like something or someone reset your TERM variable.
> > 
>
>$ echo $TERM
>cygwin
>
>
>That's the right value, correct?


Yep, it is.  OK, maybe check your other terminal-related environment
variables to see if something looks off.  If not, I'm not sure what
the problem is.  But if it's affecting more than just Cygwin tools,
it has to be something like environment variables which all applications
can see, use, and change.



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/

Re: bash 2.05a.0(2) console "misbehaving" on w2k

[Greg Fenton]

"Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> wrote:
>
> Yep, it is.  OK, maybe check your other terminal-related environment
> variables to see if something looks off.  If not, I'm not sure what
> the problem is.  But if it's affecting more than just Cygwin tools,
> it has to be something like environment variables which all
> applications
> can see, use, and change.
> 

*SMACK!*

Thanks Larry for your replies...you've uncovered my foolishness...
I had added to the windows env a $CYGWIN setting when I last upgraded
BASH and had forgotten about it...sigh...

Thanks for your help!
greg_fenton.

=====
Greg Fenton
greg_fenton@yahoo.com

__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/

--
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/

Re: bash 2.05a.0(2) console "misbehaving" on w2k

[Larry Hall (RFK Partners, Inc)]

At 07:16 PM 1/8/2002, Greg Fenton wrote:
>"Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> wrote:
> >
> > Yep, it is.  OK, maybe check your other terminal-related environment
> > variables to see if something looks off.  If not, I'm not sure what
> > the problem is.  But if it's affecting more than just Cygwin tools,
> > it has to be something like environment variables which all
> > applications
> > can see, use, and change.
> > 
>
>*SMACK!*
>
>Thanks Larry for your replies...you've uncovered my foolishness...
>I had added to the windows env a $CYGWIN setting when I last upgraded
>BASH and had forgotten about it...sigh...
>
>Thanks for your help!


Glad to be of service!  Just out of curiosity, what was the environment
variable and the setting you added/were missing?



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/

Re: bash 2.05a.0(2) console "misbehaving" on w2k

[Greg Fenton]

"Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> wrote:
>
> At 07:16 PM 1/8/2002, Greg Fenton wrote:
> >
> >Thanks Larry for your replies...you've uncovered my foolishness...
> >I had added to the windows env a $CYGWIN setting when I last
> upgraded
> >BASH and had forgotten about it...sigh...
> [...]
> Glad to be of service!  Just out of curiosity, what was the
> environment
> variable and the setting you added/were missing?
> 

$ echo $CYGWIN
check_case:adjust title tty glob:ignorecase ntea

I haven't had a chance to lookup the reference for CYGWIN
to find out what this does...and I won't have time for a
while.

Thanks again,
greg_fenton.

=====
Greg Fenton
greg_fenton@yahoo.com

__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/

--
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/

Re: bash 2.05a.0(2) console "misbehaving" on w2k

[Larry Hall (RFK Partners, Inc)]

At 02:39 PM 1/9/2002, Greg Fenton wrote:

>"Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> wrote:
> >
> > At 07:16 PM 1/8/2002, Greg Fenton wrote:
> > >
> > >Thanks Larry for your replies...you've uncovered my foolishness...
> > >I had added to the windows env a $CYGWIN setting when I last
> > upgraded
> > >BASH and had forgotten about it...sigh...
> > [...]
> > Glad to be of service!  Just out of curiosity, what was the
> > environment
> > variable and the setting you added/were missing?
> > 
>
>$ echo $CYGWIN
>check_case:adjust title tty glob:ignorecase ntea
>
>I haven't had a chance to lookup the reference for CYGWIN
>to find out what this does...and I won't have time for a
>while.


OK.  I'm still a little confused though.  I'm not aware of any settings
in the CYGWIN environment variable that should affect VIM and especially
not any non-Cygwin version.  So, I'm glad you think I helped but it's 
not clear to me from the information provided that there was any real
Cygwin link for this issue.

OK, I'll drop the thread since it seems OT.

Glad you found a fix for your problem though.



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/