Triple-click doesn't select entire line

[lilyball]

Triple-click isn't selecting the entire line. In particular, it won't select leading whitespace, or the trailing newline. This diverges from macOS standard text selection behavior.

[mitchellh]

This is a design decision we've done on purpose. I'll leave this open to gather more feedback from others but this isn't something I plan to change unless there is overwhelming support.

[lilyball]

With macOS text selection if you don't want leading spaces it's really easy to just double-click the first word and drag to the right. But the current behavior makes it very hard to select and paste some output verbatim from the terminal somewhere, since leading spaces are lost. And if I triple-click and drag down the subsequent lines do select leading whitespace, so it makes the first line inconsistent with the rest.

[sttts]

Was hitting this too in my git push workflow:

Git outputs the git push with leading spaces. Pasting it like that is convenient as the command with leading space will not end up in the shell history. I don't want every git push for every feature branch in my history.

[xsYf6tdq8]

I'm hitting a similar white space issue for my use case being markdown text with two trailing spaces to indicate a new line (GitLab Markdown).

I have some text including white spaces and the control characters.

$ mklog | cat -e
## [ 1.0.0 ] - 2025.01.29  $
$
### Added  $
- New stuff. !1914  $

But no matter which clipboard-trim-trailing-spaces configuration I use I'm unable to copy the white spaces correctly. There is no distinction between white space coming from the host and white space displayed to fill up your terminal width.

gnome-terminal shows this distinction when selecting text: