Skip to content

Mac OS X :: PowerShell Intellisense not invoking #371

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pcgeek86 opened this issue Dec 12, 2016 · 6 comments
Closed

Mac OS X :: PowerShell Intellisense not invoking #371

pcgeek86 opened this issue Dec 12, 2016 · 6 comments
Milestone

Comments

@pcgeek86
Copy link
Contributor

System Details

  • Operating system name and version: Mac OS X 10.11.6
  • VS Code version: 1.7.2
  • PowerShell extension version: 0.7.2
  • Output from $PSVersionTable:
Name                           Value
----                           -----
PSVersion                      6.0.0-alpha
PSEdition                      Core
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   3.0.0.0
GitCommitId                    v6.0.0-alpha.13
CLRVersion
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

PowerShell Intellisense not working for cmdlets, similar to #250. I simply receive a PowerShell code snippets auto-complete correctly, however.

  • I have the latest PowerShell Alpha installed (Alpha 13).
  • I already have Mac OS X Homebrew installed, and installed the OpenSSL package, per the VSCode PowerShell directions.
  • The logs folder never gets created, despite following the directions to modify the User Settings file, to enable Verbose logging.

Attached Logs

I followed the instructions to enable verbose logging, but no logs are emitted.

@pcgeek86
Copy link
Contributor Author

screen shot 2016-12-12 at 2 19 16 pm

@daviwil
Copy link
Contributor

daviwil commented Dec 12, 2016

Those instructions were updated in anticipation of the 0.8.0 release on Wednesday, you'll need to follow an extra step for now:

sudo ln -s /opt/local/lib/libcrypto.1.0.0.dylib /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib
sudo ln -s /opt/local/lib/libssl.1.0.0.dylib /usr/local/opt/openssl/lib/libssl.1.0.0.dylib

Restart VS Code after running those two commands and you should be all set.

After Wednesday's update this will no longer be necessary. I'd release it today but we've got a couple more things to finish up.

@daviwil daviwil added this to the 0.8.0 milestone Dec 12, 2016
@pcgeek86
Copy link
Contributor Author

@daviwil Should those arguments be reversed? I just get "file exists," and the /opt/local directory doesn't exist.

@daviwil
Copy link
Contributor

daviwil commented Dec 12, 2016

Crap, sorry, I tried to copy/paste those on the fly but got the parameters wrong. Here's the correct lines:

mkdir /usr/local/lib
ln -s /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib /usr/local/lib/libcrypto.1.0.0.dylib
ln -s /usr/local/opt/openssl/lib/libssl.1.0.0.dylib /usr/local/lib/libssl.1.0.0.dylib

@pcgeek86
Copy link
Contributor Author

I can confirm that these steps work. Thank you @daviwil.

screen shot 2016-12-12 at 2 31 13 pm

@daviwil
Copy link
Contributor

daviwil commented Dec 12, 2016

Thanks for confirming!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants