Can't abort command line with Ctrl-C anymore...

Can't abort command line with Ctrl-C anymore...

[Paul Johnston]

Hi, I've just upgraded from B20 to net release 1.1.4 (latest, as of today).
Nice install!  Anyway, when I type a command ctrl-c does not abort it.
Ctrl-C still works to interrupt a running process, but I can't bail out of a
command without using the backspace key.  Is this a setting or has the
behavior of bash changed?  I'm on NT4.

Thanks for your help on such a small issue,

Paul

---------------------------------------
 Cygwin DLL version info:
     dll major: 1001
     dll minor: 4
     dll epoch: 19
     dll bad signal mask: 19005
     dll old termios: 5
     api major: 0
     api minor: 26
     shared data: 3
     dll identifier: cygwin1
     mount registry: 2
     cygnus registry name: Cygnus Solutions
     cygwin registry name: Cygwin
     program options name: Program Options
     cygwin mount registry name: mounts v2
     build date: Thu Aug 3 20:53:46 EDT 2000
     CVS tag: cygwin-1-1-4
     shared id: cygwin1S3


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

[BASH] Backtick problem still NOTsolved!! (Win95b/CW1.1.4)

[Andreas Eibach]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]

Hi,

after trying and trying, I MUST be sure this _is_ a bug in Cygwin!!

Despite trying all the things I read here, the problem PERSISTS!

 - Win95 b (and NOT WindowsNT, where Joerg Schaible reported that it
*does*work there,
 so it's a Win9x-only (Win95-only?) problem!)
 - Cygwin 1.1.4
 - GERMAN Keyboard layout

The "backtick" is the key that's used for executing commands in a shell
script.
It works on the dos editor EDIT.COM, but it doesn't work on the cygwin
bash command line!!!

But to test a one-liner, I'd *like* to test it on the command-line first!

administrator@DEFAULT $ ls-al `which bash`
requires backticks and DOESN'T WORK!
(Well I do know that you can also do it by $(     ) but I want to get my
backticks
working finally, damnit.)

So what I need to do instead?
-> Launch EDIT.COM
#!/bin/sh
ls-al `which bash`

save as ... say "temp".

administrator@DEFAULT $ ./temp
-rwxr-xr-x    1    administ    unknown     466944   Jun 2    00:50
/bin/bash

Somewhat awkward, but what the hell should I do if everybody says "it's
already solved". It's NOT.

2)  Read http://sources.redhat.com/cygwin/cygwin-ug-net/setup-files.html

3) Made aware that I'm not a beginner and I do know I need to press SPACE
after a "dead-key". ;)
4) Created .inputrc with the settings described there (2).
5) Verified that .inputrc does only contain LF's and no CR/LF pairs.
6) Put .inputrc in /home/administrator.

7) RESTART CYGWIN  .... and .... surprise, surprise...
8) Typed  <SHIFT-accent><SPACE>  --- No backticks despite pressing space!

++++++++++++++++++++++++
Umlauts work - but no backticks!
++++++++++++++++++++++++

And what is bash without  the backtick?

In EDIT.COM I can get a "French e accent aigu" (é)
in bash I cannot!!

So don't tell me this works.
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!

/Please/.

Andreas



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

Re: [BASH] Backtick problem still NOTsolved!! (Win95b/CW1.1.4)

[Corinna Vinschen]

Andreas Eibach wrote:
> after trying and trying, I MUST be sure this _is_ a bug in Cygwin!!
> 
> Despite trying all the things I read here, the problem PERSISTS!
> 
>  - Win95 b (and NOT WindowsNT, where Joerg Schaible reported that it
> *does*work there,
>  so it's a Win9x-only (Win95-only?) problem!)
>  - Cygwin 1.1.4
>  - GERMAN Keyboard layout
> [...most repetitions deleted...]
> So don't tell me this works.
> 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!

Sounds as if you have a problem with the backtick...

So your description is loud and clear: you're not a beginner but,
however, I'm missing some details here:

- Did you try to enter ` while executing Cygwin's "cat" on the command
  line?

- Did you try to enter ` while executing a native Cygwin editor (vim)
  instead of using a native Windows editor?

These tests would be able to show if it's a problem in Cygwin or
in bash.

But most important:

- Did you try to _debug_ the problem?
  Gdb and strace are part of the distro. And it's even better: It's
  GPL'd software and all(!) sources are available so you will be able
  to figure the problem and send a patch which might help thousands of
  people!!! This is even better than just complaining.

Isn't open source software wonderful?

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

Re: [BASH] Backtick problem still NOTsolved!! (Win95b/CW1.1.4)

[Andreas Eibach]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2873 bytes --]

> Sounds as if you have a problem with the backtick...
Yes.

>
> So your description is loud and clear:
That's what it supposed to be.
I don't like long  descriptions at all but this was a must because
otherwise I would've gotten these wonderful tips like
"please note  that you must press space after the backtick" ;))))

> however, I'm missing some details here:
>
> - Did you try to enter ` while executing Cygwin's "cat" on the command
>   line?

Yes. Doesn't work either. No backtick.

>
> - Did you try to enter ` while executing a native Cygwin editor (vim)
>   instead of using a native Windows editor?

Yes. Doesn't work either. No backtick in Cygwin vim. Unfortunately.

I think/hope this may trigger some logical process now.
>("it's this, but not that...")

> These tests would be able to show if it's a problem in Cygwin or
> in bash.

> - Did you try to _debug_ the problem?
Not yet.

>   Gdb and strace are part of the distro. And it's even better: It's
>   GPL'd software and all(!) sources are available so you will be able
>   to figure the problem and send a patch which might help thousands of
>   people!!!

Fine saying, Corinna - but maybe this goes beyond my programming abilities?
Think about that. I know C but I'm not a guru to find out this problem.
Looking at the code, this is quite sophisticated stuff - to say it clearly.

Ah...
 some additional info I've got here (maybe useful,  maybe not) :)

$ bash  -version
GNU bash, version 2.04.0(1)-release (i586-pc-cygwin)
Copyright 1999 Free Software Foundation, Inc.

Note 2: this "complaining style" is not my usual one.
I only use this if people keep answering "read the docs. this is a faq. read
the docs
and you'll get it working." _despite_ having a different Windows than me as
it turns
out in the end! This happened to often regarding the backtick problem.
_Not with me_, but with third-party people whose postings I also read -
passively,
that is.

No, I'm quite too experienced to complain about a thing that can be fixed in
a blink
of an eye. This is a *real* problem *in* the code and not able to be fixed
just by
"correct settings"
in bash.

HOWEVER: I can say the backticks worked in older _B20_ with
the --noediting option:

[B20] $ bash --noediting
[B20] $ ééééé

However this workaround does NOT  work in current Cygwin release.

I'm always feeling embarrassed shouting out loud "_Cygwin_ _Bug_ _Found_!"
if
it turns out to be just my non-ability of configuring things properly. But
this time I'm
absolutely sure. This _is_ a missing thing.

And: note that it WORKS FINE on the machines of WinNT users here!
This minimizes the chance of being  able to fix it  myself.

So  ... enough the rambling ;)
I hope every fog has lifted now - thanks for reading :)

Andreas



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

Re: [BASH] Backtick problem still NOTsolved! [STRACE output inside]

[Andreas Eibach]

> Sounds as if you have a problem with the backtick...
>
> But most important:
>
> - Did you try to _debug_ the problem?
>   Gdb and strace are part of the distro.

YUP, thanks!!

That's what I did:

$ cat
 test``

This is my strace output: (like you can see, I've typed two backticks
with a space followed each, but only the space.(0x20 / dec. #32) is
recognized, the other part is regarded as if not there:

**********************************************
Program name: D:\CYGWIN32\BIN\CAT.EXE
App version:  1001.2, api: 0.21
DLL version:  1001.4, api: 0.26
DLL build:    2000-08-03 20:53
OS version:   Windows 95-4.0
Date/Time:    2000-09-25 10:22:24
**********************************************
<snip>

  544  562239 [main] CAT 1027 setmode: setmode (1, text) returns binary
16339  578578 [main] CAT 1027 time: 969870145 = time (0)
 2364  580942 [main] CAT 1027 _fstat: 0 = fstat (0, 253FCD8)
12230  593172 [main] CAT 1027 set_sig_errno: errno 0
 1755  594927 [main] CAT 1027 _read: read (0, 0x45710F0, 1024)
  546  595473 [main] CAT 1027 _read: non-interruptible read

8683926 9279399 [main] CAT 1027 fhandler_termios::line_edit: char t
 3004 9282403 [main] CAT 1027 fhandler_console::write: 253FB1B, 1
 1742 9284145 [main] CAT 1027 fhandler_console::write: at 116(t) state is 1
10721 9294866 [main] CAT 1027 fhandler_console::write: 1 = write_console
(,..1)

1779299 11074165 [main] CAT 1027 fhandler_termios::line_edit: char e
 1977 11076142 [main] CAT 1027 fhandler_console::write: 253FB1B, 1
 1571 11077713 [main] CAT 1027 fhandler_console::write: at 101(e) state is 1
 3059 11080772 [main] CAT 1027 fhandler_console::write: 1 = write_console
(,..1)

1634141 12714913 [main] CAT 1027 fhandler_termios::line_edit: char s
 2979 12717892 [main] CAT 1027 fhandler_console::write: 253FB1B, 1
 1672 12719564 [main] CAT 1027 fhandler_console::write: at 115(s) state is 1
 9237 12728801 [main] CAT 1027 fhandler_console::write: 1 = write_console
(,..1)

1544859 14273660 [main] CAT 1027 fhandler_termios::line_edit: char t
 3045 14276705 [main] CAT 1027 fhandler_console::write: 253FB1B, 1
 1596 14278301 [main] CAT 1027 fhandler_console::write: at 116(t) state is 1
 2783 14281084 [main] CAT 1027 fhandler_console::write: 1 = write_console
(,..1)

7207450 21488534 [main] CAT 1027 fhandler_termios::line_edit: char 0x20
 3069 21491603 [main] CAT 1027 fhandler_console::write: 253FB1B, 1
 1606 21493209 [main] CAT 1027 fhandler_console::write: at 32(0x20) state is
1
 2975 21496184 [main] CAT 1027 fhandler_console::write: 1 = write_console
(,..1)

6116442 27612626 [main] CAT 1027 fhandler_termios::line_edit: char 0x20
 3044 27615670 [main] CAT 1027 fhandler_console::write: 253FB1B, 1
 1621 27617291 [main] CAT 1027 fhandler_console::write: at 32(0x20) state is
1
 3046 27620337 [main] CAT 1027 fhandler_console::write: 1 = write_console
(,..1)

Andreas




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

Re: [BASH] Backtick problem still NOTsolved!! (Win95b/CW1.1.4)

[Corinna Vinschen]

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

Re: [BASH] Backtick problem still NOTsolved!! (Win95b/CW1.1.4)

[Corinna Vinschen]

Corinna Vinschen wrote:
> In W95 with german keyboard, it returns _always_ ASCII
> code 0x00 when pressing backtick as well as the following space,
> unfortunately.

Nonsense! The space key returns 0x20 of course.

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

Re: [BASH] Backtick problem still NOTsolved!! (Win95b/CW1.1.4)

[Andreas Eibach]

From: "Corinna Vinschen" <vinschen@cygnus.com>

> 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

Read.

So CYGWIN was developed using M$ Win32 SDK?
Ah this is news for me... :)

Well HOW COULD YOU DARE...!!
*grin*

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

Easily said.
Maybe replacing a few dlls fixes the problem but MS doesn't  tell
which dll they enhanced to make DK work.

> In W95 with german keyboard, it returns _always_ ASCII
> code [corrected] 0x20 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.

hehe...what an ugly workaround ;)

Well as I can finally *define* the actual problem, I can even try to install
an
US KEYBOARD LAYOUT on my W95 where  I can switch between
[USA] and [GER].

However, I'm afraid I need a little more information:

*Which* keyboard layout? The one I set in Win32 or the one I set via
KEYB.COM when *booting up* Win95?

In the latter case, I only would have to *comment out* my KEYB GR
line. But I *think* I tested this already and it didn't work either.
However I'm not absolutely sure.

Corinna,
Thanks so much for your labourous efforts,

 :-)
Andreas




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

Re: [BASH] Backtick problem still NOTsolved!! (Win95b/CW1.1.4)

[Andreas Eibach]

From: "Corinna Vinschen" <vinschen@cygnus.com>

> 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

Read.

So CYGWIN was developed using M$ Win32 SDK?
Ah this is news for me... :)

Well HOW COULD YOU DARE...!!
*grin*

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

Easily said.
Maybe replacing a few dlls fixes the problem but MS doesn't  tell
which dll they enhanced to make DK work.

> In W95 with german keyboard, it returns _always_ ASCII
> code [corrected] 0x20 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.

hehe...what an ugly workaround ;)

Well as I can finally *define* the actual problem, I can even try to install
an
US KEYBOARD LAYOUT on my W95 where  I can switch between
[USA] and [GER].

However, I'm afraid I need a little more information:

*Which* keyboard layout? The one I set in Win32 or the one I set via
KEYB.COM when *booting up* Win95?

In the latter case, I only would have to *comment out* my KEYB GR
line. But I *think* I tested this already and it didn't work either.
However I'm not absolutely sure.

Corinna,
Thanks so much for your labourous efforts,

 :-)
Andreas



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

Re: Can't abort command line with Ctrl-C anymore...

[Chris Faylor]

On Sun, Sep 24, 2000 at 03:16:35PM -0700, Paul Johnston wrote:
>Hi, I've just upgraded from B20 to net release 1.1.4 (latest, as of today).
>Nice install!  Anyway, when I type a command ctrl-c does not abort it.
>Ctrl-C still works to interrupt a running process, but I can't bail out of a
>command without using the backspace key.  Is this a setting or has the
>behavior of bash changed?  I'm on NT4.

It's a bug in Cygwin 1.1.4.  This has been mentioned many times.  Check
the mailing list archives.

cgf

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