This is the mail archive of the
mailing list for the Cygwin project.
Please make sure your mailer respects the Reply-To: header.
Also, if advice given by someone on the Cygwin list helped you, it's
usually a good idea to post a followup to the list stating this, just to
bring things to a closure, so that others searching the archives will see
what worked and what didn't. Hence, I'm directing this reply to the
On Thu, 8 Jan 2004, H. James de St. Germain wrote:
> thanks for the info about rxvt.
Sure. You might want to invoke it via 'SHELL=bash rxvt', so that you get
it to run 'bash' instead of 'sh'.
> i don't have a winsup directory (didn't compile cygwin from src)
> so fixing fhandler_console.cc might be more than i want to attempt.
> strange though, you would think that if it were that easy the
> developers would have already fixed it...
They probably all use vi. :-) Or emacs in rxvt or xterm. In other words,
bugs don't get fixed until someone's motivated enough to fix them. You
can still try to submit a patch (after testing it, of course, and filling
out the copyright assignment -- see <http://cygwin.com/contrib.html>).
> anyway, again i appreciate your response and the nice work
Glad I could help.
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html