search

tkellogg / Jump-Location

Powershell `cd` that reads your mind
MIT License
467 stars 26 forks source link

CommandNotFoundException #62

Open MitjaBezensek opened 8 years ago

MitjaBezensek commented 8 years ago

I have been using Jump-Location for quite some time now. Today I suddenly started having a problem when opening a powershell window. I'm getting the following error:

Set-JumpLocation : The term 'Set-JumpLocation' is not recognized as the name of a cmdlet, function, script file, or operabl e program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At C:\Users\mitja.bezensek\Documents\WindowsPowerShell\Modules\Jump.Location\Load.ps1:36 char:2

  • Set-JumpLocation -Initialize
  • 
- CategoryInfo          : ObjectNotFound: (Set-JumpLocation:String) [], CommandNotFoundException
- FullyQualifiedErrorId : CommandNotFoundException

I've reinstalled Jump-Location but the error persists. Any clue what is going on?

Sleepmode commented 8 years ago

I have the same problem, have you come to a solution ? EDIT I downloaded the zip file, extracted all the files into the folder, then i rightclicked on every single file and opened the properties tab. on the bottom i had an option to allow or unblock the file. Now it works again

sjdeere commented 8 years ago

I just came accross this and have tried to give it a go ..but am getting the exact same thing. I succesfully
launch powershell as administrator (right click etc)

Set-ExecutionPolicy RemoteSigned and i installed PsGet

(new-object Net.WebClient).DownloadString("http://psget.net/GetPsGet.ps1") | iex

all successfully.

Install-Module Jump.Location Please reload your profile for the changes to take effect: C:\Users\username\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1

Module Jump.Location was successfully installed.

but when i type j my_websites it comes back with

j : The term 'Set-JumpLocation' is not recognized as the name of a cmdlet, function, script file, or operable program.

..well got this far down my essay and realise i really should close and re-open power shell reload your profile for the changes to take effect

it works now