WTE is an all-in-one realtime editor for updating of Windows Terminal settings. This gif is showing wt-editor-cli, a prototype of wte written in node.js. The goal is to create an .exe that can run either as a cli as shown and or host a local static serve and use json-editor to function as a gui.

Info
GitHub
Twitter

Related repositories

• wt-editor-cli - Real-time command-line editor for Windows Terminal settings
• wt-editor-gui - A graphical user interface version of wt-editor-cli
• nateshmbhat's windows-terminal-tweaker - A electron-based windows terminal editor

Prerequisites

• Running Windows 1903 (build >= 10.0.18362.0) or later
• Have installed Windows Terminal Version 1.0.1401.0 or later
• Have installed Rust 1.44.0 or later

Setup

Before doing anything I will highly recommend that you backup you settings.json prior to working with this project.

When running src/setup.bat

• Generates a config.json, which locates the folder of your settings.json (which is located here: %appdata%\..\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\)
• Creates a backup of your current settings (called settings.json.pre.wte.backup in the same folder)
• Prompted to allow administrative rights to powershell, this is for setting a environment variable to the projects folder. As it is not setup yet, then you can easily decline and run the project using cargo run. The environment variable can be found by running powershell -window minimized -command "SystemPropertiesAdvanced" and clicking on Environment variables > System Variables > Path > Scroll to the buttom.
• Creates a .batfile that calls cargo run when typing wte (Granted that the environment variable has been set)

config.json

WTE uses config.json to know what settings.json-file to edit. To debug I would recommend copying your settings.json and changing the settings_folder_path for debug perpose shown below. Default is to your folder of your settings.json

{ 
    "settings_folder_path":"C:/Users/USERNAME/Repos/wte/src/", 
    "asset_path":"...", 
    "questionColor":"lightgray", 
    "errorColor":"red" 
} 

WIP

Additionally step

• If you are running using the Linux-Subsystem you can add alias wte='cmd.exe /c wte' in your ~/.bashrc file.

Contribution

Any contribution is appreciated, their are no formalities, just create a pull request.

Creating Pull Requests

Push your commit to get it back up to your fork: git push origin HEAD Visit Github, click handy “Pull request” button that it will make upon noticing your new branch.