Activity

1. SpitFire-666 (SpitFire-666)

   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 Apr 18, 2021
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 Apr 18, 2021
3. ghost added

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

   on Apr 18, 2021
4. LuanVSO commented on Apr 18, 2021

   

   Luan Vitor Simião Oliveira (LuanVSO)

   on Apr 18, 2021

   Contributor

   More actions

   the ctrl+a selection is handled by PowerShell while the triple click is handed by terminal.
   there's no way for terminal to have the same behavior because it doesn't know where the prompt is or even if there is a prompt in the screen
5. KalleOlaviNiemitalo commented on Apr 19, 2021

   

   Kalle Olavi Niemitalo (KalleOlaviNiemitalo)

   on Apr 19, 2021

   Last edited by KalleOlaviNiemitalo

   More actions

   Shells could be configured to emit FTCS_COMMAND_START from Proprietary Escape Codes of iTerm2, and Windows Terminal could then use that to avoid selecting the prompt. The same marking of prompts would be used in #6232.

   I think cmd.exe and PowerShell already let users embed ESC characters in prompts, so these shells would not have to be changed. Not so sure about Windows PowerShell though.

   👍React with 👍1Reacted by Luan Vitor Simião Oliveira
6. zadjii-msft commented on Apr 19, 2021

   

   Mike Griese (zadjii-msft)

   on Apr 19, 2021

   Member

   More actions

   Huh. Okay, the FTCS_COMMAND_START solution is clever. This would then also require #1553, and some way of setting triple click to "select the whole line up to the prompt (if one exists)". So I guess I'll toss this in on #1553
7. Mike Griese (zadjii-msft)

   added

   Area-InputRelated to input processing (key presses, mouse, etc.)Related to input processing (key presses, mouse, etc.)

   Area-TerminalControlIssues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)

   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.

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

   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 Apr 19, 2021
8. ghost removed

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

   on Apr 19, 2021
9. Mike Griese (zadjii-msft)

   added this to the Terminal Backlog milestone on Apr 19, 2021
10. Mike Griese (zadjii-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 Apr 29, 2021
11. Mike Griese (zadjii-msft)

    modified the milestones: Terminal Backlog, Backlog on Jan 4, 2022
12. zadjii-msft commented on Jul 20, 2023

    

    Mike Griese (zadjii-msft)

    on Jul 20, 2023

    Member

    More actions

    I am TEMPTED to axe this, in favor of the experimental.rightClickContextMenu (#3337, #14775) and shell integration + the "select command" entries added in #15020.

    

    That's not triple click, it's rightclick, move, left click, but still