Re: Couple of nits about Cygwin

Re: Couple of nits about Cygwin

[Earnie Boyd]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

--- DJ Delorie <dj@delorie.com> wrote:
> 
> >  1. When you start a bash shell, the cursor flashes at a reasonable 
> > rate, but when you start typing it generally disappears from view. 
> 
> This has always bothered me, but I always thought it was NT doing it.
> Testing in the MS-DOS window shows that it's not NT.  Sigh.
> 

Huh, I've never experienced this.  WinNT 4, sp 4.

Cheers,

=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail – Free email you can access from anywhere!
http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Earnie Boyd]

--- Chris Faylor <cgf@cygnus.com> wrote:
-8<-
> 
> Unfortunately, I can.
> 

Are you sure you're using ash for sh?  I don't see the problem with sh at all. 
However, I do see it with zsh which has it's own input routines (i.e. doesn't
use readline).

Cheers,

=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Robert Collins]

I saw it with bash, and vim but Chris's fix fixed it for me

win2k pro, two machines

Rob
----- Original Message -----
From: "Earnie Boyd" <earnie_boyd@yahoo.com>
To: <cygwin@sources.redhat.com>
Sent: Friday, July 28, 2000 11:26 PM
Subject: Re: Couple of nits about Cygwin


> --- Chris Faylor <cgf@cygnus.com> wrote:
> -8<-
> >
> > Unfortunately, I can.
> >
>
> Are you sure you're using ash for sh?  I don't see the problem with sh at
all.
> However, I do see it with zsh which has it's own input routines (i.e.
doesn't
> use readline).
>
> Cheers,
>
> =====
> ---
>    Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
>             __Cygwin: POSIX on Windows__
> Cygwin Newbies: < http://gw32.freeyellow.com/ >
>            __Minimalist GNU for Windows__
>   Mingw32 List: < http://www.egroups.com/group/mingw32/ >
>     Mingw Home: < http://www.mingw.org/ >
>
> __________________________________________________
> Do You Yahoo!?
> Kick off your party with Yahoo! Invites.
> http://invites.yahoo.com/
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Chris Faylor]

On Fri, Jul 28, 2000 at 11:39:57PM +1000, Robert Collins wrote:
>I saw it with bash, and vim but Chris's fix fixed it for me

I can't take credit for the fix. DJ figured it out.

The loss of cursor has been a problem with cygwin for some time.

I probably aggravated the problem when I changed console input to
be more UNIX-like, allowing CTRL-D to terminate input, and getting
stty commands to work.

When you type a bunch of characters, the cursor disappears for a time.
I saw this on Windows 2K under ash.  I was specifically looking for this
because I was going to investigate a readline alternative, myself.

Of course, fixing readline doesn't solve the problem for programs that
don't use readline.  DJ's patch seemed to be the most generic fix for
the problem.

Of course, I'm not seeing any irritating cursor behavior, either.

cgf

>win2k pro, two machines
>
>Rob
>----- Original Message -----
>From: "Earnie Boyd" <earnie_boyd@yahoo.com>
>To: <cygwin@sources.redhat.com>
>Sent: Friday, July 28, 2000 11:26 PM
>Subject: Re: Couple of nits about Cygwin
>
>
>> --- Chris Faylor <cgf@cygnus.com> wrote:
>> -8<-
>> >
>> > Unfortunately, I can.
>> >
>>
>> Are you sure you're using ash for sh?  I don't see the problem with sh at
>all.
>> However, I do see it with zsh which has it's own input routines (i.e.
>doesn't
>> use readline).
>>
>> Cheers,
>>
>> =====
>> ---
>>    Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
>>             __Cygwin: POSIX on Windows__
>> Cygwin Newbies: < http://gw32.freeyellow.com/ >
>>            __Minimalist GNU for Windows__
>>   Mingw32 List: < http://www.egroups.com/group/mingw32/ >
>>     Mingw Home: < http://www.mingw.org/ >
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Kick off your party with Yahoo! Invites.
>> http://invites.yahoo.com/
>>
>> --
>> Want to unsubscribe from this list?
>> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>>
>>
>
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com

-- 
cgf@cygnus.com                        Cygnus Solutions, a Red Hat company
http://sourceware.cygnus.com/         http://www.redhat.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Robert Collins]

> On Fri, Jul 28, 2000 at 11:39:57PM +1000, Robert Collins wrote:
> >I saw it with bash, and vim but Chris's fix fixed it for me
> 
> I can't take credit for the fix. DJ figured it out.

Sorry DJ! I saw both patches go by - I only tried the second :-]


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Kendall Bennett]

Chris Faylor <cgf@cygnus.com> wrote:

> The loss of cursor has been a problem with cygwin for some time.
> 
> I probably aggravated the problem when I changed console input to
> be more UNIX-like, allowing CTRL-D to terminate input, and getting
> stty commands to work.
> 
> When you type a bunch of characters, the cursor disappears for a time.
> I saw this on Windows 2K under ash.  I was specifically looking for this
> because I was going to investigate a readline alternative, myself.
> 
> Of course, fixing readline doesn't solve the problem for programs that
> don't use readline.  DJ's patch seemed to be the most generic fix for
> the problem.

Yep, and it seems to be working nicely. However I did notice that if 
you telnet to another box (a local Linux box in my case), the cursor 
problem is not completely resolved. The cursor 'sort-of' disappears 
when you cursor through the command line, but it comes back almost 
instantly when you take your finger off the cursor key.

I suspect this has something to do with the network latency involed 
in telnetting to another machine?

Regards,

+---------------------------------------------------------------+
|   SciTech Software - Building Truly Plug'n'Play Software!     |
+---------------------------------------------------------------+
| Kendall Bennett          | Email: KendallB@scitechsoft.com    |
| Director of Engineering  | Phone: (530) 894 8400              |
| SciTech Software, Inc.   | Fax  : (530) 894 9069              |
| 505 Wall Street          | ftp  : ftp.scitechsoft.com         |
| Chico, CA 95928, USA     | www  : http://www.scitechsoft.com  |
+---------------------------------------------------------------+


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Earnie Boyd]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

--- Kendall Bennett <KendallB@scitechsoft.com> wrote:
>  2. Bash seems a lot slower at responding to commands than a regular 
> command shell on NT. Bash on Linux is very responsive, so it must be 
> something inherent in Cygwin. Is this something that is a known 
> issue? I assume it would be solved already if it was simple, so I am 
> mostly curious.
> 

Blame Cygwin for that.  It has a lot of string manipulation to do.  I will add
that some of the slowness has been eliminated in recent snapshots.

Regards,

=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail – Free email you can access from anywhere!
http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: "which" bug

[Earnie Boyd]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

--- David Starks-Browning <starksb@ebi.ac.uk> wrote:
> On Friday 21 Jul 00, Earnie Boyd writes:
> > how to find out if a binary is using the
> > cygwin1.dll, etc?
> 
> You'll have to tell me how.  (I've always just *known*.)
> 

cygcheck foo.exe

If the output list contains cygwin1.dll then it uses it.

Cheers,

=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail – Free email you can access from anywhere!
http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Couple of nits about Cygwin

[Kendall Bennett]

Hi Guys,

I have a couple of nits that I would like to pick about Cygwin. 
Mostly I am trying to find out if anyone knows what causes this, and 
if there is something that could be done about it. If I can zero in 
on the problem code, I would be willing to take a look at this myself.

 1. When you start a bash shell, the cursor flashes at a reasonable 
rate, but when you start typing it generally disappears from view. 
Normally in NT when you start typing something, the cursor remains as 
a solid block vertical bar until you stop typing, so you can tell 
where you are at. Ie: with bash if you start using the arrow keys to 
move around in the command line, you have to pause every so often to 
let the cursor flash so you can see where you are at! Any ideas on 
how to fix this? 
 
 2. Bash seems a lot slower at responding to commands than a regular 
command shell on NT. Bash on Linux is very responsive, so it must be 
something inherent in Cygwin. Is this something that is a known 
issue? I assume it would be solved already if it was simple, so I am 
mostly curious.

Regards,

+---------------------------------------------------------------+
|   SciTech Software - Building Truly Plug'n'Play Software!     |
+---------------------------------------------------------------+
| Kendall Bennett          | Email: KendallB@scitechsoft.com    |
| Director of Engineering  | Phone: (530) 894 8400              |
| SciTech Software, Inc.   | Fax  : (530) 894 9069              |
| 505 Wall Street          | ftp  : ftp.scitechsoft.com         |
| Chico, CA 95928, USA     | www  : http://www.scitechsoft.com  |
+---------------------------------------------------------------+


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[DJ Delorie]

>  1. When you start a bash shell, the cursor flashes at a reasonable 
> rate, but when you start typing it generally disappears from view. 

This has always bothered me, but I always thought it was NT doing it.
Testing in the MS-DOS window shows that it's not NT.  Sigh.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Kendall Bennett]

DJ Delorie <dj@delorie.com> wrote:

> >  1. When you start a bash shell, the cursor flashes at a reasonable 
> > rate, but when you start typing it generally disappears from view. 
> 
> This has always bothered me, but I always thought it was NT doing
> it. Testing in the MS-DOS window shows that it's not NT.  Sigh. 

No, it is definately not NT. If I telnet from a regular command 
prompt to a Linux box the cursor works fine. However telnetting from 
a bash shell has the same problem as the bash shell itself.

Also I noticed that the cursor block is slightly larger than a 
regular NT command prompt window.

Any ideas about what would be causing this? I assume that bash goes 
through the curses library to access the NT console, so perhaps this 
is a bug in the NT version of curses? That might be an easy place to 
try and track this down...

Regards,

+---------------------------------------------------------------+
|   SciTech Software - Building Truly Plug'n'Play Software!     |
+---------------------------------------------------------------+
| Kendall Bennett          | Email: KendallB@scitechsoft.com    |
| Director of Engineering  | Phone: (530) 894 8400              |
| SciTech Software, Inc.   | Fax  : (530) 894 9069              |
| 505 Wall Street          | ftp  : ftp.scitechsoft.com         |
| Chico, CA 95928, USA     | www  : http://www.scitechsoft.com  |
+---------------------------------------------------------------+


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[DJ Delorie]

>  1. When you start a bash shell, the cursor flashes at a reasonable 
> rate, but when you start typing it generally disappears from view. 

Found it.  WriteFile() to the console causes the cursor to dissapear
for a bit.  Setting the cursor position makes it show up again.  Try
the attached patch (I'll try it myself later, but the machine is in
the middle of a big build I don't want to interrupt).

Index: fhandler_console.cc
===================================================================
RCS file: /cvs/src/src/winsup/cygwin/fhandler_console.cc,v
retrieving revision 1.9
diff -p -2 -r1.9 fhandler_console.cc
*** fhandler_console.cc	2000/07/04 02:26:20	1.9
--- fhandler_console.cc	2000/07/26 00:17:37
*************** fhandler_console::write (const void *vsr
*** 1237,1240 ****
--- 1237,1242 ----
    syscall_printf ("%d = write_console (,..%d)", len, len);
  
+   cursor_rel (0,0); /* to make cursor appear on the screen immediately */
+ 
    return len;
  }

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Chris Faylor]

On Tue, Jul 25, 2000 at 08:19:22PM -0400, DJ Delorie wrote:
>
>>  1. When you start a bash shell, the cursor flashes at a reasonable 
>> rate, but when you start typing it generally disappears from view. 
>
>Found it.  WriteFile() to the console causes the cursor to dissapear
>for a bit.  Setting the cursor position makes it show up again.  Try
>the attached patch (I'll try it myself later, but the machine is in
>the middle of a big build I don't want to interrupt).

That seems to do it.  Thanks!  This problem has plagued Cygwin for
years.

I think it makes more sense for this to be in fhandler_console::read,
though.  Otherwise you're forcing the cursor to track every write, which
probably defeats the purpose of making it invisible for a while.

Putting it in the console read part means that the cursor is made
visible when cygwin is ready to receive input.

The change below just moves your code to the input part of cygwin rather
than the output.  It seems to work as well as putting it in the write
part.

Thanks again.  This problem was particularly noticeable on Windows 2K.
I've been meaning to investigate it for a while.

cgf

Index: fhandler_console.cc
===================================================================
RCS file: /cvs/src/src/winsup/cygwin/fhandler_console.cc,v
retrieving revision 1.11
diff -u -p -r1.11 fhandler_console.cc
--- fhandler_console.cc	2000/07/10 23:08:45	1.11
+++ fhandler_console.cc	2000/07/26 01:35:49
@@ -145,6 +145,7 @@ fhandler_console::read (void *pv, size_t
       if ((bgres = bg_check (SIGTTIN)) <= 0)
 	return bgres;
 
+      cursor_rel (0,0); /* to make cursor appear on the screen immediately */
       switch (WaitForMultipleObjects (nwait, w4, FALSE, INFINITE))
 	{
 	case WAIT_OBJECT_0:

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[DJ Delorie]

> I think it makes more sense for this to be in fhandler_console::read,
> though.  Otherwise you're forcing the cursor to track every write, which
> probably defeats the purpose of making it invisible for a while.

Sounds good to me.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Kazuhiro Fujieda]

>>> On Tue, 25 Jul 2000 21:37:50 -0400
>>> Chris Faylor <cgf@cygnus.com> said:

> The change below just moves your code to the input part of cygwin rather
> than the output.  It seems to work as well as putting it in the write
> part.

I'm afraid I don't like this solution. I'm annoyed with the
cursor flushing every time I type something. I prefer solving
this problem in the configuration of readline included in bash
as the following. This solution makes the cursor flush on using
the right arrow key.

--- bash/lib/readline/rlconf.h-	Fri Jul 28 08:03:08 2000
+++ bash/lib/readline/rlconf.h	Fri Jul 28 08:11:11 2000
@@ -45,7 +45,7 @@
 
 /* If defined, use the terminal escape sequence to move the cursor forward
    over a character when updating the line rather than rewriting it. */
-/* #define HACK_TERMCAP_MOTION */
+#define HACK_TERMCAP_MOTION
 
 /* The string inserted by the `insert comment' command. */
 #define RL_COMMENT_BEGIN_DEFAULT "#"

____
  | AIST      Kazuhiro Fujieda <fujieda@jaist.ac.jp>
  | HOKURIKU  School of Information Science
o_/ 1990      Japan Advanced Institute of Science and Technology

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Chris Faylor]

On Fri, Jul 28, 2000 at 08:18:10AM +0900, Kazuhiro Fujieda wrote:
>>>> On Tue, 25 Jul 2000 21:37:50 -0400
>>>> Chris Faylor <cgf@cygnus.com> said:
>
>> The change below just moves your code to the input part of cygwin rather
>> than the output.  It seems to work as well as putting it in the write
>> part.
>
>I'm afraid I don't like this solution. I'm annoyed with the
>cursor flushing every time I type something. I prefer solving
>this problem in the configuration of readline included in bash
>as the following. This solution makes the cursor flush on using
>the right arrow key.

Except that this has nothing to do with readline or termcap.

The problem shows up in /bin/sh, too.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Kazuhiro Fujieda]

>>> On Thu, 27 Jul 2000 19:28:30 -0400
>>> Chris Faylor <cgf@cygnus.com> said:

> Except that this has nothing to do with readline or termcap.
> The problem shows up in /bin/sh, too.

I recognize the problem is that we can't see the position of the
cursor when we move it around the command line with the arrow
keys. My solution can solve this problem at least in bash.
I can't observe it in /bin/sh on NT4 Sp6a.
____
  | AIST      Kazuhiro Fujieda <fujieda@jaist.ac.jp>
  | HOKURIKU  School of Information Science
o_/ 1990      Japan Advanced Institute of Science and Technology

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Chris Faylor]

On Fri, Jul 28, 2000 at 09:23:35AM +0900, Kazuhiro Fujieda wrote:
>>>> On Thu, 27 Jul 2000 19:28:30 -0400
>>>> Chris Faylor <cgf@cygnus.com> said:
>
>> Except that this has nothing to do with readline or termcap.
>> The problem shows up in /bin/sh, too.
>
>I recognize the problem is that we can't see the position of the
>cursor when we move it around the command line with the arrow
>keys. My solution can solve this problem at least in bash.
>I can't observe it in /bin/sh on NT4 Sp6a.

Unfortunately, I can.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Couple of nits about Cygwin

[Kendall Bennett]

DJ Delorie <dj@delorie.com> wrote:

> >  1. When you start a bash shell, the cursor flashes at a reasonable 
> > rate, but when you start typing it generally disappears from view. 
> 
> Found it.  WriteFile() to the console causes the cursor to dissapear
> for a bit.  Setting the cursor position makes it show up again.  Try
> the attached patch (I'll try it myself later, but the machine is in
> the middle of a big build I don't want to interrupt).

Aha! Excellent stuff!

Unfortunately I only just re-installed Cygwin again and I don't have 
a build environment set up so I can't try the patch myself. It looks 
like Chris Faylor made a few changes also to clean it up.

I assume this will make it into the next public DLL build? Any idea 
when that would be? I might try apply Chris's patch on my system to 
see if I can get it all to build myself.

Regards,

+---------------------------------------------------------------+
|   SciTech Software - Building Truly Plug'n'Play Software!     |
+---------------------------------------------------------------+
| Kendall Bennett          | Email: KendallB@scitechsoft.com    |
| Director of Engineering  | Phone: (530) 894 8400              |
| SciTech Software, Inc.   | Fax  : (530) 894 9069              |
| 505 Wall Street          | ftp  : ftp.scitechsoft.com         |
| Chico, CA 95928, USA     | www  : http://www.scitechsoft.com  |
+---------------------------------------------------------------+


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com