Terminal: There is no merits in one-liner text terminal prompt - go full-blown text windows

[sq2500]

Description of the new feature/enhancement

There is no merits in one-liner text terminal console - boldly use proper IDE text windows

• With 2K, 4K display "estate" it make absolute no sense to stick with one-liner terminal prompts
• enable multiple split-view windows like a text editor.

Enables better integration across traditional keystroke/shortcuts UI, GUI and mouse-clicks.
One-line prompt were invented in days with limited resources.

Today Console UI's does not need to follow in "exact" same foot steps - proper editor windows would supplement the Console UI more conveniently when it comes to features such as history, searches, line numbers, also ease script editing.

Multiple split-view windows would be kind of loading various (text) files from last or save session together a interactive script interpreter.

VS Code has most of the plumping, line-by-line debugging already.
Keyboard shortcuts easy accessible by and re-assignable.

Features like on-the-fly filenames highlighting (current folder, folders in the path), Output redirection, Output Error codes & Hyper Linking, Line numbers etc. could major productivity gain benefits over a more traditional one-liner console prompt interface.

Text-click selection expansion similar to Excel cell selection range expansion.
Browser like ALT+click to open/launch/clipboard/buffer copy for selected text.
MDI split screen views for file load, file save, history will make it easier for the console users.

Combination of both GUI keyboard shortcuts, traditional console keyboard shortcuts enable larger user base, also make it easier for newbies.

Traditional Console keyboard shortcuts should take precedence, also allow conflicting GUI keyboard shortcuts to reassigned or preferably used by keyboard modifier keys.

F. ex.:
WIN key ==> GUI
CTRL/ALT/SHIFT key ==> console

"Standard" keyboard shortcuts could be used in a larger context, also more quickly become "natural".
Configurable mouse-click interactions with the console prompt.

Enables Terminal console UI interaction with Windows GUI applications.

Proposed technical implementation details (optional)

Split screen buffer views: 0..9, Q-P (scrollable splitview windows)
Side by side buffer views for copy/paste/diff/highlighting

"Standard" window buffers available for copy/paste/search/replace/regexp (NFA)
Buffer 0: Clipboard Text
Buffer 1: Search, Replace output
Buffer 2: Filenames, symbol links, (folder view)
Buffer 3: Matched searches/replaced (like find all)
Buffer 4: Command History
Buffer 5: Filename History (recent filelist)
Buffer 6: Edit history (column-view of keystroke, filename, date/time like VS Code Ctrl+K+S)
Buffer 7: Diff history
Buffer 8: Regexp history
Buffer 9: Output history applications (stdout, stderr, date/time)

Re-assignable keyboard shortcuts.
Traditional keyboard shortcuts take precedence over conflicting GUI shortcuts.
Keyboard modifier keys, WIN+ for GUI, CTL+ALT+SHIFT combination for Terminal
Proper editing in Text window and also faster than "spinning" single text-line "up-down"

Proposed technical implementation details (optional)

[DHowett-MSFT]

We have a policy against filing one issue that contains, like, a hundred feature requests. There's a whole bunch of these that have already been filed, and I really appreciate you taking the time to write this up. I'll break a couple of them down:

• One-line prompts
  
  
  
  • every shell in existence now allows you to customize your prompt -- and I think that by providing a short prompt by default we _encourage_ people to customize them.
  
  
• Split panes #1000
• Highlighting of directories, filenames
  
  
  
  • This shouldn't be provided by the terminal.
  
  
• Text-click selection expansion -- like, double-click and triple-click combined with dragging? That already exists as of 0.4
• All of our key bindings are customizable, and you can set key bindings that interact with the terminal UI
• configurable mouse bindings #1553

[DHowett-MSFT]

/dup #1553 #1000 #1933 #2285

[msftbot[bot]]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

[sq2500]

I do not agreed, there might be some overlap
Please do a review by human

[DHowett-MSFT]

dude, I AM A HUMAN.

[sq2500]

OK, where do You see the duplication - my core intent is to have more window like seamless integration of the terminal

[DHowett-MSFT]

Half of the things you asked for are possible today, with integration from the shell and some additional text-mode programs.

[sq2500]

What do I need to cut or refrase?

[DHowett-MSFT]

Please review the work items I've linked to this one (#1553 #1000 #1933 #2285 #2046 #1595 #605) and consider filing _individual_ feature requests for the other ones you need. Some of these things are totally out of our control, though. The _shell_ (we do not own the shell) controls the prompt and the text editing experience. The other things, we'll have to discuss individually.

Thanks!

[sq2500]

OK - thanks for Your review