Re: [PATCH] cannot input bar with JP106 keyboards

[Jamie Lokier]

John Bradford wrote:
> As I understand it there was traditionally a distinction between pipe,
> (a broken vertical line), and bar, (solid vertical line).
> 
> The markings on my keyboard are as follows:
> 
> Pipe is the fourth character on the lower-right backslash key.
> Bar is the second character on the upper-right yen key.
> 
> However, my keyboard emulates a US one in Set 2, and produces the
> Linux 'pipe' symbol, for example as in
> 
> cat foo | less
> 
> when the bar key is pressed.

I have a UK keyboard; it's a Microsoft Natural keyboard.

It has both "broken vertical line" and "solid vertical line" markings.
The former is in the usual place above backslash.  The latter is in
the alternate (altgr, as opposed to shift) position on the key which
has backquote (grave) and logical-not symbols.

Curiously, both "broken vertical line" and "solid vertical line"
generate a solid vertical line character in X (U+007C, standard pipe
character), though shift+altgr+"broken vertical line" generates a
broken vertical line character (U+08A6).

On the Linux console, all combinations generate a broken vertical
line, although that's the terminal font displaying a broken line for
the same character that X shows as a solid one.

What a strange mismash.  It would be nice if the keyboard simply
produced what is shown on the keys!

It's nice that the logical-not key actually generates a logical-not
character these days.  I'm not sure why so many keyboard have it, and
in such a prominent position, considering I've never _ever_ seen it
used in a document, and the other logical symbols aren't present.

Many older mappings emitted tilde at this position instead of
logical-not, which I often used and was quite startled the day it
started emitting what was on the key.

-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/