Selecting a shell on startup in the Hyper terminal emulator

hyperstart.bat

@ECHO off
:top
CLS
ECHO Choose a shell:
ECHO [1] cmd
ECHO [2] bash
ECHO [3] PowerShell
ECHO [4] Python
ECHO.
ECHO [5] restart elevated
ECHO [6] exit
ECHO.

CHOICE /N /C:123456 /M "> "
CLS
IF ERRORLEVEL ==6 GOTO end
IF ERRORLEVEL ==5 powershell -Command "Start-Process hyper -Verb RunAs"
IF ERRORLEVEL ==4 python
IF ERRORLEVEL ==3 powershell
IF ERRORLEVEL ==2 bash
IF ERRORLEVEL ==1 cmd

CLS
ECHO Switch or exit?
ECHO [1] Switch
ECHO [2] Exit

CHOICE /N /C:12 /D 2 /T 5 /M "> "
IF ERRORLEVEL ==2 GOTO end
IF ERRORLEVEL ==1 GOTO top

:end

hyperstart.ps1

$knownshells = @(
    @{
        Name       = "CMD"
        Executable = "$env:SystemRoot\System32\cmd.exe"
    },
    @{
        Name       = "Powershell 5.1"
        Executable = "$env:SystemRoot\System32\WindowsPowerShell\v1.0\powershell.exe"
    },
    @{
        Name       = "Powershell 6 (Core)"
        Executable = "$env:ProgramFiles\PowerShell\6\pwsh.exe"
    },
    @{
        Name       = "Powershell 7 (Core)"
        Executable = "$env:ProgramFiles\PowerShell\7\pwsh.exe"
    },
    @{
        Name       = "Bash on Ubuntu"
        Executable = "$env:ProgramFiles\WindowsApps\CanonicalGroupLimited.UbuntuonWindows_1804.2020.5.0_x64__79rhkp1fndgsc\ubuntu.exe"
    },
    @{
        Name       = "Git Bash"
        Executable = "$env:ProgramFiles\Git\git-bash.exe"
    }
) | Where-Object { Test-Path -Path $_.Executable }

"Choose a shell:"

$index = 1; $teststring = ""
foreach ($shell in $knownshells) {
    "[$index] $($shell.Name)"
    $teststring += $index++
}

""

do { $keyPress = [System.Console]::ReadKey() } until ($teststring.Contains($keyPress.Key));

$choice = $knownshells[($keyPress.KeyChar.ToString() -as [int]) - 1]

Start-Process -Path $choice.Executable -NoNewWindow -Wait -ArgumentList $choice.ArgumentList

exit

info.md

Hyperstart

I'm not supporting this anymore - I use Windows Terminal now.

Short script for Windows that allows you to select which shell you want when Hyper starts. As flexible as the windows command line.

Install

1. Grab the script from below.
2. Save it wherever you want.
3. Set your shell to '' (meaning CMD on Windows) and your shellArgs to ["/C", "path\\to\\your\\hyperstart.bat"]
4. Additional steps

• To enable the "launch elevated" line, Hyper needs to be on the PATH.

Customize

Add a shell

1. Add another ECHO line with a new number: ECHO [4] Python
2. Add the corresponding number to the CHOICE line: CHOICE /N /C:1234
3. Add the corresponding IF ERRORLEVEL line below the CLS line: IF ERRORLEVEL ==4 python
4. Fix up the other numbers, if necessary.

If you're having the resize error mentioned above, make sure the file hyperstart.bat is a windows batch file and not a text document. You may have it as a text if you saved it directly from the page. It worked for me once it's a batch file.

Nice job!

Awesome Job!
I had the same issue as seen by @ammein above.
I did not want to add the ms-git's version of bash in my PATH, as I would soon setup WSL, and I want that application's bash to be in PATH.

So, if like me, you have multiple bashes :-), you can do the following:

@ECHO off
:top
CLS
ECHO Choose a shell:
ECHO [1] cmd
ECHO [2] bash
ECHO [3] PowerShell
ECHO [4] Python
ECHO.
ECHO [5] restart elevated
ECHO [6] exit
ECHO.

CHOICE /N /C:123456 /M "> "
CLS
IF ERRORLEVEL ==6 GOTO end
IF ERRORLEVEL ==5 powershell -Command "Start-Process hyper -Verb RunAs"
IF ERRORLEVEL ==4 python
IF ERRORLEVEL ==3 powershell
IF ERRORLEVEL ==2 "C:\Program Files\Git\bin\bash.exe"
IF ERRORLEVEL ==1 cmd

CLS
ECHO Switch or exit?
ECHO [1] Switch
ECHO [2] Exit

CHOICE /N /C:12 /D 2 /T 5 /M "> "
IF ERRORLEVEL ==2 GOTO end
IF ERRORLEVEL ==1 GOTO top

:end

In other words, you can give full path to the bash.exe you want to execute.
Once I install WSL, I will extend this script, to include 2 bash options, each pointing to their respective exes.

Batch file no longer runs (resolved)
After a recent update (I'm now on 3.0.0 stable), my version of this batch files no longer runs from shellArgs, or any other configs when starting Hyper. It looks like the .hyper.js config file is now located in the Windows roaming AppData folder for Hyper (%USERPROFILE%\AppData\Roaming\Hyper). Once I moved my config and batch file there, it works as expected.

I'm just amazed that this one dinky little script that I put together in half an hour or so has gotten more response than any of my other projects that I've put considerably more time into.
Y'all make me smile.

I'm just amazed that this one dinky little script that I put together in half an hour or so has gotten more response than any of my other projects that I've put considerably more time into.
Y'all make me smile.

I say thank you.

I am having a problem where I can't close any tabs or panes though, and even closing the whole window ends up with a crash. Opening new tabs and selecting the shell works fine. Have you encountered anyone with this issue too?

May I ask what the .ps1 file is for? There's no mention of what it is intended for? I have just been using the .bat file for now.

@lopugit - the ps1 file is a PowerShell script file that's essentially equivalent to the .bat file. As for the other problem? I have no clue. I actually haven't used Hyper in ages - I've been using Windows Terminal.

@lopugit - the ps1 file is a PowerShell script file that's essentially equivalent to the .bat file. As for the other problem? I have no clue. I actually haven't used Hyper in ages - I've been using Windows Terminal.

I've just looked into windows terminal, but it seems they're having issues implementing traditional basic window transparency like hyper has.

May I ask how you implement the ps1 script? I couldn't just substitute it in place of the .bat file as the runtime argument

@lopugit

I've just looked into windows terminal, but it seems they're having issues implementing traditional basic window transparency like hyper has.

Fair enough. You don't like the acrylic, then?

May I ask how you implement the ps1 script? I couldn't just substitute it in place of the .bat file as the runtime argument

Set shell to whatever PowerShell executable you want to use, either powershell for 5.x or pwsh for 6.x+. Set shellArgs to ["path\\to\\hyperstart.ps1"]