From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Oracle SQLPLUS and the latest release Kill a line (control U default) not working
Date: Sat, 2 May 2020 12:44:36 +0200 [thread overview]
Message-ID: <bbe25691-ecf7-f62c-add9-d0e03c065c03@gmail.com> (raw)
In-Reply-To: <1588260874963-0.post@n5.nabble.com>
Am 30.04.2020 um 17:34 schrieb jsteifel:
> I'm totally frustrated by this. I do not want to have to add this to all the
> systems I have since I don't have a development env setup with compilers, I
> am finding the shift key doesn't work at all.
that is strange, can you clarify the conditions ?
>
> I have an older version of cygwin, no problem. Why is it a problem now. Why
> would the new code require this, yet the old works fine?
>
> I am finding this new env to be more windows like in a few areas than Nix
> like.
>
> What is it that drove the developers to take this action and make it
> incompatible with forked processes?
>
it is usually adding features or trying to correct mistakes,
unfortunately it is almost impossible to test all NOT cygwin
applications.
So about your problem:
- under Mintty, what setting are you using as Keyboard Features ?
- Are you runnign SQLPLUS locally or remote ?
- Have you tested the "set CYGWIN=disable_pcon" before running
Cygwin ? https://cygwin.com/cygwin-ug-net/using-cygwinenv.html
It will be nice to have a bit more of description of the problem
and of your Windows system
as mentioned on https://cygwin.com/problems.html
please provide the cygcheck.out as attachment.
Regards
Marco
Regards
Marco
Regards
prev parent reply other threads:[~2020-05-02 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 18:44 jsteifel
2020-03-17 19:42 ` Brian Inglis
2020-03-18 14:54 ` jsteifel
2020-04-30 15:34 ` jsteifel
2020-05-02 10:44 ` Marco Atzeri [this message]
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=bbe25691-ecf7-f62c-add9-d0e03c065c03@gmail.com \
--to=marco.atzeri@gmail.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).