ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Powershell​Utils

by SublimeText ST2

Run powershell commands from within Sublime Text.

Details

  • 2011.04.25.10.31.18
  • github.​com
  • github.​com
  • 7 years ago
  • 38 minutes ago
  • 7 years ago

Installs

  • Total 5K
  • Win 4K
  • OS X 369
  • Linux 132
Aug 18 Aug 17 Aug 16 Aug 15 Aug 14 Aug 13 Aug 12 Aug 11 Aug 10 Aug 9 Aug 8 Aug 7 Aug 6 Aug 5 Aug 4 Aug 3 Aug 2 Aug 1 Jul 31 Jul 30 Jul 29 Jul 28 Jul 27 Jul 26 Jul 25 Jul 24 Jul 23 Jul 22 Jul 21 Jul 20 Jul 19 Jul 18 Jul 17 Jul 16 Jul 15 Jul 14 Jul 13 Jul 12 Jul 11 Jul 10 Jul 9 Jul 8 Jul 7 Jul 6 Jul 5
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
OS X 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

PowershellUtils package for Sublime Text

This plugin provides an interface to filter buffer text through a Windows Powershell pipeline and run and capture Powershell commands.

Requirements

Windows Powershell v2

Windows Powershell v2 is preinstalled in Windows 7 and later and it's available for previous versions of Windows too under the name Windows Management Framework.

Powershell is a powerful languange and needs to be used carefully to avoid undesired effects.

Getting Started

If you're running a full installation, simply double click on the .sublime-package files. If you're running a portable installation, perform an installation by hand.

Lastly, run run_powershell from the Python console or bind this command to a key combination:

# In Sublime's Python console.
view.run_command("sublime_cmd")

Using The Windows Powershell Pipeline

  1. Execute run_powershell
  2. Type in your Windows Powershell command
  3. Press enter

All the currently selected regions in Sublime Text will be piped into your command sequencially. In turn, you can access each of this regions through the $_ automatic variable.

Roughly, this is what goes on behind the scenes:

reg1..regN | <your command> | out-string

You can ignore the piped content and treat your command as the start point of the pipeline.

The generated output will be inserted into each region in turn.

Using Intrinsic Commands

(Not all intrinsic commands work.)

The following commands have a special meaning for this plugin:

!mkh
Saves the session's history of commands to a file.
!h
Brings up the history of commands so you can choose one and run it again.

Examples

$_.toupper()
Turns each region's content to all caps.
$_ -replace "\\","/"
Replaces each region's content as indicated.
"$(date)"
Replaces each region's content with the current date.
"$pwd"
Replaces each region's content with the current working directory.
[environment]::GetFolderPath([environment+specialfolder]::MyDocuments)
Replaces each region's content with the path to the user's My Documents folder.
0..6|%{ "$($_+1) $([dayofweek]$_)" }
Replaces each region's content with the enumerated week days.

Caveats

To start a Windows Powershell shell, do either Start-Process powershell or cmd /k start powershell, but don't call Windows Powershell directly because it will be launched in windowless mode and will block Sublime Text forever. Should this happen to you, you can execute the following command from an actual Windows Powershell prompt to terminate all Windows Powershell processes except for the current session:

Get-Process powershell | Where-Object { $_.Id -ne $PID } | Stop-Process

Alternatively, you can use a shorter version:

gps powershell|?{$_.id -ne $pid}|kill

Other Ways of Using PowershellUtils

PowershellUtils can be called with arguments so that the prompt is bypassed. This is interesting if you want to integrate powershell with a separate plugin.