terminal-spawn

Spawn the system terminal in the current file or project directory. Distinct from Pulsar's built-in terminal package: this one launches the OS terminal application as a separate process, not an embedded one.

Fork of open-terminal-here.

Features

• Spawn at file: Launch the terminal in the active file's directory or tree view selection.
• Spawn at project root: Launch the terminal in the project root directory.
• Configurable command: Customize the shell command used on each platform.
• Spawn with command: Launch the terminal with a command pre-executed inside it (via the provided service).
• Preset list: Pick from a list of per-platform terminal presets to populate the settings.

Installation

To install terminal-spawn search for terminal-spawn in the Install pane of the Pulsar settings or run ppm install terminal-spawn. Alternatively, you can run ppm install asiloisad/pulsar-terminal-spawn to install a package directly from the GitHub repository.

Commands

Commands available in atom-workspace:

• terminal-spawn:root: Alt+` spawn the terminal in the project root directory,
• terminal-spawn:open: spawn the terminal in the selected or active file's directory,
• terminal-spawn:list: open a list of terminal presets and apply the chosen one to the settings.

Configuration

Pick a row matching your terminal of choice. Use terminal-spawn:list to apply one directly, or copy the snippets into the two settings above. Defaults for each platform are marked (default).

Platform	Terminal	Command	Command with arguments
Windows	Command Prompt (default)	start /D "{cwd}" cmd	start /D "{cwd}" cmd /K "{command}"
Windows	Windows PowerShell	start powershell -NoExit -Command "Set-Location -LiteralPath '{cwd}'"	start powershell -NoExit -Command "Set-Location -LiteralPath '{cwd}'; {command}"
Windows	PowerShell 7	start pwsh -NoExit -Command "Set-Location -LiteralPath '{cwd}'"	start pwsh -NoExit -Command "Set-Location -LiteralPath '{cwd}'; {command}"
Windows	Windows Terminal (new window)	wt -d "{cwd}"	wt -d "{cwd}" cmd /K "{command}"
Windows	Windows Terminal (new tab)	wt -w 0 nt -d "{cwd}"	wt -w 0 nt -d "{cwd}" cmd /K "{command}"
macOS	Terminal.app (default)	open -a Terminal.app "{cwd}"	osascript -e 'tell app "Terminal" to do script "cd \"{cwd}\" && {command}"'
macOS	iTerm2	open -a iTerm "{cwd}"	osascript -e 'tell app "iTerm" to create window with default profile command "bash -c \"cd {cwd}; {command}; exec bash\""'
Linux	Default emulator (default)	x-terminal-emulator	x-terminal-emulator -e bash -c 'cd "{cwd}"; {command}; exec bash'
Linux	GNOME Terminal	gnome-terminal --tab --working-directory="{cwd}"	gnome-terminal --working-directory="{cwd}" -- bash -c '{command}; exec bash'
Linux	Konsole	konsole --new-tab --workdir "{cwd}"	konsole --workdir "{cwd}" -e bash -c '{command}; exec bash'
Linux	WezTerm	wezterm start --cwd "{cwd}"	wezterm start --cwd "{cwd}" -- bash -c '{command}; exec bash'
Linux	Kitty	kitty @ launch --type tab --cwd "{cwd}"	kitty @ launch --type tab --cwd "{cwd}" bash -c '{command}; exec bash'

Supports {cwd} and {command} placeholders.

Provided Service terminal-spawn

Allows other packages to spawn the configured terminal at a given path, optionally pre-executing a command inside it.

In your package.json:

{
  "consumedServices": {
    "terminal-spawn": {
      "versions": {
        "^1.0.0": "consumeTerminalSpawnService"
      }
    }
  }
}

In your main module:

module.exports = {
  consumeTerminalSpawnService(service) {
    service.open("/path/to/dir");
    service.open("/path/to/dir", "npm install");
  }
}

• open(dirpath, command?): spawns the user-configured terminal at dirpath. If command is provided, the terminal opens with that command pre-executed inside it (using the Terminal command with arguments template). If dirpath is falsy, falls back to the active project root. If dirpath points to a file, uses its parent directory.

Contributing

Got ideas to make this package better, found a bug, or want to help add new features? Just drop your thoughts on GitHub. Any feedback is welcome!