Every Linux flavour gives me this issue:

The Caps-Lock key, that I use to capitalise sentences, only toggles the capitalisation modifier when I release said key.

Instead, I want it to toggle (and lock) the capitalisation modifier when I simply press the key, disregarding if I ever release said key.

That's the behaviour of Windows.

I don't use the Shift key because I learned how to type relying on the Caps-Lock key to those jobs. I don't intend to re-learn how to type unless I have absolutely no way around this.

I tend to hold the Caps key a little longer on some sentences, thus outputing this:

"THis IS AN EXample SEntence".

Obviously I posted this on the Ubuntu Forums (since that's the distro I use).

The original post is here: How to Change Caps Lock Behavior

But so I far I failed to find a fix.

If you guys have something to say to help me, please do.

Thanks.

SiegeLord you seemed to have nailed it exactly!

Summarising all the Ubuntu thread in a single post.

Maybe I should do that as you described but I'll refrain to tag it as a "bug" yet.

I'm fairly new to Linux so I don't know how accessible/simple is to simply pick-up the corresponding piece of code, try to change it and recompile.

Do you have any pointers on that? Or maybe it's way out of my league.

Anyway I'll look into the responsible party that deals with keyboard.

Thanks.

[edit]
Not related to this topic: I have two profiles and would like to request that Mr. Leverton deactivates the latter one (2006) so I could stop confusing myself and others.

I'd file this bug under the "Keyboard to Chair Interface Failure" category.

Self-pity won't win you any points. I wasn't taught formally either, I just do whatever comes naturally. Pressing the caps-lock key might come naturally for you as well, I was just commenting that its very strange that it would come naturally at all considering how much harder it is to press caps-lock twice than it is to hit shift once.

Anyway, have you determined if its application specific or does it happen everywhere? You can probably just remap caps-lock to shift using xmodmap.

I wouldn't call it "bad". Caps lock is a SWITCH not a regular button. Its state toggles. Why in heck you'd expect it to act like SHIFT I'll never know.

Why would you hold down a shift lock? Just a quick peck with your pinky and you're done.

I hardly EVER use my right shift key. In fact, I mainly use it just for playing games. Capital A, E, S, etc I use left shift for too. Shift with right pinky, index finger for T, ring finger for A, and middle finger for E and S.

I had to look the expression "self-pity" on Google to understand it.

If I understand correctly it was an insult.

You've interpreted my post the wrong way. I wrote in an impartial way, only describing the scenario for you guys information.

Re-reading my post again I think that starting the sentence with "I'm just saying" made me sound that way.

Happens in every application that I've used.

I'm taking a touch-typing tutorial to overcome my disability.

Well, X.org had the same problem concerning the SHIFT key. If you'd do the following:

Press c
Release c
Press d
Release d
Press space
Press shift
Release space
Press 7 (shift still pressed)

it would result in 'cd 7', where I was obviously trying to type 'cd /'. Took them several months to fix it.
Anyway - the problem you are describing is a real bug nevertheless, even if no one cares about it. I have a LED for caps lock (most of you do), and as soon as I press capslock the second time, the LED turns off, even if caps lock is still pressed. So you can type upper case letters even if the caps lock LED is off and shift is not pressed. I would post that somewhere on https://bugs.freedesktop.org/

I never thought I'd know of two people with that particular quirk.

It's bad because it is inconsistent, no matter what people use it for. Either the key press should reset the state, or key release should reset the state, not one or another at differing times. Plus, as the OP said, this also leads to the mismatch between the actual Caps Lock state and the Caps Lock LED and which does get reset by the key down event.

SiegeLord, X is not Windows. Get over it

But that oddness of shift being ignored in the following sequence does seem like a bug:

Press c
Release c
Press d
Release d
Press space
Press shift
Release space
Press 7 (shift still pressed)

I agree that the caps lock inconsistent behavior is a bug, though not one I've ever had a problem with (I remap capslock to ctrl, to use emacs). I can't imagine it's too serious for most people, though, as most people who use it at all use it as a switch.