mintty / wsltty.appx

Mintty is the Cygwin Terminal, as well as the terminal emulator for MSYS (Msys2, old MSYS).

Overview

For an introduction, features overview, and screenshots, see the Mintty homepage.

For detailed hints and specific issues, see the Wiki.

For comprehensive general documentation, see the manual page.

Bugs and Enhancements

Please report bugs or suggest enhancements via the issue tracker.

Bugs that were reported to the previous repository at Google code before June, 2015, have been migrated here.

• Mind! Before reporting an issue about character interaction with an application, please check the issue also with at least one other terminal (xterm, urxvt), and maybe the Cygwin Console. It may also be useful to get a proper understanding of the rôle of a terminal as explained e.g. in difference between a 'terminal', a 'shell', a 'tty' and a 'console'.

Contribution

If you consider to suggest a patch or contribute to mintty otherwise, discuss your proposal in an issue first, or on the Cygwin mailing list, or with the maintainer.

• Repository policy: No unsolicited pull requests!

wsltty.appx's Issues

Discussion: Use newer wslbridge2

I have updated this project to build with newer Windows SDK and to use newer wslbridge2. Here is my test branch https://github.com/Biswa96/wsltty.appx/tree/test. Would you like to test if the package can be built and use?

This is to fix mintty/wsltty#302

Discussion: Launch wsltty as a signed Appx Package or unsigned ZIP file

Continuing discussion from mintty/wsltty #63.

• As a signed Appx: Extract wsltty.zip in the cloned wsltty.appx folder. Then run the build.cmd script which make appx and signed it with users own signed certificate. The folder structure of wsltty.zip will be like following:

Folder structure (click to open)

+---bin
|       cygwin-console-helper.exe
|       cygwin1.dll
|       mintty.exe
|       wslbridge-backend
|       wslbridge.exe
|       
+---usr
    +---share
        +---mintty
            +---lang
            +---themes

But user does need the Windows SDK tools to sign (and may be Build tools). This procedure secures the package installation and user doesn't need to enable Developer mode.

• As a unsigned ZIP: User can download it from release page directly (will be added). Then extract ZIP file and run the command from powershell: Add-AppxPackage -Path <Path_To_AppxManifest.xml> -Register. The folder structure of build folder like following:

Folder structure (click to open)

+build
|
|   AppxManifest.xml
|   resources.pri
|   
+---Assets
|       
+---bin
|       cygwin-console-helper.exe
|       cygwin1.dll
|       Launcher.exe
|       Launcher.exe.config
|       mintty.exe
|       wslbridge-backend
|       wslbridge.exe
|       wsltty.ico
|       
+---usr
    +---share
        +---mintty
            +---lang
            +---themes

With this procedure user does not need any developer tools but needs to enable Developer mode in Settings. This also is not certified.
Further Details will be added later.

build failed

Concerning mintty/wsltty#63 (comment):
After building wslbridge and mintty, makefile invokes build.sh with the following output, with some intermediate popups where I entered certificate passwords; sorry, MS tool messages are in German (unaffected by LC_ALL). I may have to update my tool set for the current Windows version (10, 64 bit, updated yesterday).

cleaning old build artefacts
copying assets
Output location of PRI file(s) is detected to be under the project root. If previously generated PRI file(s) are present, these may be re-indexed and lead to unexpected results.
Index Pass Completed.
AlternateForm Qualifiers: UNPLATED
Scale Qualifiers: 100,125,150,200,400
TargetSize Qualifiers: 256,16,24,32,48

Finished building
Version: 1.0
Resource Map Name: mintty.wsltty
Named Resources: 5
Resource Candidates: 31
Successfully Completed
copying mintty
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1126,5): error MSB3644: Die Verweisassemblys f�r Framework ".NETFramework,Version=v4.6.1" wurden nicht gefunden. Installieren Sie zum Beheben dieses Problems das SDK oder das Paket zur Festlegung vonZielversionen f�r die vorliegende Frameworkversion, oder legen Sie als neues Ziel f�r die Anwendung eine Version des Frameworks fest, f�r die Sie das SDK oder Paket zur Festlegung der Zielversionen installiert haben. Assemblys werden im globalen Assemblycache (GAC) aufgel�st und anstelle von Verweisassemblys verwendet. Daher wird die Assembly f�r das gew�nschte Framework unter Umst�nden nicht ordnungsgem�� als Ziel festgelegt. [C:\cygwin\home\towo\mintty\wsltty.appx\Launcher\Launcher.csproj]
/bin/cp: cannot stat 'Launcher/Launcher.exe': No such file or directory
/bin/cp: cannot stat 'Launcher/Launcher.exe.config': No such file or directory
Microsoft (R) MakeAppx Tool
Copyright (C) 2013 Microsoft. All rights reserved.

The path (/p) parameter is: "\?\C:\cygwin\home\towo\mintty\wsltty.appx\wsltty_unsigned.appx"
The content directory (/d) parameter is: "\?\C:\cygwin\home\towo\mintty\wsltty.appx\build"
Enumerating files from directory "\?\C:\cygwin\home\towo\mintty\wsltty.appx\build"
Packing 56 file(s) in "\?\C:\cygwin\home\towo\mintty\wsltty.appx\build" (content directory) to "\?\C:\cygwin\home\towo\mintty\wsltty.appx\wsltty_unsigned.appx" (output file name).
Memory limit defaulting to 4240934912 bytes.
Using "\?\C:\cygwin\home\towo\mintty\wsltty.appx\build\AppXManifest.xml" as the manifest for the package.
MakeAppx : error: Manifest validation error: Line 5, Column 18, Reason: The file name "bin\launcher.exe" declared for element "[local-name()='Applications']/[local-name()='Application']" doesn't exist in the package.
MakeAppx : error: Package creation failed.
MakeAppx : error: 0x80080204 - The specified package format is not valid: The package manifest is not valid.

TODO: Remove Launcher and execute mintty directly in Appx package

Here are my thoughts:

1. Get execution path with GetModuleFileName() which has only read permission.
2. Get Local\AppData\Package\mintty.wsltty-xxx\LocalCache folder (UWP environment specific) with SHGetKnownFolderPath() which has read/write/execute permission.
3. Copy wslbridge.exe, wslbridge-backend and cygwin1.dll from execution path to LocalCache folder.
4. Execute mintty.exe with parameters having wslbridge.exe in LocalCache folder (like in the C# project).

All functions/variable should be with UNICODE/wide character.