Wonky Tilde (~) Key in Haiku / VMware

Does anyone else have this problem:

I have to press ~ twice for Haiku to recognize it. This includes HTML forms, Terminal commands, the works.

Is it caused by VMware?

Haiku R1/Alpha 2
VMware Fusion 3.1.2
Mac OS X 10.6.7
MacBook Pro 5,1

Hi mcandre,

a native Haiku shows the same behaviour. I think it’s because “~” is a “deadkey” (see Keymap preferences) to create letters like õ, ñ and ã. If you don’t think you’d ever need those, you can set the ~ deadkey to “none” in Keymap and get a tilde on first keypress.



I see that other deadkeys are enabled by default: ^, `.

Could deadkeys be set to None by default? I imagine newbies like me are scratching their heads wondering why they have to press these keys twice.

I guess it could be the default, but then people may scratch their head that they don’t get these special characters at all. At least having to press twice is automatically discovered, because people probably think their first keypress didn’t make it somehow and press again.


I lived with that for a year or so before I accidentally found out how to fix it. I sure don’t miss this “feature” - even though I do know a little Portuguese: ainda tem bastante ã e õ, através do composição.

Dear Humdinger,

Please take off your winkers! There are more languages/people(s) in this world using diacriticals than there are English speakers/writers… So these diacriticals are a must for them! Beside why would you use (try out) these diacriticals if you are used to use the plain ASCII code, rather than the Extended ASCII code?

If you do not like the feature try to set your keyboard to PLAIN “US-keyboard” (no dead keys), rather than “US-International”(dead keys).

I’m sorry, jlnh. You seem upset, but I can’t see why exactly… What are winkers?

I don’t understand. Do you wonder why anyone would have a need for writing diacriticals, if their preferred language normally doesn’t have them?

What’s the feature I don’t like? I’m perfectly fine how it works now, just trying to help out mcandre…
If anyone is experiencing problems they should file a well thought out enhancement ticket at the bugtracker detailing how things can be improved.


Getting in touch again with Haiku I have problems to type a ‘~’ symbol.
The keymap shows it (German Mac), but nevertheless it is impossible
to type it even when repeatedly typed in.

This is a very important symbol for programming purposes.

Because I have intended to have my new release of a chess program
be compilable also for Haiku, it is very disappointing to be faced to
such frustrating obstacles. Moreover the Paladin application seems
not to support writing of pure console applications, which will be
necessary in all cases. Is that by intention?

After same experiments I saw, that it will be the wrong
decision to select in Germany on a Mac the "German (Mac)"
keymap. The “German” keymap seems to work better here.

The problem with the US-International keymap is that the deadkeys are unmodified which means that they kill frequently used characters. This is just dumb. ~ is a shortcut for the home directory in bash so I run into this wonky behavior a lot.

To solve it I made a keymap where you generate dead keys by holding down the Win key plus a key to get an accented letter. I made it work like the US-International keymap in BeOS 5 (which works similar to Mac OS (not-X)) so to get an acute you type Win+e and then follow that with the letter you want to accent. For example Win+e followed by e gives you é, Win+e followed by i gives you í.

Similarly Win+u followed by u gives you ü. Win+i followed by i gives you î, Win+n followed by n gives you ñ, and Win+` followed by i gives you ì, etc. Also Win+c plus c gives you ç (I think it does on the Haiku US-International keymap too).

This seems a lot more reasonable for North American users where accented letters are used infrequently and they are mapped to the most frequently used letter in English. So you can still type resumé, façade, and el niño while being able to type ~ without having to hit the ~ key twice.

For now the “American” keymap has no dead keys so you can use that to get rid of the wonky ~ problem.

In defence of the default behaviour, Haiku seems to have a large percentage if not the majority of developers coming from Europe where English is NOT their most used language.

It may be a pain, but I think the default is probable the right choice.

Second, since I am an English only person, is your keymap available for downloading?

The default behavior should make deadkeys activated by the Win key I think.

My keymap is not publicly available, but I pastebin’d it for you.



Thank you.