### Define Starting Directory for Cmder

Source: https://github.com/cmderdev/cmder/wiki/Seamless-Windows-Terminal-Integration

Modifies the Cmder profile to open in a specific directory upon startup instead of the default user home directory.

```json
{
    "guid": "{00000000-0000-0000-ba54-000000000132}",
    "commandline": "cmd.exe /k \"%cmder_root%/vendor/init.bat\"",
    "startingDirectory": "E:/Codes/",
    "name": "Cmder",
    "icon": "%cmder_root%/icons/cmder.ico",
    "hidden": false
}
```

--------------------------------

### Install Bash from Babun in Cmder

Source: https://github.com/cmderdev/cmder/wiki/Customization

This snippet shows how to configure Cmder to launch a Bash shell installed via Babun. It includes setting the icon and the command to execute, utilizing conemu-cyg-64.exe for launching the Bash executable from the Babun installation directory.

```bash
set "PATH=%ConEmuBaseDirShort%\wsl;%PATH%" & %ConEmuBaseDirShort%\conemu-cyg-64.exe -new_console:p C:\Users\yourname\.babun\cygwin\bin\bash.exe --login -i
```

--------------------------------

### Install Bash from Cygwin in Cmder

Source: https://github.com/cmderdev/cmder/wiki/Customization

This snippet provides the command to configure Cmder to launch a Bash shell installed via Cygwin. It specifies the icon and the command to execute, including setting the PATH and using conemu-cyg-64.exe to launch the Bash executable.

```bash
set "PATH=%ConEmuBaseDirShort%\wsl;%PATH%" & %ConEmuBaseDirShort%\conemu-cyg-64.exe -new_console:p C:\cygwin64\bin\bash.exe --login -i
```

--------------------------------

### Install PowerShell Modules for Prompt Customization

Source: https://github.com/cmderdev/cmder/wiki/Customization

Commands to install Posh-Git and Oh-My-Posh modules via PowerShellGet to enhance terminal prompts with Git status and themes.

```powershell
Install-Module posh-git -Scope CurrentUser
Install-Module oh-my-posh -Scope CurrentUser
```

--------------------------------

### Customize Shell Startup Arguments

Source: https://github.com/cmderdev/cmder/wiki/Seamless-Hyper-integration

Provides examples for setting custom tab titles, changing the default startup directory, and combining both functionalities. Note the requirement to escape spaces with a caret (^) symbol in paths.

```javascript
// Set tab title
shellArgs: ['/k', 'title Cmder & %CMDER_ROOT%\\vendor\\init.bat'],

// Set custom directory
shellArgs: ['/k', 'cd /d D:\\Custom^ Folder & %CMDER_ROOT%\\vendor\\init.bat'],

// Combined configuration
shellArgs: ['/k', 'cd /d D:\\Custom^ Folder & title Cmder & %CMDER_ROOT%\\vendor\\init.bat']
```

--------------------------------

### Escape Spaces and Special Characters in Windows Paths

Source: https://github.com/cmderdev/cmder/wiki/Seamless-FluentTerminal-Integration

This example demonstrates how to escape spaces and special characters like parentheses in Windows paths for command-line interpreters. This is often necessary when installing applications like Cmder in directories with spaces or special characters to avoid command execution errors. The caret symbol (^) is used to escape the following character.

```cmd
"C:\Program^ Files^ ^(x86^)\Cmder"
```

--------------------------------

### Profile.d Scripts for Automatic Execution (Batch)

Source: https://context7.com/cmderdev/cmder/llms.txt

Drop scripts into the profile.d folder for automatic execution at startup across different shell types. This example shows a batch script for setting development environment variables.

```batch
:: File: %CMDER_ROOT%\config\profile.d\dev_env.cmd
:: Automatically sourced for cmd.exe sessions

@echo off
:: Set development environment variables
set NODE_ENV=development
set JAVA_HOME=C:\Program Files\Java\jdk-17
set PATH=%JAVA_HOME%\bin;%PATH%

:: Set proxy if on corporate network
if defined USERDNSDOMAIN (
    set HTTP_PROXY=http://proxy.corp.com:8080
    set HTTPS_PROXY=http://proxy.corp.com:8080
)

echo Development environment loaded.
```

--------------------------------

### Bash Prompt Customization Example

Source: https://github.com/cmderdev/cmder/wiki/Customization

This bash script demonstrates how to customize the Bash prompt in Cmder. It defines ANSI escape sequences for colors, creates a `prompt_command` function to display Git branch and status information, and sets the prompt to be colorful and informative.

```bash
# Define colors
RED="\e[1;31m"
GREEN="\e[1;32m"
YELLOW="\e[1;33m"
BLUE="\e[1;34m"
MAGENTA="\e[1;35m"
CYAN="\e[1;36m"
WHITE="\e[1;37m"
RESET="\e[0m"

# Define prompt command
function prompt_command {
  # Check if the current directory is a git repository
  if git rev-parse --git-dir > /dev/null 2>&1;
    then
    # Get the current branch name
    branch=$(git branch --show-current)
    # Get the current status
    status=$(git status --short | wc -l)
    # Set the color and icon based on the status
    if [ $status -eq 0 ];
      then
      color=$GREEN
      icon="✔"
    else
      color=$RED
      icon="✘"
    fi
    # Set the git part of the prompt
    git_part="[$color$branch$RESET $color$icon$RESET]"
  else
    # Set the git part of the prompt to empty
    git_part=""
  fi
}

```

--------------------------------

### Handling Spaces in Paths for Cmder in VS Code Settings

Source: https://github.com/cmderdev/cmder/wiki/Seamless-VS-Code-Integration

When installing Cmder in a path containing spaces, you need to escape these spaces and special characters in your VS Code settings.json. This example shows how to format a path with spaces and parentheses for use in the settings.

```plaintext
C:\Program Files (x86)\Cmder  →  "C:\\Program^ Files^ ^(x86^)\\Cmder"
```

--------------------------------

### Profile.d Scripts for Automatic Execution (PowerShell)

Source: https://context7.com/cmderdev/cmder/llms.txt

Drop scripts into the profile.d folder for automatic execution at startup across different shell types. This example shows a PowerShell script for setting development environment variables and importing modules.

```powershell
# File: %CMDER_ROOT%\config\profile.d\dev_env.ps1
# Automatically sourced for PowerShell sessions

# Set development environment
$env:NODE_ENV = "development"
$env:JAVA_HOME = "C:\Program Files\Java\jdk-17"
$env:PATH = "$env:JAVA_HOME\bin;$env:PATH"

# Import useful modules if available
if (Get-Module -ListAvailable -Name posh-git) {
    Import-Module posh-git
}
```

--------------------------------

### Bash/Mintty Profile Configuration (Bash)

Source: https://context7.com/cmderdev/cmder/llms.txt

Customize Bash sessions with portable settings that follow your Cmder installation. This script is typically located at $CMDER_ROOT/config/user_profile.sh.

```bash
# File: $CMDER_ROOT/config/user_profile.sh

# Set custom prompt
export PS1='[\e[1;32m]\u@\h[\e[0m]:[\e[1;34m]\w[\e[0m]\$ '

# Common aliases
alias ll='ls -la'
alias la='ls -A'
alias l='ls -CF'
alias ..='cd ..'
alias ...='cd ../..'
alias grep='grep --color=auto'

# Git aliases
alias gs='git status'
alias ga='git add'
alias gc='git commit'
alias gp='git push'
alias gl='git log --oneline -10'
alias gd='git diff'
alias gco='git checkout'

# Custom functions
mkcd() {
    mkdir -p "$1" && cd "$1"
}

# Extract various archive types
extract() {
    if [ -f "$1" ]; then
        case "$1" in
            *.tar.bz2) tar xjf "$1" ;;
            *.tar.gz)  tar xzf "$1" ;;
            *.bz2)     bunzip2 "$1" ;;
            *.gz)      gunzip "$1" ;;
            *.tar)     tar xf "$1" ;;
            *.zip)     unzip "$1" ;;
            *.7z)      7z x "$1" ;;
            *)         echo "'$1' cannot be extracted" ;;
        esac
    else
        echo "'$1' is not a valid file"
    fi
}

# Set editor
export EDITOR=vim
export VISUAL=vim

# Add custom paths
export PATH="$HOME/bin:$PATH"

# Source additional configs
if [ -f "$HOME/.bash_aliases" ]; then
    . "$HOME/.bash_aliases"
fi
```

--------------------------------

### Launching VS Code with Cmder at Startup

Source: https://github.com/cmderdev/cmder/wiki/Seamless-VS-Code-Integration

This configuration snippet is used to automatically launch VS Code at startup when Cmder starts, along with its built-in terminal. It specifies the command and arguments to execute.

```json
{
    "args": ["/k", "${env:cmder_root}\\vendor\\bin\\vscode_init.bat", "/noautorun"]
}
```

--------------------------------

### Install Hyper Plugins for Cmder UI

Source: https://github.com/cmderdev/cmder/wiki/Seamless-Hyper-integration

Adds recommended plugins to the Hyper configuration to replicate the Cmder visual experience, including color schemes and status bars.

```javascript
plugins: [
	'hyperterm-monokai',
	'hyper-tab-icons',
	'hyper-statusline'
]
```

--------------------------------

### Running VS Code at Startup from user-profile.cmd

Source: https://github.com/cmderdev/cmder/wiki/Seamless-VS-Code-Integration

This batch command is placed in the user-profile.cmd file to ensure VS Code is launched at startup when Cmder starts. It uses the '%ccall%' feature and passes arguments to the VS Code executable.

```batch
%ccall% NOT "/noautorun" "start" "%cmder_root%\bin\vsCode\Code.exe %*"
```

--------------------------------

### Advanced Cmder Shell Extension Setup (Registry)

Source: https://github.com/cmderdev/cmder/wiki/Context-menu-integration

This registry script sets up an advanced shell extension for Cmder, allowing for more customization like reusing existing instances and specifying console behavior. It targets different shell contexts including directories, directory backgrounds, and drives. Ensure the paths to Cmder.exe and icons are correct for your system.

```registry
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Directory\Background\shell\ConEmu_Cmder]
@="ConEmu/Cmder Here"
"NoWorkingDirectory"=""
"Icon"="C:\\Users\\vagrant\\cmderdev\\icons\\cmder_red.ico"

[HKEY_CLASSES_ROOT\Directory\Background\shell\ConEmu_Cmder\command]
@=""C:\\Users\\vagrant\\cmderdev\\Cmder.exe" -- -reuse -run {cmd::Cmder} -new_console:d:"%V":t:"ConEmu - Cmder" "

[HKEY_CLASSES_ROOT\Directory\shell\ConEmu_Cmder]
@="ConEmu/Cmder Here"
"NoWorkingDirectory"=""
"Icon"="C:\\Users\\vagrant\\cmderdev\\icons\\cmder_red.ico"

[HKEY_CLASSES_ROOT\Directory\shell\ConEmu_Cmder\command]
@=""C:\\Users\\vagrant\\cmderdev\\Cmder.exe" -- -reuse -run {cmd::Cmder} -new_console:d:"%V":t:"ConEmu - Cmder" "

[HKEY_CLASSES_ROOT\Drive\Background\shell\ConEmu_Cmder]
@="ConEmu/Cmder Here"
"NoWorkingDirectory"=""
"Icon"="C:\\Users\\vagrant\\cmderdev\\icons\\cmder_red.ico"

[HKEY_CLASSES_ROOT\Drive\Background\shell\ConEmu_Cmder\command]
@=""C:\\Users\\vagrant\\cmderdev\\Cmder.exe" -- -run {cmd::Cmder} -new_console:d:"%V""t:"ConEmu - Cmde" "

[HKEY_CLASSES_ROOT\Drive\shell\ConEmu_Cmder]
@="ConEmu/Cmder Here"
"NoWorkingDirectory"=""
"Icon"="C:\\Users\\vagrant\\cmderdev\\icons\\cmder_red.ico"

[HKEY_CLASSES_ROOT\Drive\shell\ConEmu_Cmder\command]
@=""C:\\Users\\vagrant\\cmderdev\\Cmder.exe" -- -reuse -run {cmd::Cmder} -new_console:d:"%V":t:"ConEmu - Cmder" "
```

--------------------------------

### Auto-start SSH Agent for Git Operations (Batch)

Source: https://context7.com/cmderdev/cmder/llms.txt

This batch script, intended for the user_profile.cmd file, automatically starts the SSH agent when Cmder is launched. This is crucial for seamless Git operations over SSH, eliminating the need for manual agent startup.

```batch
:: File: %CMDER_ROOT%\config\user_profile.cmd
:: Uncomment or add this line to auto-start SSH agent

@call "%GIT_INSTALL_ROOT%\cmd\start-ssh-agent.cmd"
```

--------------------------------

### Verify Cmder installation via command line

Source: https://github.com/cmderdev/cmder/wiki/Setting-up-Environment-Variables

Use the 'where' command in a Windows terminal to verify if cmder.exe is correctly recognized by the system PATH. It returns the file path if found or an error if not configured.

```batch
where cmder.exe
```

--------------------------------

### Auto-start SSH Agent for Git Operations (Bash)

Source: https://context7.com/cmderdev/cmder/llms.txt

This Bash script, for user_profile.sh, configures Cmder's Bash environment to automatically start the SSH agent and add the default SSH key. This simplifies secure Git operations within Bash sessions.

```bash
# File: $CMDER_ROOT/config/user_profile.sh
# Start SSH agent for bash sessions

# Start ssh-agent if not running
if [ -z "$SSH_AUTH_SOCK" ]; then
    eval "$(ssh-agent -s)"
fi

# Add default key
ssh-add ~/.ssh/id_rsa 2>/dev/null
```

--------------------------------

### Set Custom Default Directory in Hyper (JavaScript)

Source: https://github.com/cmderdev/cmder/wiki/Seamless-Hyper-integration

Sets a custom starting directory for Hyper when launching Cmder. The `shellArgs` are modified to include a `cd` command. Paths with spaces must escape spaces with a `^` character.

```javascript
"shellArgs": ["/k", "cd /d D:\Custom^ Folder & %CMDER_ROOT%\vendor\init.bat"],

```

--------------------------------

### Configure Cmder Cmd Profile in Fluent Terminal

Source: https://github.com/cmderdev/cmder/wiki/Seamless-FluentTerminal-Integration

This configuration defines a new profile in Fluent Terminal for running Cmder's default cmd shell. It specifies the executable, working directory, arguments to initialize Cmder, the chosen theme, and a keyboard shortcut for quick access. Ensure the CMDER_ROOT environment variable is set correctly.

```batch
C:\Windows\System32\cmd.exe
/k title Cmder/Cmd & "%CMDER_ROOT%\vendor\init.bat"
```

--------------------------------

### Configure Cmder Bash Profile in Fluent Terminal

Source: https://github.com/cmderdev/cmder/wiki/Seamless-FluentTerminal-Integration

This configuration sets up a profile in Fluent Terminal to run the Bash shell included with Git for Windows, integrated with Cmder. It requires manually specifying the path to bash.exe and setting the working directory. Arguments are provided for a login shell. Note that environment variables like CMDER_ROOT might not resolve directly in this field and may need to be replaced with the absolute path.

```bash
[CMDER_ROOT]\vendor\git-for-windows\bin\bash.exe
--login -i
```

--------------------------------

### Cmder Split-Pane Configuration Options (Text)

Source: https://github.com/cmderdev/cmder/wiki/Seamless-Sublime-Text-3-Integration

Illustrates the command-line switches used in Cmder to configure split-pane behavior for launching applications. These options specify whether the split is horizontal or vertical and the percentage of screen space each pane occupies.

```text
-new_console:s or -new_console:s50H
--new_console:s50V
```

--------------------------------

### Configure Cmder with PowerShell Shell

Source: https://github.com/cmderdev/cmder/wiki/Seamless-FluentTerminal-Integration

This snippet shows the arguments needed to configure Cmder to use PowerShell as its shell. It bypasses the execution policy, avoids loading profiles and logos, and ensures the PowerShell session remains open to execute a custom profile script. Ensure to replace '[CMDER_ROOT]' with the actual installation path.

```powershell
-ExecutionPolicy Bypass -NoLogo -NoProfile -NoExit -Command "Invoke-Expression '. ''[CMDER_ROOT]\vendor\profile.ps1'''"
```

--------------------------------

### Configure SSH Agent Startup

Source: https://github.com/cmderdev/cmder/blob/master/README.md

Commands to initialize the SSH agent manually or automatically upon Cmder startup by modifying the user profile.

```batch
start-ssh-agent
@call "%GIT_INSTALL_ROOT%/cmd/start-ssh-agent.cmd"
```

--------------------------------

### Cmder.exe Command Line Arguments

Source: https://context7.com/cmderdev/cmder/llms.txt

Launch Cmder with various arguments to control startup behavior, such as specifying custom configuration paths, registering context menus, selecting tasks, or forwarding parameters to ConEmu.

```batch
:: Start Cmder with individual user config folder
cmder.exe /C %userprofile%\cmder_config

:: Register "Cmder Here" context menu for all users (requires Admin)
cmder.exe /REGISTER ALL

:: Unregister context menu for current user only
cmder.exe /UNREGISTER USER

:: Start Cmder in single mode in a specific directory
cmder.exe /SINGLE /START "C:\Projects\MyApp"

:: Start with a specific task
cmder.exe /TASK "PowerShell as Admin"

:: Use machine-specific ConEmu settings
cmder.exe /M

:: Forward parameters directly to ConEmu
cmder.exe /X "-run {cmd::Cmder} -new_console:d:C:\Projects"
```

--------------------------------

### Configure PowerShell for Cmder

Source: https://github.com/cmderdev/cmder/wiki/Seamless-Windows-Terminal-Integration

Sets up a profile to run PowerShell with Cmder initialization scripts instead of the default clink shell.

```json
{
    "guid": "{00000000-0000-0000-ba54-000000000127}",
    "name": "Cmder :: Powershell",
    "commandline": "%SystemRoot%/System32/WindowsPowerShell/v1.0/powershell.exe -ExecutionPolicy Bypass -NoLogo -NoProfile -NoExit -Command \"Invoke-Expression '. ''%cmder_root%/vendor/profile.ps1'''\"",
    "icon": "%cmder_root%/icons/cmder.ico"
}
```

--------------------------------

### Add Cmder to Windows PATH variable

Source: https://github.com/cmderdev/cmder/wiki/Setting-up-Environment-Variables

Instructions for appending the Cmder installation directory to the Windows PATH environment variable. This allows users to launch Cmder from any terminal or explorer window.

```shell
C:\bin\Cmder
```

```shell
;C:\bin\Cmder
```

--------------------------------

### Configure Development Environments

Source: https://context7.com/cmderdev/cmder/llms.txt

Sets up development environment variables, aliases, and helper functions for PowerShell and Bash sessions. These scripts are typically sourced during shell startup to ensure consistent tooling paths and environment variables.

```powershell
function Start-DevServer {
    param([string]$Port = "3000")
    npm run dev -- --port $Port
}

Write-Host "PowerShell development environment loaded." -ForegroundColor Green
```

```bash
export NODE_ENV=development
export JAVA_HOME="/c/Program Files/Java/jdk-17"
export PATH="$JAVA_HOME/bin:$PATH"

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"

alias serve='python -m http.server'
alias dc='docker-compose'
alias k='kubectl'

echo "Bash development environment loaded."
```

--------------------------------

### Manage PowerShell Themes and Profile Editing

Source: https://github.com/cmderdev/cmder/wiki/Customization

Utility commands to list available Oh-My-Posh themes and open the current user's PowerShell profile in Notepad for editing.

```powershell
Get-PoshThemes
notepad $PROFILE.CurrentUserAllHosts
```

--------------------------------

### Configure Shell Prompt (Bash/Shell)

Source: https://github.com/cmderdev/cmder/wiki/Customization

Set the PROMPT_COMMAND and PS1 variables to customize the appearance of your shell prompt. This allows for dynamic information display, such as username, host, current directory, and Git status.

```shell
# Set the prompt command
PROMPT_COMMAND=prompt_command

# Set the PS1 variable
PS1="$CYAN\u@\h$RESET $YELLOW\w$RESET $git_part $MAGENTAλ$RESET "
```

--------------------------------

### Configure PowerShell User Profile

Source: https://github.com/cmderdev/cmder/wiki/Customization

Instructions for importing modules and setting themes in the user-profile.ps1 file to customize the PowerShell session.

```powershell
Import-Module posh-git
Import-Module oh-my-posh
Set-Theme Paradox
```

--------------------------------

### init.bat Command Line Arguments

Source: https://context7.com/cmderdev/cmder/llms.txt

Configure shell initialization behavior through init.bat arguments when setting up custom Cmder tasks. Options include enabling verbose or debug output, timed init mode, fast init mode, custom config paths, and specifying tool preferences.

```batch
:: Basic task command with init.bat
cmd /s /k ""%ConEmuDir%\..\init.bat""

:: Enable verbose output for debugging
cmd /s /k ""%ConEmuDir%\..\init.bat" /v"

:: Enable debug output
cmd /s /k ""%ConEmuDir%\..\init.bat" /d"

:: Enable timed init mode (displays init script timing)
cmd /s /k ""%ConEmuDir%\..\init.bat" /t"

:: Fast init mode (disables some features for speed)
cmd /s /k ""%ConEmuDir%\..\init.bat" /f"

:: Custom user config path for admin sessions
cmd /s /k ""%ConEmuDir%\..\init.bat" /c %userprofile%\cmder_config"

:: Specify custom Git installation root
cmd /s /k ""%ConEmuDir%\..\init.bat" /git_install_root "C:\Program Files\Git""

:: Set custom home directory
cmd /s /k ""%ConEmuDir%\..\init.bat" /home "D:\Users\MyHome""

:: Set max recurse depth for bin folder PATH additions (1-5)
cmd /s /k ""%ConEmuDir%\..\init.bat" /max_depth 3"

:: Configure *nix tools preference (0=none, 1=prefer Windows, 2=prefer *nix)
cmd /s /k ""%ConEmuDir%\..\init.bat" /nix_tools 2"

:: Custom user aliases file
cmd /s /k ""%ConEmuDir%\..\init.bat" /user_aliases "D:\config\my_aliases.cmd""

:: Custom SVN SSH path
cmd /s /k ""%ConEmuDir%\..\init.bat" /svn_ssh "C:\PuTTY\plink.exe""

:: Combined example with custom flags for cexec
cmd /s /k ""%ConEmuDir%\..\init.bat" /v /t /startNotepad /myCustomFlag"
```

--------------------------------

### Define Cmd.exe Aliases

Source: https://github.com/cmderdev/cmder/blob/master/README.md

Create simple or complex aliases for Cmd.exe sessions using the alias command. Complex aliases support parameter substitution using $1-9 or $*.

```batch
alias vi=vim.exe $*
alias name=command
```

--------------------------------

### Configure Cmder Shell Arguments with CMDER_ROOT (JSON)

Source: https://github.com/cmderdev/cmder/wiki/Setting-up-Environment-Variables

This snippet demonstrates how to update the `terminal.integrated.shellArgs.windows` setting in VS Code to use the %CMDER_ROOT% environment variable. This allows Cmder to dynamically reference its installation path for initialization scripts.

```json
{
  "terminal.integrated.shell.windows": "cmd.exe",

  "terminal.integrated.shellArgs.windows": [
      "/k", "%CMDER_ROOT%\\vendor\\init.bat"
  ]
}
```

--------------------------------

### Auto-start SSH Agent for Git Operations (PowerShell)

Source: https://context7.com/cmderdev/cmder/llms.txt

This PowerShell script, for user_profile.ps1, ensures the SSH agent is running for PowerShell sessions within Cmder. It checks if the agent is already active and starts it if necessary, or uses the Git for Windows provided script.

```powershell
# File: %CMDER_ROOT%\config\user_profile.ps1
# Start SSH agent for PowerShell sessions

# Start ssh-agent if not running
$sshAgent = Get-Process ssh-agent -ErrorAction SilentlyContinue
if (-not $sshAgent) {
    Start-SshAgent -Quiet
}

# Or use the Git for Windows ssh-agent
& "$env:GIT_INSTALL_ROOT\cmd\start-ssh-agent.cmd"
```

--------------------------------

### Integrate External Shell Environments

Source: https://github.com/cmderdev/cmder/blob/master/README.md

Instructions for adding external environments like Cygwin or MSys2 as a new task in Cmder. The command uses the -new_console flag to launch the shell within the Cmder window.

```batch
cmd /c "[path_to_external_env]\bin\bash --login -i" -new_console
```

--------------------------------

### Configure Hyper for Cmder Canary (JavaScript)

Source: https://github.com/cmderdev/cmder/wiki/Seamless-Hyper-integration

Modifies the Hyper `hyper.json` file to use `cmd.exe` with Cmder's initialization script. It requires setting the `shell`, `shellArgs`, and `env` properties. Ensure `[cmder_root]` is replaced with your Cmder installation path or the `%CMDER_ROOT%` environment variable is defined.

```javascript
"shell": "cmd.exe",
    "shellArgs": ["/k", "[cmder_root]\vendor\init.bat"],
    "env": {"TERM":"cygwin"},

```

--------------------------------

### Configure Sublime Text 3 Split-Pane in Cmder (Batch)

Source: https://github.com/cmderdev/cmder/wiki/Seamless-Sublime-Text-3-Integration

Defines aliases in `user-aliases.cmd` to launch Sublime Text 3 with different split-pane configurations within Cmder. These aliases utilize the `-new_console:s` switch to control horizontal and vertical splitting and pane sizing.

```batch
sublv="%CMDER_ROOT%\bin\Sublime_Text_3\sublime_text.exe" $* -new_console:s
sublv5="%CMDER_ROOT%\bin\Sublime_Text_3\sublime_text.exe" $* -new_console:s50H
subls5="%CMDER_ROOT%\bin\Sublime_Text_3\sublime_text.exe" $* -new_console:s50V
subls75="%CMDER_ROOT%\bin\Sublime_Text_3\sublime_text.exe" $* -new_console:s75V
```

--------------------------------

### Customize Cmder VS Code Initialization Arguments

Source: https://github.com/cmderdev/cmder/wiki/Seamless-VS-Code-Integration

The vscode_init_args.cmd script allows users to define environment variables and settings specifically for the Cmder instance running inside VS Code. It handles configuration for both internal and external launch scenarios.

```batch
@echo off
echo Applying Cmder VSCode settings from '%~0'...

if defined CMDER_CONFIGURED (
    set CMDER_CONFIGURED=2
) else (
    set nix_tools=0
    set fast_init=1
    set cmder_user_bin=c:\Users\%USERNAME%\.cmder\bin
    set cmder_user_config=c:\Users\%USERNAME%\.cmder\config
)

set verbose_output=1

echo Applying Cmder VSCode settings is complete!
```

--------------------------------

### Implement conditional task execution in Cmder

Source: https://github.com/cmderdev/cmder/blob/master/README.md

Demonstrates how to trigger a specific command based on a flag using the ccall alias. This is typically implemented in the Cmder task configuration and the user_profile.cmd file.

```batch
cmd.exe /k ""%ConEmuDir%\..\init.bat" /startnotepad"

%ccall% "/startNotepad" "start" "notepad.exe"
```

--------------------------------

### Integrate Cmder into Windows Explorer Context Menu (Registry)

Source: https://context7.com/cmderdev/cmder/llms.txt

This registry file adds an 'Open Cmder Here' option to the Windows Explorer right-click context menu for both directories and their backgrounds. It requires the %CMDER_ROOT% environment variable to be set and uses Cmder's executable to open a new instance in the selected directory.

```registry
; File: OpenCmderHere.reg
; Double-click to install, requires %CMDER_ROOT% environment variable

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Directory\Background\shell\Cmder]
@="Open Cmder Here"
"Icon"=""%CMDER_ROOT%\\icons\\cmder.ico",0"

[HKEY_CLASSES_ROOT\Directory\Background\shell\Cmder\command]
@=""%CMDER_ROOT%\\Cmder.exe" /START "%v""

[HKEY_CLASSES_ROOT\Directory\shell\Cmder]
@="Open Cmder Here"
"Icon"=""%CMDER_ROOT%\\icons\\cmder.ico",0"

[HKEY_CLASSES_ROOT\Directory\shell\Cmder\command]
@=""%CMDER_ROOT%\\Cmder.exe" /START "%1""
```

--------------------------------

### Configure Cmder Profile in Windows Terminal

Source: https://github.com/cmderdev/cmder/wiki/Seamless-Windows-Terminal-Integration

Adds a new profile entry to the Windows Terminal settings.json file to launch Cmder using the %CMDER_ROOT% environment variable.

```json
{
    "guid": "{00000000-0000-0000-ba54-000000000132}",
    "commandline": "cmd.exe /k \"%cmder_root%/vendor/init.bat\"",
    "icon": "%cmder_root%/icons/cmder.ico",
    "name": "Cmder",
    "closeOnExit": "graceful",
    "hidden": false
}
```

--------------------------------

### Integrate with Windows Terminal

Source: https://context7.com/cmderdev/cmder/llms.txt

Defines profile configurations for Windows Terminal to launch Cmder using cmd, PowerShell, or Bash. Requires updating the settings.json file in Windows Terminal.

```json
{
    "guid": "{00000000-0000-0000-0000-000000000001}",
    "name": "Cmder",
    "commandline": "cmd.exe /k \"%CMDER_ROOT%\\vendor\\init.bat\"",
    "startingDirectory": "%USERPROFILE%"
}
```