Ticket #2241 (new bug)

Opened 8 months ago

Last modified 4 months ago

~ (tilda) Key requires a double keypress to be displayed

Reported by: scottmc Owned by: axeld
Priority: normal Milestone: R1
Component: - General Version: R1 development
Cc: koki Blocked By:
Platform: All Blocking:

Description

At first I just thought I have a bad key on my keyboard, but now I've noticed it happens only when I'm in Haiku and happens on any keyboard I've used in Haiku so it seems it's a haiku bug. Not sure if this is related to an already reported bug or not though.

Change History

follow-up: ↓ 2   Changed 8 months ago by axeld

Isn't that just the default for the US-International keymap? IOW it's just a deadkey and should be like that?

in reply to: ↑ 1   Changed 8 months ago by bonefish

Replying to axeld:

Isn't that just the default for the US-International keymap? IOW it's just a deadkey and should be like that?

Maybe, but then we should change the default keymap to American, which seems to work as expected.

  Changed 8 months ago by umccullough

Yes, it's always been this way in the default image AFAICR.

Interestingly, if you execute "cd ~" and the ~ doesn't appear in the shell (because you didn't press it twice) it still changes to your home directory anyway :)

  Changed 8 months ago by koki

  • cc koki added

Isn't that just the default for the US-International keymap? IOW it's just a deadkey and should be like that?

Yes, this is in fact the expected behavior for the US-International keymap.

  Changed 8 months ago by stippi

But there is definitely something fishy with the ~ key. It works differently in Haiku than what I am used to. For example, if you press it and then move the cursor, it should dump the character. I think in Haiku you have to press it twice for that to happen.

  Changed 8 months ago by koki

The behavior described in this bug is the expected behavior of a deadkey; for example, pressing "~" followed by "n" will display "ñ".

There is some strange behavior when you want to cancel input before you press the second keystroke, but it looks to me like that would probably require a different bug report.

  Changed 4 months ago by aldeck

I've got this annoying problem here too since forever (fr keymap, not sure its relevant, see below)

Interestingly i just noticed that the bug appears only when you type rapidly '~' then 'space'. Waiting a bit after typing '~' shows the expected behavior. In terminal, it seems there is a change in the cursor blinking when its ok to type the second key. Tested in Terminal and StyledEdit.

HTH

Note: See TracTickets for help on using tickets.