Description of problem:

In certain circumstances, double-click selects across word boundary
characters.

Version-Release number of selected component (if applicable):

vte-0.11.11-6

How reproducible:

100% with bash

Steps to Reproduce:
1. Use bash as a shell
2. Type a long command which makes bash to scroll one line when
   cursor-up is hit. Any gibberish will do. Enter it, so history
   has it.
3. Create a directory and populate it with files. Better not have
   directories, just to have less stuff.
4. Type "ls *", Enter. Say, you see:

[zaitcev@lembas uml]$ ls *
foo                       uml-patch-2.4.23-2.bz2
[zaitcev@lembas uml]$ 

   If you cursor-up the "ls *", and re-execute it, everything will
   be all right. Double-click on foo to verify. But wait...
5. Cursor-up to the long command. Bash will scroll one line up to
   fit that.
6. Cursor-down to the "ls *". Enter it. You see normal output,
   exactly the same as at the step 4.
7. NOW, double-click at "foo" in the example above. The vte will
   select the asterisk.

Actual results:

Selection of space at the end of "ls", asterisk, newline, and "foo".

Expected results:

Selection of "foo".

Additional info:

This is a bug in vte. The old gnome-terminal before vte didn't have
it. However, I didn't file before because I did not understand what
it took to reproduce. It should be clear now.

The most amusing result happens if you do type "rm", middle-button,
and hit enter before you realize what you've done. Then, rm says
that the file you wanted to remove does not exist already, ehehe :-)