public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@cygnus.com>
To: cygwin <cygwin@sources.redhat.com>
Subject: Re: [BASH] Backtick problem still NOTsolved!! (Win95b/CW1.1.4)
Date: Thu, 05 Oct 2000 03:25:00 -0000	[thread overview]
Message-ID: <39DC5732.CA9D45A9@cygnus.com> (raw)
In-Reply-To: <003601c026a4$57944240$708106d5@default>

Andreas Eibach wrote:
> And I'm talking about  W  i  n  d  o  w  s     9 5  b   and not WinNT!
> So please don't tell me it works in WinNT - I believe you but it's no use
> for me!
> I only want _Win9x_ users to report if it works with a German keyboard!
> 
> Heck, this needs a fix!

Unfortunately I don't have a solution for you. Deadkeys are broken
on W95 with german keyboard. This is documented by Microsoft in their
knowledge base, case Q140456:

http://support.microsoft.com/support/kb/articles/Q140/4/56.asp

They don't have a solution for that problem either, except for
noting: "This problem was corrected in Windows 2000."

The problem is that when reading the keyboard, every other Windows
reports the correct backtick ASCII character when pressing the
space key. In W95 with german keyboard, it returns _always_ ASCII
code 0x00 when pressing backtick as well as the following space,
unfortunately.

However, as a workaround you might think of installing inetd so that
telnetd works on your machine. Then you will be able to use a good
telnet client (I have very good experiences with TeraTerm:
http://hp.vector.co.jp/authors/VA002416/teraterm.html ) to login to
localhost. In that terminal sessions you will be able to press the
backtick as well since the Windows console code isn't used then.

Sorry to have no better news,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                        mailto:cygwin@sources.redhat.com
Red Hat, Inc.
mailto:vinschen@cygnus.com

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

  parent reply	other threads:[~2000-10-05  3:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-24 15:02 Can't abort command line with Ctrl-C anymore Paul Johnston
2000-09-25  1:09 ` [BASH] Backtick problem still NOTsolved!! (Win95b/CW1.1.4) Andreas Eibach
2000-09-25  2:00   ` Corinna Vinschen
2000-09-25  5:09     ` Andreas Eibach
2000-09-25  5:43     ` [BASH] Backtick problem still NOTsolved! [STRACE output inside] Andreas Eibach
2000-10-05  3:25   ` Corinna Vinschen [this message]
2000-10-05  3:33     ` [BASH] Backtick problem still NOTsolved!! (Win95b/CW1.1.4) Corinna Vinschen
2000-10-06 12:01     ` Andreas Eibach
2000-10-06 12:03     ` Andreas Eibach
2000-09-25  8:55 ` Can't abort command line with Ctrl-C anymore Chris Faylor

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=39DC5732.CA9D45A9@cygnus.com \
    --to=vinschen@cygnus.com \
    --cc=cygwin@sources.redhat.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).