Issue 1:
Environment

OS:

Platform ServicePack Version VersionString
-------- ----------- ------- -------------
Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0

Terminal:

> get-appxpackage Microsoft.WindowsTerminal

Name : Microsoft.WindowsTerminal
Publisher : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture : X64
ResourceId :
Version : 0.6.2951.0
PackageFullName : Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe
InstallLocation : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe
IsFramework : False
PackageFamilyName : Microsoft.WindowsTerminal_8wekyb3d8bbwe
PublisherId : 8wekyb3d8bbwe
IsResourcePackage : False
IsBundle : False
IsDevelopmentMode : False
NonRemovable : False
Dependencies : {Microsoft.VCLibs.140.00_14.0.27323.0_x64__8wekyb3d8bbwe,
Microsoft.VCLibs.140.00.UWPDesktop_14.0.27629.0_x64__8wekyb3d8bbwe}
IsPartiallyStaged : False
SignatureKind : Store
Status : Ok

I suspect I'm seeing the crash mentioned in PR #3027. While I can't recall the specific build number for Terminal that I first installed on this particular machine, it was one of the 0.5 releases. all versions I've tried from that first one to the version listed above by get-appxpackage have failed this same way (though I can't faithfully recall if it's been the same Event Viewer entry as reported below). I have used Feedback hub twice, I believe with different versions.

Steps to reproduce

Click Windows Terminal (Preview) in Start menu

Expected behavior

Application launches

Actual behavior

Empty Window frame is drawn, then closes. This is in Event Viewer under Windows Logs > Application

Faulting application name: WindowsTerminal.exe, version: 1.0.1910.22001, time stamp: 0x5daf7ab2
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.18362.356, time stamp: 0x0825b5b0
Exception code: 0xc000027b
Fault offset: 0x0000000000712cf0
Faulting process id: 0x2b68
Faulting application start time: 0x01d58f6c56566369
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 86621d0f-a0dd-4c17-9530-85a0b42ed873
Faulting package full name: Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Issue 2:
Environment

Windows build number: 1903 18362.267
Windows Terminal version (if applicable): 0.3.2142.0

Steps to reproduce

Window Terminal have to be possible to use internationally.

"international localization" is the keyword which have to remember.

Cant give chars @ $ £ { [ ] } because keymapping ctrl+alt+1-9 kill those keys ex. in swedish, finnish, ... keyboards.

@ = AltGr+2

$ = AltGr+4

...

Expected behavior

After I changed those tabbing keymapping ex. ctrl+shift+1, ctrl+shift+2, ... I got those important shell level characters from my keyboard as they have been since 199x.

Actual behavior

Issue #521 has been same problem, but it looks that this is not same, low level problem has fixed.

Problem is same: AltGr not work. Current problem is easier to fix: Don't kill AltGr in default configuration using ctrl+alt+N (N=1-9) key mapping.