From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Bug in Control-d handling?
Date: Mon, 20 Jun 2022 19:12:27 +0200 [thread overview]
Message-ID: <87zgi7fedg.fsf@Rainer.invalid> (raw)
In-Reply-To: <20220620192223.2e0a084a7c093939b1c7c8d6@nifty.ne.jp> (Takashi Yano's message of "Mon, 20 Jun 2022 19:22:23 +0900")
Takashi Yano writes:
> Ah, I confirmed that System V (Solaris 11.4) behaves like that.
> Does cygwin aim for System V compatibility???
Not that I know of, but even if it ever was: the current guideline is
IIRC that if something is unspecified or implementation dependent, then
Cygwin should adhere to what Linux does if possible.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2022-06-20 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 19:08 Ken Brown
2022-06-20 8:59 ` Takashi Yano
2022-06-20 10:22 ` Takashi Yano
2022-06-20 13:24 ` Ken Brown
2022-06-20 13:53 ` Eliot Moss
2022-06-20 17:50 ` Ken Brown
2022-07-04 8:10 ` Corinna Vinschen
2022-06-20 17:12 ` Achim Gratz [this message]
2022-06-20 19:22 ` Brian Inglis
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=87zgi7fedg.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).