Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

11,668

Downloads of v 3.0.3:

9,182

Last Update:

12 Apr 2015

Package Maintainer(s):

Software Author(s):

  • Steve Francia
  • Bram Moolenaar
  • Vim Community

Tags:

vim editor vi

spf13-vim

  • 1
  • 2
  • 3

3.0.3 | Updated: 12 Apr 2015

Downloads:

11,668

Downloads of v 3.0.3:

9,182

Maintainer(s):

Software Author(s):

  • Steve Francia
  • Bram Moolenaar
  • Vim Community

Tags:

vim editor vi

spf13-vim 3.0.3

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Unknown


Verification Testing Failed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install spf13-vim, run the following command from the command line or from PowerShell:

>

To upgrade spf13-vim, run the following command from the command line or from PowerShell:

>

To uninstall spf13-vim, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

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

1. Enter Your Internal Repository Url

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


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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://community.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. Copy Your Script

choco upgrade spf13-vim -y --source="'INTERNAL REPO 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 spf13-vim -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install spf13-vim
  win_chocolatey:
    name: spf13-vim
    version: '3.0.3'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'spf13-vim' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.0.3'
end

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


cChocoPackageInstaller spf13-vim
{
    Name     = "spf13-vim"
    Version  = "3.0.3"
    Source   = "INTERNAL REPO URL"
}

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


package { 'spf13-vim':
  ensure   => '3.0.3',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved by moderator alexinslc on 05 Dec 2015.

Description

spf13-vim: The Ultimate Vim Distribution. spf13-vim is a distribution of PURE AWESOMENESS in the form of vim plugins and resources for Vim, GVim and MacVim.
It is a completely cross platform distribution that stays true to the feel of vim while providing modern features like a plugin management system, autocomplete, tags and tons more. This install includes gVim 7.4 as part of the installation.


tools\chocolateyInstall.ps1
# Install script for spf13
$packageName = 'spf13-vim'
$validExitCodes = @(0,1) 

# Download and install spf13
try { 
  $scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
  $cmdPath = Join-Path $scriptPath 'spf13-vim-windows-install.ps1'

  Start-ChocolateyProcessAsAdmin $cmdPath -validExitCodes $validExitCodes
  Write-ChocolateySuccess "$packageName"
} catch {
  Write-ChocolateyFailure "$packageName" "$($_.Exception.Message)"
  throw
}
tools\chocolateyUninstall.ps1
# Uninstall for spf13-vim
$packageName = 'spf13-vim'
$installDir = Join-Path $HOME '.spf13-vim-3'

# Test whether path is a symlink, from http://stackoverflow.com/a/818054/
function Test-ReparsePoint([string]$path) {
  $file = Get-Item $path -Force -ea 0
  return [bool]($file.Attributes -band [IO.FileAttributes]::ReparsePoint)
}

function Test-SymLinkTargetsSpf13Directory([string]$Path)
{
    # PowerShell can't deal with symlinks. Call cmd.exe's dir, parse the output
    # and return true if there are any objects returned.
    # The regular expression checks if the symlink points to the .spf13-vim
    # directory in the user's directory, i.e. the symlink is from when the user
    # installed spf13-vim.
    # For example, a .vimrc symlink that still points to the .spf13-vim
    # directory looks like the following:
    # 10/04/2015  18:39    <SYMLINK>      .vimrc [C:\Users\john\.spf13-vim-3\.vimrc]
    return (cmd /c dir $Path `
                | Select-String -Pattern "\[$([regex]::Escape($HOME))\\\.spf13\-vim\-3.+\]$" `
                | Measure `
                | select -ExpandProperty Count) `
            -gt 0
}

function Remove-SymLink([string]$path)
{
    # If the symlink doesn't target the spf13-vim directory the user might have
    # repurposed it, so we shouldn't delete it.
    If ((Test-ReparsePoint $path) -and (Test-SymLinkTargetsSpf13Directory $path))
    {
        If (Test-Path -PathType Container $path)
        {
            # rmdir safely deletes the directory symlink, without deleting its
            # contents (http://superuser.com/a/306618/)
            Invoke-Expression "cmd /c rmdir $path"
        }
        Else
        {
            Invoke-Expression "cmd /c del $path"
        }
    }
}

try {
  Write-Host "Deleting symbolic links"
  # Delete the symbolic links
  Remove-Symlink "$HOME\.vimrc"
  Remove-Symlink "$HOME\_vimrc"
  Remove-Symlink "$HOME\.vimrc.fork"
  Remove-Symlink "$HOME\.vimrc.bundles"
  Remove-Symlink "$HOME\.vimrc.bundles.fork"
  Remove-Symlink "$HOME\.vimrc.before"
  Remove-Symlink "$HOME\.vimrc.before.fork"
  Remove-Symlink "$HOME\.vim"

  Remove-Item -Recurse -Force $installDir
  
  Write-ChocolateySuccess "$packageName"
} catch {
  Write-ChocolateyFailure "$packageName" "$($_.Exception.Message)"
  throw
}
tools\spf13-vim-windows-install.ps1
# spf13-vim Copyright 2014 Steve Francia
#
# 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.

# Check to see if we are running as admin
If (-NOT ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole(`
    [Security.Principal.WindowsBuiltInRole] "Administrator"))
{
    Write-Warning "You do not have Administrator rights to run this script!`nPlease re-run this script as an Administrator!"
    Break
}

# Script Functions
Function New-SymLink
{
    Param(
        [parameter(Mandatory=$true)]
        [String]
        $Link,

        [parameter(Mandatory=$true)]
        [String]
        $Target,

        [parameter(Mandatory=$false)]
        [ValidateSet("File", "Directory")]
        [String]
        $Type = "File"
    )

    # This function isn't compatible with pipeline input, so execute only once.
    # Defining only the End block is equivalent to not defining any of the
    # Begin, Process or End blocks.
    End
    {
        If ($Type -eq "File")
        {
            $command = "cmd /c mklink"
        }
        # Parameter was validated as either "File" or "Directory", so it's
        # definitely a Directory symlink.
        Else
        {

            $command = "cmd /c mklink /d"
        }

        Try 
        {
            $ErrorActionPreference = "Stop"
            invoke-expression "$command $link $target"
        } 
        Catch [System.Exception]
        {
            Write-Warning "Symbolic link '$link' already exists for '$target'"
        }
    }
}

Function Get-ApplicationPath ($appName, $errorMessage, $errorCode)
{
    Try 
    {
        $ErrorActionPreference = "Stop"
        $applicationPath = (Get-Command ($appName)).Path
        Write-Host "$appName installed in `"$applicationPath`"."
        Return $applicationPath
    } 
    Catch
    {
        Write-Error $errorMessage
        Exit $errorCode
    }
}


# Main Script Execution
$appDirectory = Join-Path $HOME ".spf13-vim-3"
$bundleDirectory = Join-Path $appDirectory ".vim/bundle"
$bundleLink = Join-Path $appDirectory ".vimrc.bundles"
$vundleDirectory = Join-Path $HOME ".vim/bundle/vundle"

Try {

    Write-Host "-= Installing spf13-vim =-"
    Write-Host "Checking for installation dependencies:"
    $gitCommand = Get-ApplicationPath "git" "Git not found! The git commandline must be installed before running this script" -1
    $curlCommand = Get-ApplicationPath "curl" "Curl not found! The curl commandline must be installed before running this script" -3
    $gvimCommand = Get-ApplicationPath "vim" "Gvim not found! The gvim 7.4 or greater must be installed before running this script" -2

    If (-Not (Test-Path $appDirectory))
    {
        Write-Host "The spf13 application directory '$appDirectory' was not found."
        Set-Location $HOME
        & $gitCommand clone --recursive -b 3.0 https://github.com/spf13/spf13-vim.git "$appDirectory"
    } 
    Else
    {
        Write-Host "The spf13 application directory '$appDirectory' was found."
        Set-Location $appDirectory
        Write-Host "Updating spf13-vim"
        & $gitCommand pull
        Set-Location $HOME
    }

    # Create the symbolic links
    New-SymLink "$HOME\.vimrc" "$appDirectory\.vimrc"
    New-SymLink "$HOME\_vimrc" "$appDirectory\.vimrc"
    New-SymLink "$HOME\.vimrc.fork" "$appDirectory\.vimrc.fork"
    New-SymLink "$HOME\.vimrc.bundles" "$appDirectory\.vimrc.bundles"
    New-SymLink "$HOME\.vimrc.bundles.fork" "$appDirectory\.vimrc.bundles.fork"
    New-SymLink "$HOME\.vimrc.before" "$appDirectory\.vimrc.before"
    New-SymLink "$HOME\.vimrc.before.fork" "$appDirectory\.vimrc.before.fork"
    New-SymLink "$HOME\.vim" "$appDirectory\.vim" "Directory"

    # Check to see If the bundle directory exists, if not, create it
    If (-Not (Test-Path $bundleDirectory))
    {
        Write-Host "Creating vim bundle directory: $bundelDirectory"
        New-Item -ItemType directory -Path $bundleDirectory
    }

    # Check for vundle
    If (-Not (Test-Path $vundleDirectory))
    {
        & $gitCommand clone https://github.com/gmarik/vundle.git "$vundleDirectory"
   
    } 
    Else
    {
        Set-Location $vundleDirectory
        & $gitCommand pull
        Set-Location $HOME
    }

    # Run vim and install the bundles
    Write-Host "Launching another process to finish installing the spf13-vim bundles..."
    Write-Host "HAVE PATIENCE: This could take a while!"
    Start-Process -FilePath $gvimCommand -ArgumentList "-u `"$bundleLink`" +BundleInstall! +BundleClean +qall"
}
Catch 
{
    Write-Warning "Could not install spf13-vim!"
    Write-Warning $_
} 

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.

Add to Builder Version Downloads Last Updated Status
spf13-vim 3.0.2 2486 Sunday, November 30, 2014 Approved

Several fixes thanks to John Fisher:
Added delete symlinks during uninstallation
Removed duplicate symlink creation
Fixed directory symlink creation
Added code to check that symlinks point to .spf13-vim before deleting

Discussion for the spf13-vim Package

Ground Rules:

  • This discussion is only about spf13-vim and the spf13-vim 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 spf13-vim, 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