Activity

1. Egmont Koblinger (egmontkob)

   added

   Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Complex enough to require an in depth planning process and actual budgeted, scheduled work.

   on Oct 5, 2019
2. ghost added

   Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting

   on Oct 5, 2019
3. ghost added

   Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirements

   on Oct 5, 2019
4. Dustin L. Howett (MSFT) (DHowett-MSFT)

   added

   Area-SettingsIssues related to settings and customizability, for console or terminalIssues related to settings and customizability, for console or terminal

   Product-TerminalThe new Windows Terminal.The new Windows Terminal.

   on Oct 7, 2019
5. ghost removed

   Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirements

   on Oct 7, 2019
6. Mike Griese (zadjii-msft)

   added

   Help WantedWe encourage anyone to jump in on these.We encourage anyone to jump in on these.

   Issue-TaskIt's a feature request, but it doesn't really need a major design.It's a feature request, but it doesn't really need a major design.

   and removed

   Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Complex enough to require an in depth planning process and actual budgeted, scheduled work.

   on Oct 24, 2019
7. Mike Griese (zadjii-msft)

   added this to the Terminal v1.0 milestone on Oct 24, 2019
8. Dustin L. Howett (MSFT) (DHowett-MSFT)

   removed

   Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting

   on Oct 29, 2019
9. Kayla Cinnamon (cinnamon-msft)

   modified the milestones: Terminal v1.0, Terminal v1.x on Jan 23, 2020
10. Kayla Cinnamon (cinnamon-msft)

    added

    Priority-3A description (P3)A description (P3)

    v1-Scrubbed

    on Jan 23, 2020
11. Carlos Zamora (carlos-zamora)

    self-assigned this

    on May 12, 2020
12. Kayla Cinnamon (cinnamon-msft)

    modified the milestones: Terminal v1.x, Terminal v2.0 on Sep 29, 2020
13. Mike Griese (zadjii-msft)

    modified the milestones: Terminal v2.0, 22H2 on Jan 4, 2022
14. Dustin L. Howett (DHowett)

    removed

    v1-Scrubbed

    on Feb 7, 2022
15. zadjii-msft commented on Nov 15, 2022

    

    Mike Griese (zadjii-msft)

    on Nov 15, 2022

    Member

    More actions

    Notes from #14374 and #14392:

    The variety here is staggering! 😄

    Yeah, I was just experimenting with a few terminals I have on my test VM. This is what I established after a lot of double-clicking (might be a couple of errors, but you get the idea).

    Xterm		"$'()*;<>[\]^`{|}
    Gnome Terminal	!"$'()*:;<>[]^`{|}
    Konsole		!"$'()*,;<>[\]^`{|}
    Rxvt		&();<>|
    Alacritty	"'(),:<>[]`{|}
    Kitty		!"$'()*,:;<>[\]^`{|}
    

    They do seem fairly consistent about avoiding the *nix path separator though, so that's perhaps something worth noting. Obviously they're less likely to care about the Windows path separator.

    For the record, I couldn't care less.

    ---

    I'm sorry for the entirely unrelated comment, but I think I just now realized how "crazy" those ASCII word delimiters are in an international setting. For instance this:

    ねこはかわいい。

    It consists of 3 words and a delimiter (ねこ , は , かわいい , 。) and your browser probably handles this correctly, whereas terminals are perpetually stuck in the "What do you mean there are people who don't speak English?". conhost's whitespace-only splitting doesn't feel any better in that regard. I feel like terminals are in a dire need of some UAX #29, Section 4.

    ---

    [...] I think I just now realized how "crazy" those ASCII word delimiters are in an international setting. For instance this:

    ねこはかわいい。

    It consists of 3 words and a delimiter (ねこ , は , かわいい , 。) and your browser probably handles this correctly, whereas terminals are perpetually stuck in the "What do you mean there are people who don't speak English?". conhost's whitespace-only splitting doesn't feel any better in that regard. I feel like terminals are in a dire need of some UAX #29, Section 4.

    Proposed technical implementation details (optional)

    • Use this by default: unicode.org/reports/tr29/#Word_Boundaries
    • Use character-set splitting, if the user has configured wordDelimiters

    ---

    and your browser probably handles this correctly

    For the record, my browser (Firefox) does not.

    And while I agree that it's worthwhile considering a more international-friendly approach, we also need to bear in mind that command-line text selection is possibly somewhat different from typical document text selection, so sticking strictly to the UAX#29 spec may not be ideal as a default (assuming we're considering changing the default).

    For example, in a terminal, the decision as to whether a punctuation character should be treated as a separator or not is often based on the semantics of that characters in the shell (e.g. slash as a path separator, or colon as a drive letter suffix). I haven't looked at the UAX#29 spec in detail, but I suspect it is unlikely to categorize punctuation symbols in the same way.

    And in your example above, if those characters were used in a path, and you were trying to select that path, would you really want the selection to stop at the word boundaries? I don't know. That's really a question for the people that speak the language, and in what situations they're most likely to be double clicking on strings of Japanese characters. But my point is that it's not necessarily obvious that UAX#29 would be best default.
16. Mike Griese (zadjii-msft)

    unassigned

    Carlos Zamora (carlos-zamora)

    on Nov 15, 2022
17. Mike Griese (zadjii-msft)

    modified the milestones: 22H2, Backlog on Nov 15, 2022
18. radekg commented on Mar 13, 2023

    

    Radek Gruchalski (radekg)

    on Mar 13, 2023

    More actions

    For the reference:

    "wordDelimiters": " ()\"':,;<>~!@#$%^&*|=[]{}?│",
    

    to mimic the setting from iTerm2. It treats /-+\~_. as part of the word allowing a selection of a full path and a word containing dashes, for example a repository name.