22

When I double-click to select text in GNOME Terminal, the selection stops at spaces but continues over hyphens:

spaces

hyphens

Some of my filenames contain uncommon characters such as the heavy teardrop-spoked asterisk and are not selectable by double-clicking:

unusual characters

Is there a way to make double-click selection continue over these characters as well?

ændrük
  • 78,496

6 Answers6

21

Yes, GNOME Terminal has a setting word-char-exceptions that controls which punctuation characters are considered to break words for double-click selection.

By default, all punctuation will break words, but characters in the exceptions list are instead considered part of the word.

There used to be a UI for it, but that was removed in gnome-terminal 3.14 (Ubuntu 15.04), so now it can only be set via dconf or dconf-editor.

I like to use #%&+,-./:=?@_~ as the set of non-word-separators.

Script

I put this together into a script to set the word separators:

https://github.com/ab/ubuntu-wart-removal/blob/main/gnome-terminal-word-separators.sh

Download:

wget https://raw.githubusercontent.com/ab/ubuntu-wart-removal/main/gnome-terminal-word-separators.sh

Usage:

# print help
./gnome-terminal-word-separators.sh -h

set word-char-exceptions for all profiles


./gnome-terminal-word-separators.sh --all '#%&+,-./:=?@_~'


set word-char-exceptions for a specific profile


./gnome-terminal-word-separators.sh -p 8741a4c2-15c8-45bb-86ec-34c3080526a7 '#%&+,-./:=?@_~'

dconf-editor

You can also edit this with a GUI using the dconf-editor.

Find your GNOME Terminal profile's UUID:

menu -> Preferences -> select your profile -> find the Profile ID listed in the bottom right

Your UUID might look like b1dcc9dd-5262-4d8d-a863-c897e6d979b9.

gnome-terminal preferences

Then open dconf-editor.

  • Navigate to /org/gnome/terminal/legacy/profiles:/.
  • Go to your profile's UUID
  • Go to word-char-exceptions
  • Set your custom value (must be surrounded by quotation marks)

dconf-editor showing word-char-exceptions

History

GNOME Terminal has flip flopped several times on this subject.

There used to be a setting in the preferences GUI to manage this, but that was removed in gnome-terminal 3.14 (included in Ubuntu 15.04 Vivid).

Then in gnome-terminal 3.16 (included in Ubuntu 15.10 Wily), the option was reintroduced under the hood, but with no UI. In addition, colon : was changed to be treated as a word separator (removed from exceptions).

Note: The help text description in dconf-editor of word-char-exceptions was backwards for gnome-terminal versions before 3.51.90. https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/8054

A B
  • 1,466
11

In "Edit > Profile Preferences > General", add the character to the "Select-by-word characters" box.

mgunes
  • 9,910
2

Other answers do not work today ... this works on ubuntu 18.04 ... first identify your UUID gnome terminal profile id ... issue this in terminal

profile=$(gsettings get org.gnome.Terminal.ProfilesList default)

echo $profile  #  for me it gives b1dcc9dd-5262-4d8d-a863-c897e6d97969

now make change : 

dconf write /org/gnome/terminal/legacy/profiles:/:b1dcc9dd-5262-4d8d-a863-c897e6d97969/word-char-exceptions '@ms "-,.;?%&#_+@~·$/"'

until ubuntu 18.04 gets fixed the following read command silently fails whereas it worked fine on ubuntu 16.04

dconf  read  /org/gnome/terminal/legacy/profiles:/:b1dcc9dd-5262-4d8d-a863-c897e6d979b9/word-char-exceptions
Scott Stensland
  • 17,385
0

At Ubuntu 20.04.5 LTS. I've lost a couple of hours, trying to make it work. But the reason of the stall is quite simple: the meaning of "@ms" variable is inverse to intuitive, and inverse to what they've written in org.gnome.Terminal.gschema.xml.

@ms should contain the only characters, ALLOWED to select by double-click. So, if you DON'T want dashes or colons or smth to select, you may enter:

UUID=$(gsettings get org.gnome.Terminal.ProfilesList default | tr -d \')
dconf write /org/gnome/terminal/legacy/profiles:/:${UUID}/word-char-exceptions "@ms '_^'"

Change works immediately, retains through reset; but for different profile, you should repeat the command.

Jackal
  • 43
  • 5
0

A very useful default feature implemented in other terminals is the progressive selection of extended sections of a line on the screen. e.g., given

/home/username/dir1_r.2-3/dsr.filenr_34.ctr 23456677 dftrprpr

double-clicking on, say, filenr in dsr.filenr_34.ctr would progress from filenr to:

                              filenr_34
                          dsr.filenr_34.ctr
                       -3/dsr.filenr_34.ctr
                      2-3/dsr.filenr_34.ctr
                    r.2-3/dsr.filenr_34.ctr
               dir1_r.2-3/dsr.filenr_34.ctr
      username/dir1_r.2-3/dsr.filenr_34.ctr
 home/username/dir1_r.2-3/dsr.filenr_34.ctr
 home/username/dir1_r.2-3/dsr.filenr_34.ctr 23456677
 home/username/dir1_r.2-3/dsr.filenr_34.ctr 23456677 dftrprpr
/home/username/dir1_r.2-3/dsr.filenr_34.ctr 23456677 dftrprpr

Surrounding symmetries may be solved by adding pairs until next-level delimiter.

And of course the user should be given the option of changing defaults.

ændrük
  • 78,496
marc
  • 9
0

Extending @alberge answer, you can execute the following python3 script to change all your profiles to do this:

#!/usr/bin/python3

import subprocess

command = ["dconf", "list", "/org/gnome/terminal/legacy/profiles:/"]
result = subprocess.run(command, stdout=subprocess.PIPE, stderr=subprocess.PIPE, universal_newlines=True)

profiles = result.stdout.split('\n')

for profileString in profiles:
    if profileString.startswith(":"):
        changeCmdPart = "/org/gnome/terminal/legacy/profiles:/" + profileString + "word-char-exceptions"
        changeCmd = ["dconf", "write", changeCmdPart, '@ms "-#%&+,./:=?@_~"']
        subprocess.run(changeCmd)

print("done!")

Or you can just execute:

curl -s http://scripts.programster.org/scripts/5?output=raw | python3
Programster
  • 6,039