From: Brian Ford <ford@vss.fsi.com>
To: cygwin@cygwin.com
Subject: Re: ctrl-c in rxvt
Date: Fri, 12 Sep 2003 16:18:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.56.0309121116290.685@eos> (raw)
On Fri, Sep 12, 2003, Rick Rankin wrote:
> Many thanks. Did the fix make it into last night's snapshot?
By looking at the ChangeLog link for that snapshot, I'd say it did. Use
the source, Luke :).
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2003-09-12 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 16:18 Brian Ford [this message]
2003-09-12 17:53 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 18:39 Patrick Peralta
2003-09-11 23:02 Patrick Peralta
2003-09-11 23:18 ` Christopher Faylor
2003-09-12 0:32 ` Rick Rankin
2003-09-12 0:41 ` Christopher Faylor
2003-09-12 4:54 ` Rick Rankin
2003-09-12 6:43 ` Christopher Faylor
2003-09-12 11:50 ` Norman Vine
2003-09-12 16:06 ` Rick Rankin
2003-09-12 16:43 ` Rick Rankin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.56.0309121116290.685@eos \
--to=ford@vss.fsi.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).