Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ConEmu eats dead keys #646

Open
Maximus5 opened this issue Jul 31, 2015 · 19 comments
Open

ConEmu eats dead keys #646

Maximus5 opened this issue Jul 31, 2015 · 19 comments

Comments

@Maximus5
Copy link
Owner

Originally reported on Google Code with ID 646

OS version: WinXP   SP3   x86
ConEmu version: 120719

*Bug description*

If ConEmu is running, I can't type accents.

*Steps to reproduction*
1. Start ConEmu.
2. Try to type accented caracters or use any dead key.

Dead keys won't work in *any* application as long as ConEmu is running.

Reported by guillermo.listas on 2012-07-20 09:49:32

@Maximus5
Copy link
Owner Author

Issue is not complete. 

0. Check keybindings. May be you have set dead key for global hotkey?

Because I don't have dead keys in my keyboard layouts, describe IN DETAILS
1. Name of layout
2. What keys you are typing (where they are located)
3. What is expected output.


> Dead keys won't work in *any* application as long as ConEmu is running.

Hm? "any" do you means, started outside of ConEmu?

Reported by ConEmu.Maximus5 on 2012-07-20 10:45:41

@Maximus5
Copy link
Owner Author

Layout: Spanish - International Sort
Keys: any dead key, for example:

";" (that is, the unshifted key) in a standard QWERTY layout:

http://en.wikipedia.org/wiki/File:Qwerty.svg

´ + a yields a whereas á is expected

> Hm? "any" do you means, started outside of ConEmu?

Yes, it seems to affect the system globally (I have not experimented this issue in
Windows 7 with basically the same setup). I belive during the first startup ConEmu
prompts the user to let it inject a dll in all processes? Don't know if it's related,
but just as a pointer.

Reported by guillermo.listas on 2012-07-20 11:51:54

@Maximus5
Copy link
Owner Author

Did you read my comment thoroughly? Seems to be not.


again

0. Check keybindings. May be you have set dead key for global hotkey?

Reported by ConEmu.Maximus5 on 2012-07-20 12:30:11

@Maximus5
Copy link
Owner Author

Hi again,

I haven't set any key bindings myself and I don't see any conflicting ones under Settings...,
so if the correct key names are reported there, it doesn't seem to be due to key bindings.

Reported by guillermo.listas on 2012-07-20 12:51:09

@Maximus5
Copy link
Owner Author

Found the problem with dead chars in ConEmu. Cause - physical difference between spanish
and english keyboards. My keyboard produces different keycodes and seems to be working
:)

For clarification, ConEmu does not inject dll in other processes (specially), so skipping
of dead chars (in other apps) may be caused by global hotkeys only.

Reported by ConEmu.Maximus5 on 2012-07-22 01:46:23

  • Status changed: Started

@Maximus5
Copy link
Owner Author

Fantastic! Thank you! I'll give it a try tomorrow.

Re. global hotkeys, I'm pretty sure that it was happening only when ConEmu was running
(maybe in full screen mode only), because I tested that a couple of times and the problem
consistenly went away as soon as ConEmu exited. I will try again, though.

Thanks for your prompt reply!

Reported by guillermo.listas on 2012-07-22 14:47:31

@Maximus5
Copy link
Owner Author

Try 120722

Reported by ConEmu.Maximus5 on 2012-07-22 23:46:29

@Maximus5
Copy link
Owner Author

Hi,

Unfortunately, the problem persists with 120722.

It's worth noting I'm using a QWERTZ German keyboard set to a Spanish (Modern Sort)
QWERTY layout.

It's confirmed too that accents stop working globally when ConEmu is running and work
again when I quit ConEmu.

Let me know if I can provide any more info.

Regards,
Guillermo


Reported by guillermo.listas on 2012-07-23 08:32:51

@Maximus5
Copy link
Owner Author

1. Screenshot of "Keys & Macro" page AND export of ConEmu settings

2. Run "ConEmu /log /cmd cmd", try to type accented characters several times, type
standard (nonaccented) chars several times, close ConEmu, attach log

3. Run "ConEmu /nokeyhooks /log /cmd cmd", try to type accented characters several
times, type standard (nonaccented) chars several times, close ConEmu, attach log


Reported by ConEmu.Maximus5 on 2012-07-23 10:47:15

@Maximus5
Copy link
Owner Author

Here's what I've been able to see:

1) Starting ConEmu like this, I CAN type accents:

C:\"N:\guillermo\Progs\Far Manager\conemu.exe" /cmd cmd
C:\"N:\guillermo\Progs\Far Manager\conemu.exe" /cmd powershell

2) Starting ConEmu like this, I CANNOT type accents:

C:\"N:\guillermo\Progs\Far Manager\conemu.exe"

In Conemu, there's a startup task defined like this:

=============================
{StartUp}
-----------------------------
> powershell.exe

far.exe

cmd.exe

python.exe
=============================

I'm attaching:

* Keys & Macros settings page
* Logs

Unfortunately, I could not figure out how to export settings, but they should be the
default.

Reported by guillermo.listas on 2012-07-23 12:59:40


- _Attachment: [set1.GIF](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-646/comment-12/set1.GIF)_ - _Attachment: [ConEmu-input-4524.log](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-646/comment-12/ConEmu-input-4524.log)_ - _Attachment: [ConEmu-input-4632.log](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-646/comment-12/ConEmu-input-4632.log)_

@Maximus5
Copy link
Owner Author

Hm, I think now, it is not a ConEmu problem...

Try to remove one-by-one apps from <Startup> task. Python and Far are first suspects

Reported by ConEmu.Maximus5 on 2012-07-23 15:02:35

@Maximus5
Copy link
Owner Author

Looking into you log. Man, why you do not follow instructions? Remember, I have asked


> try to type accented characters several times, type standard (nonaccented) chars
several times

But I see in log 4524
a b c d f f t ñ ´ á ´ á 
and so on
And log 4632
a s f d a d s f w... ñ ´ á ´ á ´ á
and so on

It's a joke? You want to confuse me?
Also, I seek in BOTH logs accented characters successfully sended to the console.

Why you don't describe in detail?
1. What you type
2. What you get in the console
3. AND WHAT PROGRAM (exactly, with versions) in active (and inactive) console is running?

Seems for now, this report is invalid (

Reported by ConEmu.Maximus5 on 2012-07-24 07:04:51

@Maximus5
Copy link
Owner Author

I'm starting to really dislike this conversation with you. I will kindly remind you
that I don't work for you and that I'm doing what I can to help, but honestly, my patience
is almost exhausted.

> It's a joke? You want to confuse me?

No, it's not. If you don't understand your own program, you can imagine what I feel
like.

> But I see in log 4524
> a b c d f f t ñ ´ á ´ á 
> and so on
> And log 4632
> a s f d a d s f w... ñ ´ á ´ á ´ á
> and so on

As per your instructions above, I ran:

C:\"N:\guillermo\Progs\Far Manager\conemu.exe" /cmd cmd
C:\"N:\guillermo\Progs\Far Manager\conemu.exe" /cmd powershell

... and then typed in accented charactes. Also, as I've told you, when I start ConEmu
like that I CAN type accented characters. That's why you get correct results in both
logs.

Only when I start ConEmu like this do dead keys stop working:

C:\"N:\guillermo\Progs\Far Manager\conemu.exe"

In this case, ConEmu will run the {StartUp} task mentioned above.

Now this is new information:

After a quick check, it does seem that the problem depends on the programs that are
running within ConEmu at any given time, but I haven't determined which ones yet, although
Python seems to be one of them.

I'll post back with more details if I'm able to find out anything else and if I think
your manners are worth my time.

Reported by guillermo.listas on 2012-07-24 08:36:43

@Maximus5
Copy link
Owner Author

I think, the problem is caused by Python, not ConEmu. If you want to continue conversation
(wich unfortunately I starting to dislike too) I can give you some hints.

Manners? Hm... now my point of view.
I do my best in my spare time to help YOU!
IMHO, my anwers are polite, preciese and informative.

As I said, the problem does not reproduced on my side and seems that no other users
experie same problem.
If you want to eliminate this problem,  I'm ready to help you (of course), but it is
your responsibility to provide exact asnwers to my questions.

And of course, not you or me do not owe anything to other.

Reported by ConEmu.Maximus5 on 2012-07-24 10:49:41

@Maximus5
Copy link
Owner Author

I appreciate your taking time for this; I hope you reciprocate.

Let's see if this is more useful to you:

SYMPTOMS

After ConEmu has started with a {StartUp} task like the one described below:

* I cannot type accented characters in certain console applications in ConEmu.
* I cannot type accented characters in any other application outside of ConEmu.

{StartUp} Task Used

> powershell.exe

far.exe

OBSERVATIONS

* The same thing seems to happen if cmd.exe is included in the {StartUp} task instead
of far.exe.
* I have NOT observed the same thing if powershell.exe AND python.exe are in {StartUp}
instead.

After startup, I cannot type accented characters in powershell.exe, but they work fine
in far.exe. Furthermore, if I first type an accented character in Powershell (it doesn't
work), then switch to Far and type the same accented character (it works now), and
finally go back to Powershell, I can now type accented characters normally in Powershell.exe.
And they work too outside of ConEmu from this point on.

Also, it seems that, for the accented characters to stop working, the first thing you
need to do is to press a dead key. If you first press any other key in Powershell,
and then type accented characters, they will work without doing what I describe in
the previous paragraph.

It also seems that moving the mouse around over ConEmu before starting typing makes
the deadkeys work normally.

LOGS

* I'm attaching a log for this session:

ConEmu /log /cmd {StartUp}

And this is what I do:

* First I type an accented character in Powershell several times (á)
* Then I type normal characters
* Then I type more á characters
* Then I switch to Far
* I type á in Far
* I go back to Powershell
* I type á in Powershell again

(I don't know why, I'm getting two log files, so I'm attaching both. I suppose there's
one for each tab in ConEmu.)

Reported by guillermo.listas on 2012-07-24 12:45:13


- _Attachment: [ConEmu-input-2716.log](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-646/comment-17/ConEmu-input-2716.log)_ - _Attachment: [ConEmu-input-3212.log](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-646/comment-17/ConEmu-input-3212.log)_

@Maximus5
Copy link
Owner Author

So strange behavior...
Thanks for thorough report!

Reported by ConEmu.Maximus5 on 2012-07-24 13:05:52

@Maximus5
Copy link
Owner Author

Just a quick note that my work computer has been upgraded and I will not be able to
follow up on this issue any more.

Reported by guillermo.listas on 2012-09-11 17:38:44

@Maximus5
Copy link
Owner Author

XP -> Win7?

Reported by ConEmu.Maximus5 on 2012-09-11 17:56:30

@Maximus5
Copy link
Owner Author

Yep. I'm now using Win7 Pro.

Reported by guillermo.listas on 2012-09-11 18:39:04

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant