Downloads:

559

Downloads of v 1.0.2:

244

Last Update:

14 May 2018

Package Maintainer(s):

Software Author(s):

  • Michael Chavinda

Tags:

admin powershell module bash with

posh-with (PowerShell Module)

This is not the latest version of posh-with (PowerShell Module) available.

1.0.2 | Updated: 14 May 2018

Downloads:

559

Downloads of v 1.0.2:

244

Maintainer(s):

Software Author(s):

  • Michael Chavinda

posh-with (PowerShell Module) 1.0.2

This is not the latest version of posh-with (PowerShell Module) available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install posh-with (PowerShell Module), run the following command from the command line or from PowerShell:

>

To upgrade posh-with (PowerShell Module), run the following command from the command line or from PowerShell:

>

To uninstall posh-with (PowerShell Module), run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade poshwith -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade poshwith -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure poshwith installed
  win_chocolatey:
    name: poshwith
    state: present
    version: 1.0.2
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'poshwith' do
  action    :install
  version  '1.0.2'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: poshwith,
    Version: 1.0.2,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller poshwith
{
   Name     = 'poshwith'
   Ensure   = 'Present'
   Version  = '1.0.2'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'poshwith':
  provider => 'chocolatey',
  ensure   => '1.0.2',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install poshwith version="1.0.2" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator gep13 on 15 May 2018.

Description

Program prefixing for continuous workflow using a single tool.

NOTE: This module requires a minimum of PowerShell v3.

NOTE: This is an automatically updated package. If you find it is out of date by more than a week, please contact the maintainer(s) and let them know the package is no longer updating correctly.


tools\.skipAutoUninstaller
 
tools\chocolateyBeforeModify.ps1
$ErrorActionPreference = 'Stop'

$moduleName = 'posh-with'      # this could be different from package name
Remove-Module -Name $moduleName -Force -ErrorAction SilentlyContinue
tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$moduleName = 'posh-with'  # this may be different from the package name and different case

if ($PSVersionTable.PSVersion.Major -lt 3) {
    throw "$moduleName module requires a minimum of PowerShell v3."
}

# module may already be installed outside of Chocolatey
Remove-Module -Name $moduleName -Force -ErrorAction SilentlyContinue

$sourcePath = Join-Path -Path $toolsDir -ChildPath "$modulename\*"
$destPath = Join-Path -Path $env:ProgramFiles -ChildPath "WindowsPowerShell\Modules\$moduleName"

if ($PSVersionTable.PSVersion.Major -ge 5) {
    $manifestFile = Join-Path -Path $toolsDir -ChildPath "$moduleName\$moduleName.psd1"
    $manifest = Test-ModuleManifest -Path $manifestFile -WarningAction Ignore -ErrorAction Stop
    $destPath = Join-Path -Path $destPath -ChildPath $manifest.Version.ToString()
}

Write-Verbose "Creating destination directory '$destPath' for module."
New-Item -Path $destPath -ItemType Directory -Force -ErrorAction SilentlyContinue | Out-Null

Write-Verbose "Moving '$moduleName' files from '$sourcePath' to '$destPath'."
Move-Item -Path $sourcePath -Destination $destPath -Force

if ($PSVersionTable.PSVersion.Major -lt 4) {
    $modulePaths = [Environment]::GetEnvironmentVariable('PSModulePath', 'Machine') -split ';'
    if ($modulePaths -notcontains $destPath) {
        Write-Verbose "Adding '$destPath' to PSModulePath."
        $newModulePath = @($destPath, $modulePaths) -join ';'

        [Environment]::SetEnvironmentVariable('PSModulePath', $newModulePath, 'Machine')
        $env:PSModulePath = $newModulePath
    }
}
tools\chocolateyUninstall.ps1
$ErrorActionPreference = 'Stop'

$moduleName = 'posh-with'
$sourcePath = Join-Path -Path $env:ProgramFiles -ChildPath "WindowsPowerShell\Modules\$moduleName"

Write-Verbose "Removing all version of '$moduleName' from '$sourcePath'."
Remove-Item -Path $sourcePath -Recurse -Force -ErrorAction SilentlyContinue

if ($PSVersionTable.PSVersion.Major -lt 4) {
    $modulePaths = [Environment]::GetEnvironmentVariable('PSModulePath', 'Machine') -split ';'

    Write-Verbose "Removing '$sourcePath' from PSModulePath."
    $newModulePath = $modulePaths | Where-Object { $_ -ne $sourcePath }

    [Environment]::SetEnvironmentVariable('PSModulePath', $newModulePath, 'Machine')
    $env:PSModulePath = $newModulePath
}
tools\LICENSE.txt
From: https://github.com/JanDeDobbeleer/posh-with/blob/master/LICENSE.txt

LICENSE

Copyright 2016 Michael Chavinda

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
tools\posh-with\appveyor.yml
 
tools\posh-with\LICENSE.txt
Copyright 2016 Michael Chavinda

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
tools\posh-with\posh-with.psd1
#
# Module manifest for module 'posh-with'
#
# Generated by: Jan
#
# Generated on: 24-Aug-16
#

@{

# Version number of this module.
ModuleVersion = '1.0.2'

# Script module or binary module file associated with this manifest.
RootModule = 'posh-with.psm1'

# ID used to uniquely identify this module
GUID = '52d68197-b642-4c8a-be08-16b92399f1f1'

# Company or vendor of this module
CompanyName = 'Unknown'

# Author of this module
Author = 'JanJoris'

# Copyright statement for this module
Copyright = '(c) 2016 JanJoris. All rights reserved.'

# Description of the functionality provided by this module
Description = 'A PowerShell port of the Bash with commandlet'

# Minimum version of the Windows PowerShell engine required by this module
PowerShellVersion = '3.0'

# List of all files packaged with this module
FileList = @()

# Cmdlets to export from this module
CmdletsToExport = @()

# Variables to export from this module
VariablesToExport = @()

# Aliases to export from this module
AliasesToExport = '*'

# Functions to export from this module
FunctionsToExport = @('Invoke-With', 'Write-WithPrompt')

# Private data to pass to the module specified in RootModule. This may also contain a PSData hashtable with additional module metadata used by PowerShell.
PrivateData = @{

    PSData = @{

        # Tags applied to this module. These help with module discovery in online galleries.
        Tags = @('git', 'with', 'repeat', 'bash', 'prompt')

        # A URL to the license for this module.
        LicenseUri = 'https://github.com/JanJoris/posh-with/blob/master/LICENSE'

        # A URL to the main website for this project.
        ProjectUri = 'https://github.com/JanJoris/posh-with'

    } # End of PSData hashtable

} # End of PrivateData hashtable

}

tools\posh-with\posh-with.psm1
function Remove-With()
{
    param(
        [string]
        $command
    )

    $splitted = $command -split ' '
    if (!($splitted.Length -eq 1))
    {
        $splitted = $splitted[0..($splitted.Length - 2)]
    }    
    return "$splitted"
}

function Start-With()
{
    param(
        [string]
        $command
    )

    while($true)
    {
        Write-Host  ''
        Write-WithPrompt -command $command
        $input = [Microsoft.PowerShell.PSConsoleReadLine]::ReadLine($host.Runspace, $ExecutionContext)
        
        if ($input.ToLower() -eq ':q')
        {
            return
        }
        elseif ($input.StartsWith(':'))
        {
            if ($input.Length -eq 1)
            {
                continue
            }
            Invoke-Expression "$($input.Substring(1))"
        }
        elseif ($input.StartsWith($command)) {
            # let the user know the command is duplicated
            Write-Host "Your expression starts with '$command'"
            Write-Host 'When using with, make sure to not duplicate the expression.'
            Write-Host "Continuing assuming you meant '$($input.Substring($command.Length).Trim())'"
            Invoke-Expression "$input"
        }
        elseif ($input.StartsWith('>'))
        {
            $addition = $input.Substring(1).Trim()
            if (!($addition -eq ''))
            {
                $command += " $($input.Substring(1).Trim())"
            }
        }
        elseif ($input.StartsWith('<'))
        {
            $command = Remove-With -command $command
        }
        else 
        {
            Invoke-Expression "$command $input"
        }
        
    }
}

function global:Write-WithPrompt()
{
    param(
        [string]
        $command
    )

    Write-ClassicPrompt -command $command
}

function Write-ClassicPrompt()
{
    param(
        [string]
        $command
    )
    
    Write-Host "PS $pwd " -NoNewline
    Write-Host "$($command.ToUpper())" -ForegroundColor Yellow -NoNewline
    Write-Host "> " -NoNewline    
}

function Invoke-With()
{
    $command = $args
    if (Test-Command -command $command[0])
    {
        Start-With -command ($command.Trim())
    }
    else
    {
        Write-Host "$($command[0]): command not found"
    }
}

function Test-Command()
{
    param(
        [string]
        $command
    )
    return [bool](Get-Command -Name $command -ErrorAction SilentlyContinue)
}

Set-Alias with Invoke-With

tools\posh-with\PSGetModuleInfo.xml
<Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04">
  <Obj RefId="0">
    <TN RefId="0">
      <T>Microsoft.PowerShell.Commands.PSRepositoryItemInfo</T>
      <T>System.Management.Automation.PSCustomObject</T>
      <T>System.Object</T>
    </TN>
    <MS>
      <S N="Name">posh-with</S>
      <Version N="Version">1.0.2</Version>
      <S N="Type">Module</S>
      <S N="Description">A PowerShell port of the Bash with commandlet</S>
      <S N="Author">JanJoris</S>
      <S N="CompanyName">janjoris</S>
      <S N="Copyright">(c) 2016 JanJoris. All rights reserved.</S>
      <DT N="PublishedDate">2016-08-25T06:13:34+01:00</DT>
      <Nil N="InstalledDate" />
      <Nil N="UpdatedDate" />
      <URI N="LicenseUri">https://github.com/JanJoris/posh-with/blob/master/LICENSE</URI>
      <URI N="ProjectUri">https://github.com/JanJoris/posh-with</URI>
      <Nil N="IconUri" />
      <Obj N="Tags" RefId="1">
        <TN RefId="1">
          <T>System.Object[]</T>
          <T>System.Array</T>
          <T>System.Object</T>
        </TN>
        <LST>
          <S>git</S>
          <S>with</S>
          <S>repeat</S>
          <S>bash</S>
          <S>prompt</S>
          <S>PSModule</S>
        </LST>
      </Obj>
      <Obj N="Includes" RefId="2">
        <TN RefId="2">
          <T>System.Collections.Hashtable</T>
          <T>System.Object</T>
        </TN>
        <DCT>
          <En>
            <S N="Key">Function</S>
            <Obj N="Value" RefId="3">
              <TNRef RefId="1" />
              <LST>
                <S>Invoke-With</S>
                <S>Write-WithPrompt</S>
              </LST>
            </Obj>
          </En>
          <En>
            <S N="Key">RoleCapability</S>
            <Obj N="Value" RefId="4">
              <TNRef RefId="1" />
              <LST />
            </Obj>
          </En>
          <En>
            <S N="Key">Command</S>
            <Obj N="Value" RefId="5">
              <TNRef RefId="1" />
              <LST>
                <S>Invoke-With</S>
                <S>Write-WithPrompt</S>
              </LST>
            </Obj>
          </En>
          <En>
            <S N="Key">DscResource</S>
            <Obj N="Value" RefId="6">
              <TNRef RefId="1" />
              <LST />
            </Obj>
          </En>
          <En>
            <S N="Key">Workflow</S>
            <Obj N="Value" RefId="7">
              <TNRef RefId="1" />
              <LST />
            </Obj>
          </En>
          <En>
            <S N="Key">Cmdlet</S>
            <Obj N="Value" RefId="8">
              <TNRef RefId="1" />
              <LST />
            </Obj>
          </En>
        </DCT>
      </Obj>
      <Nil N="PowerShellGetFormatVersion" />
      <Nil N="ReleaseNotes" />
      <Obj N="Dependencies" RefId="9">
        <TNRef RefId="1" />
        <LST />
      </Obj>
      <S N="RepositorySourceLocation">https://www.powershellgallery.com/api/v2/</S>
      <S N="Repository">PSGallery</S>
      <S N="PackageManagementProvider">NuGet</S>
      <Obj N="AdditionalMetadata" RefId="10">
        <TN RefId="3">
          <T>System.Management.Automation.PSCustomObject</T>
          <T>System.Object</T>
        </TN>
        <MS>
          <S N="copyright">(c) 2016 JanJoris. All rights reserved.</S>
          <S N="description">A PowerShell port of the Bash with commandlet</S>
          <S N="requireLicenseAcceptance">True</S>
          <S N="isLatestVersion">True</S>
          <S N="isAbsoluteLatestVersion">True</S>
          <S N="versionDownloadCount">672</S>
          <S N="downloadCount">683</S>
          <S N="packageSize">5311</S>
          <S N="published">25/08/2016 06:13:34 +01:00</S>
          <S N="created">25/08/2016 06:13:34 +01:00</S>
          <S N="tags">git with repeat bash prompt PSModule PSFunction_Invoke-With PSCommand_Invoke-With PSFunction_Write-WithPrompt PSCommand_Write-WithPrompt PSIncludes_Function</S>
          <S N="developmentDependency">False</S>
          <S N="updated">2018-05-14T08:12:39Z</S>
          <S N="NormalizedVersion">1.0.2</S>
          <S N="IsPrerelease">false</S>
          <S N="ItemType">Module</S>
          <S N="FileList">posh-with.nuspec|appveyor.yml|LICENSE.txt|posh-with.psd1|posh-with.psm1|README.md</S>
          <S N="GUID">52d68197-b642-4c8a-be08-16b92399f1f1</S>
          <S N="PowerShellVersion">3.0</S>
          <S N="CompanyName">Unknown</S>
        </MS>
      </Obj>
      <S N="InstalledLocation">C:\Users\Paul\AppData\Local\Temp\2c421c67-60d9-4a1b-a9ad-620e8f5f48d3\posh-with\1.0.2</S>
    </MS>
  </Obj>
</Objs>
tools\posh-with\README.md
# with

[![Build status](https://img.shields.io/appveyor/ci/janjoris/posh-with/master.svg)](https://ci.appveyor.com/project/JanJoris/posh-with)

Program prefixing for continuous workflow using a single tool.

### Installation

Use the PowerShell Gallery to install posh-with:

    Install-Module posh-with

### Usage

    with <program>

Starts an interactive shell with where every command is prefixed using `<program>`.

For example:

    PS> with git
    PS GIT> add .
    PS GIT> commit -a -m "Commited"
    PS GIT> push

And to repeat commands:

    PS> with gcc -o output input.c
    PS GCC -O -OUTPUT INPUT.C>
    <enter>
    Compiling...
    PS GCC -O -OUTPUT INPUT.C>

To execute a shell command proper prefix line with `:`.


    PS GIT> :ls

You can also drop and add different commands.

    PS GIT> > add
    PS GIT ADD> <some file>
    PS GIT ADD> <
    PS GIT>

To exit use `:q`.

Currently supports command history and limited completions.

### Theming

To override the current prompt, create your own implementation using this function template:

    function global:Write-WithPrompt()
    {
        param(
            [string]
            $command
        )

        // Your awesome prompt building logic goes here
    }
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community in verifying that this package's contents are trustworthy.

To verify the files using the project source:

1. Please go to the project source location (https://github.com/JanDeDobbeleer/posh-with) and download the source files;
2. Build the source to create the binary files to verify;
3. Use Get-FileHash -Path <FILE TO VERIFY> to get the file hash value from both the built file (from step 1 above) and the file from the package and compare them;

Alternatively you can download the module from the PowerShell Gallery ...

    Save-Module -Name posh-with -Path <PATH TO DOWNLOAD TO>

... and compare the files from the package against those in the installed module. Again use Get-FileHash -Path <FILE TO VERIFY> to retrieve those hash values.

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
posh-with (PowerShell Module) 1.0.2 244 Monday, May 14, 2018 Approved

This package has no dependencies.

Discussion for the posh-with (PowerShell Module) Package

Ground Rules:

  • This discussion is only about posh-with (PowerShell Module) and the posh-with (PowerShell Module) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or posh-with (PowerShell Module), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus