Editor selects different text when you start typing

Hi,

RubyMine 3.3.1, Ubuntu 10.10

I'm experiencing weird and frustrating behavior and am wondering if this is some kind of known problem or if I'm just missing something. I think this just started with 3.1.1, but maybe it also existed for 3.1.

Sometimes when I am typing, text gets selected other than where the cursor is and my keystrokes overwrite that selected text. The selected text is usually a few lines above or below the cursor. This is extremely frustrating because I will be typing away and all of a sudden I am not typing where the cursor is - which serves to wipe out code (i.e. the weirdly-selected text) somewhere else in my file.

When this happens I have to hit Edit>Undo to cancel the code that was just wiped out. This would be bad enough, but what makes it worse is that it is usually impossible to do any other typing. I will physically click somewhere in the file and see the cursor blinking right where I clicked - no surprise there. The surprise comes when I start typing, because as soon as I do that same weirdly-selected text gets selected *again* and I start overwriting it.

It seems like the editor gets "stuck" on selecting that piece of code no matter where you put the cursor. Sometimes if I hit ESC a few times I will be allowed to resume normal typing. Oftentimes that doesn't work and I have to close and re-open the file in order to get the typing back to normal. And sometimes even that doesn't work - which means I have to close and re-open the IDE just in order to resume typing.

This is extremely frustrating because it happens several times a day!

Has anyone else experienced this or does someone know what is going on and how I can stop it when it happens?

Thanks,
Larry

18 comments
Comment actions Permalink

I have experienced the same issue, if only once.

0
Comment actions Permalink

Thanks, Tor. Nice to know I'm not hallucinating or simply trying to code while buzzed. ;)

-- Larry

0
Comment actions Permalink

Don't know if this is related to my original issue or not, but I'm adding it to this post because it's an example of more weird keystroke behavior and it also has happened to me several times since 3.1.1...

When I fire up Changes Window > Commit Changes I can't type in the "Comment" block - which means I effectively can't do a commit because I can't describe the reason for the code changes. The previous commit is in the TextArea and selected (which is the standard behavior), and when I hit Backspace or any other key the selected text is deleted (which is also standard behavior), but subsequent keystrokes don't do anything; the TextArea remains blank.

I close and try committing again - but to no avail. So (once again) I have to shut down the entire IDE just so I can get my typing back to normal. Like I said previously, this restarting the IDE just so I can type is really pretty annoying - especially since it happens at least 5 times a day.

Any ideas?

Thanks,
Larry

0
Comment actions Permalink

Well, here it is, version 3.2. and I still have the same problem. Wich means I have to shut-down and re-open my IDE *several times a day* just because I can't type anything becasue every time I try some text somewhere else is "stuck" on getting selected and I can't do anything but shut down and start over.

This thread has a lot of views, which I assume means others are experiencing this problem. If so, can you please join in and add a comment so that someone can look into this problem?

This really, really, really, really sucks and I'm getting sick of it. Espeically since this problem has plagued me for months and no one has done anything about it. There is no *&^%$# way you should have to shut-down and re-open an IDE several %^$#@! times a day because you can no longer type in the edit window.

-- Larry

0
Comment actions Permalink

Hello again Larry,

Personally I haven't seen the issue in 3.2 yet. Although that is not to say that it isn't there.

In my case the issue usually occurs (occured) after using find to jump to a specific part of a file in the editor. In mosts cases I can workaround the issue by pressing ESC numerous times or switching to another editor tab and back. And I agree that the issue is annoying, but in my case it is currently overshadowed by another issue where the IDE freezes for 2-10 seconds when inspections are running...

Did you post a bug report?

-- Tor

0
Comment actions Permalink

I see the problem too. I'm running on Windows 7. Mainly this occurs when I move from one section of code to another. The cursor seems to grab a whole section of text below the line where I first put it, and then when I start typing it overwrites the lines a little below where I've placed the cursor. Undoing recovers the text, but when I try to carry on it does the same all over again. I have to try different key strokes until I find one that works correctly and then everything starts working again. I'm currently running 3.2.1.

0
Comment actions Permalink

Hello guys, are there any known steps to reproduce the problem with typing? Is it something similar with http://youtrack.jetbrains.net/issue/RUBY-7852 ?

Regards,
Oleg

0
Comment actions Permalink

Hi Oleg,

Performing those simple steps reproduced the problem for me - good call! Hopefully you guys can figure out and fix the problem.

Thanks to those who posted after my request to do so; also, thanks for the tips. I tried switching tabs and at first that worked, but then it didn't. But I found that if I switch tabs and type something in the new window (I just hit 'space' followed by 'backspace') that I can then resume typing in the "stuck" window. It's annoying, but its a lot better than shutting-down and re-starting the IDE.

Thanks,
Larry

0
Comment actions Permalink

Hello Oleg,

The issue in the link posted by Oleg is reproducible for me too. I am not 100% confident that it is the same issue I am experiencing, but it seems very similar.

-- Tor

0
Comment actions Permalink

That looks like what I am experiencing too. Select first text, press quote to surround first text, select second text, start typing - first text is overwritten instead of second text.

0
Comment actions Permalink

Great to hear that we've located the problem, please vote for the issue.

Regards,
Oleg

0
Comment actions Permalink

Hi,

I agree with Tor in that it is similar - but I'm not sure that is the only cause of the problem. If you're typing rather quickly and jumping around doing stuff, it's hard to be sure what caused the editor to get "stuck" like it does.

I hate to sound stupid - and it seems like I should know this - but I don't see anywhere to "vote" for this issue. How do we do that?

-- Larry

0
Comment actions Permalink

Hi Larry,

I hate to sound stupid - and it seems like I should know this - but I don't see anywhere to "vote" for this issue. How do we do that?

The only reason that you cannot find it that our Issue tracker UI is not intuitive enough.
Please have a look at the screenshot.
vote.png

Regards,
Oleg

0
Comment actions Permalink

Hi Oleg,

Thanks for the quick reply. I can see how to vote on the image that you sent, but my question is how do I get from the Forum to the Issue Tracker? I thought there'd be a link so that interested parties could track the issue that was being discussed in the Forum.

-- Larry

0
Comment actions Permalink

Larry,

I have been asking myself the same. Unless I get lucky and spot a link to the tracker, I always re-google rubymine or try to find a relevant link in my browser history, and click my way to the tracker from the top.

Oleg,

It would be nice if the tracker, forum, blog etc. was accessible in a top menu everywhere.

--Tor

0
Comment actions Permalink

The problem was fixed recently, expect fix to be included in next RubyMine bugfix update.

Regards,
Oleg

0
Comment actions Permalink

Great!

Hopefully your fix will work for all cases, as some of us weren't quite sure exactly what caused the problem to happen.

Thanks, Oleg!

Looking forward to the update,
Larry

0
Comment actions Permalink

I've seen this myself. It is quite annoying. Glad to hear it's fixed.

0

Please sign in to leave a comment.