Hello to you all,

I was not aware that this been filed as a bug! The matter of fact, myself and 
many others thought of it as an advantage of gedit over other editors and we do 
use it intensively.
Now, we do seriously miss it after upgrading to ubuntu 16.04 which comes 
shipped with the latest gedit version.

But, since there are different preferences here as you may find, perhaps
an option under preferences would be great where one can enjoy gedit
treating underscore as word delimiter or the other way.

Thank you,

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/615506

Title:
  Underscore must be a part of the word

Status in gedit:
  Fix Released
Status in gedit package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gedit

  Any known to me text editor (not a text processor) would treat
  underscore character '_' as a part of the word it's attached to, but
  gedit does not. This causes all word-related actions to be limited to
  only part of the word, e.g.:

  create_if_doesnt_exist=1

  where 'create_if_doesnt_exist' is essentially one word, but double-
  click on 'create' selects only this part of the word. The same applies
  to all other word related operations.

  This is incorrect and undesirable in many cases. There must be at
  least an option to make underscore one of the word chars (like \w in
  regexes).

  NB: This is not a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/413360 !

  The above entry only refers to selecting words with double-click.
  Mine is more general: the problem applies to all operations supposed to 
affect whole words:
    - Double-click selection
    - Next/Prev Word (Ctrl+Left/Right)
    - Find and Replace with Match entire word only turned on
    - Title Case command from Change Case plugin
    - Spell-checking

  One of the most often recommended solutions is Click_Config plugin at
  http://code.google.com/p/gedit-click-config/

  However I think it's a wrong way of resolving this issue. The problem
  isn't about clicks, it's about determining what is a part of the word,
  and what isn't. Fixing clicks does not root the cause.

  That wouldn't help replacing whole words, for example, nor would it
  act as expected in other cases, eg. when a plugin scans for
  identifiers in the text.

  Originally posted as a question:
  https://answers.launchpad.net/ubuntu/+source/gedit/+question/120519

  gedit 2.30.3, Ubuntu 10.04.1 LTS 32-bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/615506/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to