Issue 1:
Environment

Windows build number: Microsoft Windows [version 10.0.18362.295]
Windows Terminal version (if applicable): Version: 0.3.2171.0

Steps to reproduce

Install Windows Terminal

Install a Linux Distribution from Windows Store

Enable the Windows Subsystem for Linux

Reboot

Launch the WSL distro and configure it

Reboot

Expected behavior

Display the WSL distro in the profiles list

Or add easy way to add it

Actual behavior

The WSL distro not appear in the profiles list

Issue 2:
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)