Double-clicking the first command word also selects the prompt

[alescdb]

Hi :-)

Here is my bash prompt (https://gist.github.com/kruton/8345450) :

PS1=$'\\[\E[0m\\]\\[\E[0;41m\\]alex\\[\E[31;42m\\]\\[\E[0;42m\\]\\h\\[\E[32;44m\\]\\[\E[0;44;30m\\]$PWD\\[\E[0;34m\\]\\[\E[0m\\]'

Screencast.From.2026-03-26.08-30-52.mp4

It works ok if I change my prompt to somthing like PS1="test>"

Note that this does not happen with kgx or ptyxis
I'm using main branch (flatpak build).

[miifrommera]

hmm, i can reproduce with bash and zsh, but not with fish; can you also test with fish please?

[alescdb]

fish seems to have a space after it's prompts (at least in mine, I'm using tide).

But you can reproduce with :

function fish_prompt
    set_color -b red normal
    printf 'alex'

    set_color -b green red
    printf ''

    set_color -b green normal
    printf '%s' (prompt_hostname)

    set_color -b blue green
    printf ''

    set_color -b blue black
    printf '%s' $PWD

    set_color blue
    printf ''

    set_color normal
end

(again, OK with kgx, not working in boxxy)

[miifrommera]

first of, thank you a lot for the effort you put on this ..but, i believe the actual bug is on VTE (Ptyxis and kgx); they cant even select the last character of your prompt (that arrow) on double click; ; if there is not an empty cell between characters, the terminal should select them all;

it's also how it works in Ghostty (always check with Ghostyy not VTE), but you can clearly see the bug if you copy that arrow 3-4 times and try to double click select it with VTE; it fails it, the same way it fails to pick it in your original observation

if we are good, please close this issue; also in advanced settings you can display the grid! kinda helps!

[alescdb]

Too me, it looks more like a feature :
https://gitlab.gnome.org/GNOME/vte/-/blob/master/src/vte.cc?ref_type=heads#L5681

U+E0B0, is commonly used as a Powerline separator glyph.
It belongs to the Unicode Private Use Area.

https://www.unicode.org/versions/Unicode17.0.0/core-spec/chapter-23/
https://www.unicode.org/charts/PDF/UE000.pdf

[miifrommera]

i see, perhaps the correct way to solve this is to introduce a escape characters list? and expose it in Advanced Settings so everyone can pick the behavior

[alescdb]

From what I understand from the vte code (don’t quote me on that), they do the opposite, they allow certain characters/ranges to be part of a word.
But your solution should work too.

[miifrommera]

i will leave that open a for bit (or long!), because there more important stuff (and i dont think thats gonna be easy anyway!), but meanwhile add a space to your prompt! it was freaking me out there wasn't any room between the command!