about_Cd-Extras.help.txt
|
[
](https://coveralls.io/github/nickcox/cd-extras?branch=master) cd-extras =========== :zap: superpowers for the Powershell `cd` command, mostly stolen from bash and zsh :zap: <!-- TOC --> - [Navigation helpers](#navigation-helpers) - [Even faster](#even-faster) - [Navigation helper expansions](#navigation-helper-expansions) - [Viewing available locations](#viewing-available-locations) - [`cd` enhancements](#cd-enhancements) - [Path shortening](#path-shortening) - [Multi-dot `cd`](#multi-dot-cd) - [No argument `cd`](#no-argument-cd) - [Two argument `cd`](#two-argument-cd) - [Enhanced expansion for `cd` and others](#enhanced-expansion-for-cd-and-others) - [Multi-dot and variable based expansions](#multi-dot-and-variable-based-expansions) - [AUTO CD](#auto-cd) - [CD PATH](#cd-path) - [CDABLE VARS](#cdable-vars) - [Additional helpers](#additional-helpers) - [Compatibility](#compatibility) - [Alternative providers](#alternative-providers) - [OS X & Linux](#os-x--linux) - [Install](#install) - [Configure](#configure) - [cd-extras options](#cd-extras-options) - [Using a different alias](#using-a-different-alias) <!-- /TOC --> # Navigation helpers <details> <summary> [<i>Watch</i>] <p/> </summary> <p>  </p> </details> _cd-extras_ provides the following aliases (and corresponding functions): - `cd-`, `~`, (`Undo-Location`) - `cd+`, `~~`, (`Redo-Location`) - `up`, `..` (`Step-Up`) - `cdb` (`Step-Between`) ```sh [C:/Windows/System32]> up # or .. [C:/Windows]> cd- # or ~ [C:/Windows/System32]> cd+ [C:/Windows]> █ ``` Note that the aliases are `cd-` and `cd+`, without a space. `cd -` and `cd +` (with a space) also work but you won't get [tab expansions](#navigation-helper-expansions). Repeated uses of `cd-` keep moving backwards towards the beginning of the stack rather than toggling between the two most recent directories as in vanilla bash. Use `Step-Between` (`cdb`) if you want to toggle between directories. ```sh [C:/Windows/System32]> cd .. [C:/Windows]> cd .. [C:/]> cd- [C:/Windows]> cd- [C:/Windows/System32]> cd+ [C:/Windows]> cd+ [C:/]> cdb [C:/Windows]> cdb [C:/]> █ ``` ## Even faster `up`, `cd+` and `cd-` each take a single optional parameter: either a number of steps, `n`... ```sh [C:/Windows/System32]> .. 2 # or `up 2` [C:/]> cd temp [C:/temp]> cd- 2 # `cd -2`, `~ 2` or just `~2` also work [C:/Windows/System32]> cd+ 2 [C:/temp]> █ ``` ...or a string, `NamePart`, used to select the nearest matching directory from the available locations. Given a `NamePart`, _cd-extras_ will search from the current location for directories whose _leaf_ name contains the given string (ex. ¹). If none is found then it will attempt to find a match within the full path of each candidate directory (ex. ²). ```sh [C:/Windows]> cd system32 [C:/Windows/System32]> cd drivers [C:/Windows/System32/drivers]> cd- win # [ex. 1] by leaf name [C:/Windows/]> cd+ 32/dr # [ex. 2] by full name [C:/Windows/System32/drivers]> up win # by leaf name again [C:/Windows]> █ ``` ## Navigation helper expansions Tab completions are provided for each of `cd-` (_aka_ `~`), `cd+` (_aka_ `~~`) and `up` (_aka_ `..`). When the `MenuCompletion` option is set and more than one completion is available, the completions offered are the indexes of each corresponding directory; the name itself is displayed in the menu below. The full directory path is shown in the tooltip if you also have `PSReadLine` tooltips enabled. _cd-extras_ will attempt to detect `PSReadLine` options in order to set `MenuCompletion` appropriately at start-up. ```sh [C:/Windows/System32/drivers/etc]> up ⇥ [C:/Windows/System32/drivers/etc]> up 1 1. drivers 2. System32 3. Windows 4. C:\ ─────────── C:\Windows\System32\drivers ``` It's also possible tab-complete each of these commands (`cd-`, `cd+`, `up`) using a partial directory name (i.e. the [`NamePart` parameter](#even-faster)). ```sh [~/projects/PowerShell/src/Modules/Shared]> up pr⇥ [~/projects/PowerShell/src/Modules/Shared]> up '~\projects' [~/projects]> █ ``` ## Viewing available locations As an alternative to tab completion you can use: - `Get-Stack -Undo` (`dirs -u`), - `Get-Stack -Redo` (`dirs -r`) and - `Get-Ancestors` (`xup`) to quickly show a list of available navigation targets. ```sh [C:/Windows/System32/drivers]> Get-Ancestors # xup n Name Path - ---- ---- 1 System32 C:\Windows\System32 2 Windows C:\Windows 3 C:\ C:\ [C:/Windows/System32/drivers]> up 2 [C:/Windows]> up 1 [C:/]> dirs -u n Name Path - ---- ---- 1 Windows C:\Windows 2 drivers C:\Windows\System32\drivers ``` # `cd` enhancements <details> <summary> [<i>Watch</i>] <p/> </summary> <p>  </p> </details> `cd-extras` provides a proxy to `Set-Location`, called `Set-LocationEx` which is aliased to `cd` by default, giving it several new abilities: * Path shortening * Multi-dot `cd` * No argument `cd` * Two argument `cd` ## Path shortening If an unambiguous match is available then `cd` can change directory using an abbreviated path. This effectively changes a path given as, `p` into `p*` or `~/pr/pow/src` into `~/pr*/pow*/src*`. ```sh [~]> cd pr [~/projects]> cd cd-e [~/projects/cd-extras]> cd ~ [~]> cd pr/cd [~/projects/cd-extras]> █ ``` Periods (`.`) are expanded around so a segment containing `.sdk` is expanded into `*.sdk*`. ```sh [~]> cd proj/pow/s/.sdk [~/projects/powershell/src/Microsoft.PowerShell.SDK]> █ ``` Pairs of periods are expanded between so a segment containing `s..32` is expanded into `s*32`. ```sh [~]> cd /w/s..32/d/et [C:/Windows/System32/drivers/etc]> █ ``` Directories in [`CD_PATH`](#cd_path) will be matched. ```sh [C:/]> setocd CD_PATH ~/projects [C:/]> cd p..shell [~/projects/PowerShell/]> █ ``` [`AUTO_CD`](#auto_cd) uses the same expansion algorithm if enabled. ```sh [~]> /w/s/d/et [C:/Windows/System32/drivers/etc]> ~/pr/pow/src [~/projects/PowerShell/src]> .sdk [~/projects/PowerShell/src/Microsoft.PowerShell.SDK]> █ ``` If you're not sure whether an unambiguous match is available then just hit tab to pick from a [list of potential matches](#enhanced-expansion-for-cd-and-others) instead. ## Multi-dot `cd` In the same way that you can navigate up one level with `cd ..`, `Set-LocationEx` supports navigating multiple levels by adding additional dots. [`AUTO_CD`](#auto_cd) works the same way if enabled. ```sh [C:/Windows/System32/drivers/etc]> cd ... # same as `up 2` or `.. 2` [C:/Windows/System32]> cd- [C:/Windows/System32/drivers/etc>] cd .... # same as `up 3` or `.. 3` [C:/Windows]> █ ``` ## No argument `cd` If the `NOARG_CD` [option](#configure) is defined then `cd` without arguments navigates into that directory (`~` by default). This overrides the out of the box behaviour on PowerShell versions >= 6.0, where no-arg `cd` always navigates to `~`.) ```sh [~/projects/powershell]> cd [~]> setocd NOARG_CD / [~]> cd [C:/]> ``` ## Two argument `cd` Replaces all instances of the first argument in the current path with the second argument, changing to the resulting directory if it exists, using the `Switch-LocationPart` function. You can also use the alias `cd:` or the explicit `ReplaceWith` parameter of `Set-LocationEx`. ```sh [~/Modules/Unix/Microsoft.PowerShell.Utility]> cd unix shared [~/Modules/Shared/Microsoft.PowerShell.Utility]> cd: shared unix [~/Modules/Unix/Microsoft.PowerShell.Utility]> cd unix -ReplaceWith shared [~/Modules/Shared/Microsoft.PowerShell.Utility]> █ ``` ## Enhanced expansion for `cd` and others `cd`, `pushd` and `ls` (by default) provide enhanced tab completion, expanding all path segments so that you don't have to individually tab (⇥) through each one (using the path shortening logic [described above](#path-shortening).) ```sh [~]> cd /w/s/dr⇥⇥ [~]> cd C:/Windows/System32/DriverState/ drivers DriverState DriverStore ─────────── C:\Windows\System32\DriverState ``` Periods (`.`) are expanded around so, for example, a segment containing `.sdk` is expanded into `*.sdk*`. ```sh [~]> cd proj/pow/s/.sdk⇥ [~]> cd ~\projects\powershell\src\Microsoft.PowerShell.SDK\█ ``` or ```sh [~]> ls pr/pow/t/ins.sh⇥ [~]> ls ~\projects\powershell\tools\install-powershell.sh [~]> ls ~\projects\powershell\tools\install-powershell.sh | cat #!/bin/bash ... [~]> ``` A double-dot (`..`) token indicates a section which begins with the characters to its left and continues with the characters to the right. ```sh [~]> ls pr/pow/t/ins..psh.sh⇥ .\tools\installpsh-amazonlinux.sh .\tools\installpsh-osx.sh ───────────────────────────────── ``` You can change the list of commands that participate in enhanced directory completion using the `DirCompletions` [option](#configure): ```sh [~]> $cde.DirCompletions += 'mkdir' [~]> # setocd DirCompletions mkdir, $cde.DirCompletions [~]> mkdir ~/pow/src⇥ [~]> mkdir ~\powershell\src\█ ``` Similarly, you opt into enhanced completion for files only or for both files and directories using the `FileCompletions` and `PathCompletions` options respectively. Note that the `FileCompletions` option is less useful as you won't be able to tab through directories to get to the file you're looking for. ```sh [~]> $cde.PathCompletions += 'Invoke-Item' [~]> # or setocd PathCompletions $cde.PathCompletions, 'Invoke-Item' [~]> ii /t/⇥ [~]> ii C:\temp\subdir\█ subdir txtFile.txt txtFile2.txt ────── C:\temp\subdir ``` Paths within `$cde.CD_PATH` are included for all completion types. ```sh [~]> $cde.CD_PATH += '~\Documents\' [~]> cd win/mod⇥ [~]> ~\Documents\WindowsPowerShell\Modules\█ ``` In each case, expansions work against the target's `Path` parameter; if you want enhanced completion for a native executable or for a cmdlet without a `Path` parameter then you'll need to provide a wrapper. Either the wrapper or the target itself should handle expanding `~` where necessary. ```sh [~]> function Invoke-VSCode($path) { &code (Resolve-Path $path) } [~]> $cde.DirCompletions += 'Invoke-VSCode' [~]> Set-Alias co Invoke-VSCode [~]> co ~/pr/po⇥ [~]> co ~\projects\powershell\█ ``` An alternative to registering a bunch of aliases is to create a tiny wrapper to pipe input from `ls`. ```sh [~]> function to($target) { &$target $input } [~]> ls ~/pr/po/r.md⇥ [~]> ls ~/projects/powershell/readme.md | to bat ─────────────────────────────────────────────────────── File: C:\Users\Nick\projects\PowerShell\README.md ─────────────────────────────────────────────────────── 1 | ... 2 | ... ``` Expansions in the filesystem provider can be colourised via [DirColors][1] by setting the `ColorCompletion` option (`setocd ColorCompletion`). Alternatively, you can implement your own colourisation by creating a global `Format-ColorizedFilename` function. ## Multi-dot and variable based expansions The [multi-dot syntax](#multi-dot-cd) provides tab completion into ancestor directories. ```sh [~/projects/powershell/docs/git]> cd ...⇥ [~/projects/powershell/docs/git]> cd ~\projects\powershell\█ ``` ```sh [C:/projects/powershell/docs/git]> cd .../⇥ .git .vscode demos docs test ───── .github assets docker src tools ~\projects\powershell\.git ``` When used with the `-Export` option, `Get-Ancestors` (`xup`) recursively expands each parent directory's path into a global variable with a corresponding name. This can be useful in combination with [CDABLE_VARS](#cdable_vars) for navigating a deeply nested folder structure. ```sh [C:/projects/powershell/src/Modules/Unix]> xup -Export -ExcludeRoot n Name Path - ---- ---- 1 Unix C:\projects\powershell\src\Modules\Unix 2 Modules C:\projects\powershell\src\Modules 3 src C:\projects\powershell\src 4 powershell C:\projects\powershell 5 projects C:\projects [C:/projects/powershell/src/Modules/Unix]> cd po⇥ [C:/projects/powershell/src/Modules/Unix]> cd C:\projects\powershell\_ ``` might be easier than: ```sh [C:/projects/powershell/src/Modules/Unix]> cd ....⇥ # or cd ../../../⇥ [C:/projects/powershell/src/Modules/Unix]> cd C:\projects\powershell\█ ``` You can combine `CDABLE_VARS` with [AUTO_CD](#auto_cd) for great good: ```sh [C:/projects/powershell/src/Modules/Unix]> projects [C:/projects]> src [C:/projects/powershell/src]> █ ``` # AUTO CD <details> <summary> [<i>Watch</i>] <p/> </summary> <p>  </p> </details> Change directory without typing `cd`. ```sh [~]> projects [~/projects]> cd-extras [~/projects/cd-extras]> / [C:/]> █ ``` As with the [enhanced `cd`](#cd-enhancements) command, [abbreviated paths](#path-shortening) and multi-dot syntax are supported. ```sh [~]> pr [~/projects]> cd-e [~/projects/cd-extras]> cd [~]> pr/cd [~/projects/cd-extras]> █ ``` `AUTO_CD` also supports a shorthand syntax for `cd-` using tilde (`~`). You can use this with or without a space between tilde and the number, although [tab completion](#Enhanced-expansion-for-built-ins) only works after a space (`~ ⇥`). ```sh [C:/Windows/System32]> / [C:/]> temp [C:/temp]> dirs -u n Name Path - ---- ---- 0 temp C:\temp 1 C:\ C:\ 2 System32 C:\Windows\System32 [C:/temp]> ~2 # or ~ 2 [C:/Windows/System32]> ~~2 # or ~~ 2 [C:/temp]> █ ``` Multi-dot syntax also works with `AUTO_CD` as an alternative to `up [n]`. ```sh [C:/Windows/System32/drivers/etc]> ... # same as `up 2` or `.. 2` [C:/Windows/System32]> cd- [C:/Windows/System32/drivers/etc>] .... # same as `up 3` or `.. 3` [C:/Windows]> █ ``` # CD PATH Search additional locations for candidate directories. ```sh [~]> setocd CD_PATH ~/documents [~]> # or $cde.CD_PATH = @('~/documents')' [~]> cd WindowsPowerShell [~/documents/WindowsPowerShell]> █ ``` [Tab-expansion](#enhanced-expansion-for-built-ins) and [path shortening](#path-shortening) work with `CD_PATH` directories. Note that `CD_PATH`s are _not_ searched when an absolute or relative path is given. ```sh [~]> setocd CD_PATH '~/documents' [~]> cd ./WindowsPowerShell Set-Location : Cannot find path '~\WindowsPowerShell' because it does not exist. ``` # CDABLE VARS Save yourself a `$` when cding into folders using a variable name and enable [expansion](#multi-dot-and-variable-based-expansions) for child directories. Given a variable containing the path to a folder (configured in your `$PROFILE`, perhaps, or by invoking [`Get-Ancestors`](#multi-dot-and-variable-based-expansions)), you can `cd` into it using the name of the variable. ```sh [~]> $power = '~/projects/powershell' [~]> cd power [~/projects/powershell]> █ ``` This works with relative paths too, so if you find yourself frequently `cd`ing into the same subdirectories you could create a corresponding variable. ```sh [~/projects/powershell]> $gh = './.git/hooks' [~/projects/powershell]> cd gh [~/projects/powershell/.git/hooks]> █ ``` CDABLE_VARS is off by default. Enable it with, [`setocd CDABLE_VARS`](#configure). # Additional helpers - Get-Up (_gup_) - get the path of an ancestor directory, either by name or by `n` levels. - returns the parent of the current directory by default. - Clear-Stack (_dirsc_) - clear contents of undo (`cd-`) and/or redo (`cd+`) stacks. - Get-Stack (_dirs_) - view contents of undo (`cd-`) and redo (`cd+`) stacks. - use `dirs -u` for an indexed list of undo locations or `dirs -r` for a corresponding list of redo locations - Expand-Path (_xpa_) - expand a candidate path by inserting wildcards between each segment. - **note:** the expansion may match more than you expect. always test the output before piping it into a potentially destructive command. # Compatibility ## Alternative providers _cd-extras_ is primarily intended to work against the filesystem provider but things should work with other providers too. ```sh [~]> cd hklm:\ [HKLM:]> cd so/mic/win/cur/windowsupdate [HKLM:/SOFTWARE/Microsoft/Windows/CurrentVersion/WindowsUpdate]> .. [HKLM:/SOFTWARE/Microsoft/Windows/CurrentVersion]> cd- [HKLM:/SOFTWARE/Microsoft/Windows/CurrentVersion/WindowsUpdate]> cd- 2 [~]> █ ``` ## OS X & Linux Everything should work on non-Windows operating systems. Note that the `MenuCompletion` option may be off be default unless you configure PSReadLine with a `MenuComplete` keybinding _before_ importing `cd-extras`. ```sh Set-PSReadLineKeyHandler -Key Tab -Function MenuComplete ``` Otherwise you can enable `cd-extras` menu completions manually with: ```sh setocd MenuCompletion ``` # Install From the [gallery](https://www.powershellgallery.com/packages/cd-extras/) ```sh Install-Module cd-extras Import-Module cd-extras # add to profile. e.g: Add-Content $PROFILE `n, 'Import-Module cd-extras' ``` or from get the latest from github ```sh git clone git@github.com:nickcox/cd-extras.git Import-Module cd-extras/cd-extras/cd-extras.psd1 # yep, three :D ``` # Configure ## _cd-extras_ options - _AUTO_CD_: `[bool] = $true` - Any truthy value enables auto_cd. - _CD_PATH_: `[string[]] = @()` - Paths to be searched by `cd` and tab expansion. Note that this is an array, not a delimited string. - _CDABLE_VARS_: `[bool] = $false` - `cd` and tab-expand into directory paths stored in variables without prefixing the variable name with `$`. - _NOARG_CD_: `[string] = '~'` - If specified, `cd` command with no arguments will change to this directory. - _MenuCompletion_: `[bool] = $true` (if PSReadLine available) - If truthy, indexes are offered as completions for `up`, `cd+` and `cd-` with full paths displayed in the menu. - _DirCompletions_: `[string[]] = @('Push-Location', 'Set-Location', 'Set-LocationEx')` - Commands that participate in enhanced tab expansion for directories. - _PathCompletions_: `[string[]] = @('Get-ChildItem')` - Commands that participate in enhanced tab expansion for any type of path (files & directories). - _FileCompletions_: `[string[]] = @()` - Commands that participate in enhanced tab expansion for files. - _ColorCompletion_ : `[bool] = false` - If truthy, offered Dir/Path/File completions will be coloured by `Format-ColorizedFilename`, if available. - MaxMenuLength : `[int] = 60` - Truncate completion menu items to this length. Column layout may break below about 60 characters. - _MaxCompletions_ : `[int] = 99` - Limit the number of Dir/Path/File completions offered. Should probably be at least one less than `(Get-PSReadLineOption).CompletionQueryItems`. To configure _cd-extras_ create a hashtable, `cde`, with one or more of these keys _before_ importing it: ```sh $cde = @{ AUTO_CD = $false CD_PATH = @('~/Documents/', '~/Downloads') } Import-Module cd-extras ``` or call the `Set-CdExtrasOption` (`setocd`) function after importing the module: ```sh Import-Module cd-extras setocd CDABLE_VARS setocd AUTO_CD $false setocd NOARG_CD '/' ``` Note: if you want to opt out of the default [path completions](#Enhanced-expansion-for-built-ins) then you should do it before _cd-extras_ is loaded since PowerShell doesn't provide any way of unregistering argument completers. ```sh $cde = @{ DirCompletions = @() } Import-Module cd-extras ``` ## Using a different alias _cd-extras_ aliases `cd` to its proxy command, `Set-LocationEx`, by default. If you want to use a different alias then you'll probably want to restore the default `cd` alias at the same time. ```sh [~]> set-alias cd set-location -Option AllScope [~]> set-alias cde set-locationex [~]> cde /w/s/d/et [C:/Windows/System32/drivers/etc]> cd- # note: still cd-, not cde- [~]> █ ``` `cd-extras` will only remember locations visited via `Set-LocationEx` or its alias. [1]: https://github.com/DHowett/DirColors |