Control characters pass through?

[Emilio III]

[C:\]ver /r

TCC 10.00.64 Windows XP [Version 5.1.2600]
TCC Build 64 Windows XP Build 2600 Service Pack 3
Registered to Emilio Perea - 1 System License
*---

It seems that control characters are not being passed through to attached Microsoft Services for Unix shells or those invoked from tcc via e.g.

alias csh posix /u /c /usr/local/bin/tcsh -l

I know this used to work fine on earlier builds of TCC 10, but unfortunately I did not notice when it changed. It was already a problem with build 63, but I no longer have earlier versions to check. Tabs must be detached before control characters work.

% uname -a
Interix ARTEMIS 3.5 SP-8.0.1969.1 x86 AMD_x86_Family15_Model104_Stepping2

 

[rconn]

Emilio III wrote:

>
> It seems that control characters are not being passed through to attached Microsoft Services for Unix shells or those invoked from tcc via e.g.
>
> alias csh posix /u /c /usr/local/bin/tcsh -l
>
> I know this used to work fine on earlier builds of TCC 10, but unfortunately I did not notice when it changed. It was already a problem with build 63, but I no longer have earlier versions to check. Tabs must be detached before control characters work.
>
> % uname -a
> Interix ARTEMIS 3.5 SP-8.0.1969.1 x86 AMD_x86_Family15_Model104_Stepping2

Not sure what you mean by "control characters" - can you give me a
specific example?

Rex Conn
JP Software

 

[Emilio III]

On Tue, Mar 31, 2009 at 09:27:08PM -0500, rconn wrote:

> Not sure what you mean by "control characters" - can you give me a
> specific example?

Sorry, that's not the right wording. I meant <Ctrl-C> or <Ctrl-Z> in
particular. Neither the right nor the left Ctrl key can be used with C
to stop a ping, for example. This morning I thought <Ctrl-Z> to suspend
and several others didn't work either, but they work fine now. Only
<Ctrl-C> seems to be a problem now, and <Ctrl-Break> can substitute, so
it's not nearly as big a problem as I thought it was, though still
annoying.

OTOH, if I'm the only one seeing this there's no point in worrying about
it.

 

[vefatica]

On Tue, 31 Mar 2009 21:27:14 -0500, rconn <> wrote:

|Not sure what you mean by "control characters" - can you give me a
|specific example?

I wasn't sure what the OP meant either. I tried TCSH in a tab and ^U erased a
command line in progress, ^H erased the character before the caret ... both as
expected. And ^C terminated an (external) ls and ping.exe. ^Break causes
ping.exe to give up-to-date stats and continue. ALl seems as it should be.
--
- Vince

 

[rconn]

Emilio III wrote:

> On Tue, Mar 31, 2009 at 09:27:08PM -0500, rconn wrote:
>
>
> ---Quote---
>> Not sure what you mean by "control characters" - can you give me a
>> specific example?
> ---End Quote---
> Sorry, that's not the right wording. I meant <Ctrl-C> or <Ctrl-Z> in
> particular. Neither the right nor the left Ctrl key can be used with C
> to stop a ping, for example. This morning I thought <Ctrl-Z> to suspend
> and several others didn't work either, but they work fine now. Only
> <Ctrl-C> seems to be a problem now, and <Ctrl-Break> can substitute, so
> it's not nearly as big a problem as I thought it was, though still
> annoying.
>
> OTOH, if I'm the only one seeing this there's no point in worrying about
> it.

Not reproducible here.

Check your TCMD menu shortcuts - right click on the menu bar, then
Customize, then Keyboard, and select Edit in the Category combo box.
Make sure you don't have Ctrl+C set as a shortcut key for Copy.

Rex Conn
JP Software

 

[Emilio III]

On Wed, Apr 01, 2009 at 06:50:57AM -0500, rconn wrote:

> Not reproducible here.
>
> Check your TCMD menu shortcuts - right click on the menu bar, then
> Customize, then Keyboard, and select Edit in the Category combo box.
> Make sure you don't have Ctrl+C set as a shortcut key for Copy.

No, it's Ctrl+Ins. I reset all key assignments, but ^C still doesn't
work for me. NBD if you can't reproduce it.

 

[eclayp]

I am having the same issue with Ctrl -C not working as well. As others have mentioned, it worked in previous builds (I just can't remember which ones exactly).

Info:
Vista x64 w/SP1 (also happens with Vista x64 SP2RC escrow)
TC v10 (build 64)
cmd.exe as my comspec
Ctrl-C is not mapped to any keyboard shortcuts

Steps to reproduce (hopefully):

1. In a cmd window from TC, go to C:\Windows\System32
2. Type dir /p
3. Ctrl-C

If all goes well, nothing will happen for you as it does me :)

Now if I try the following from a cmd window that I open from the Windows Start Menu, Ctrl-C will work as expected (i.e. stop dir/p).

Hope that helps,
-Eric