8000 Completion for cmdlets / scripts doesn't work right after initial configuration · Issue #108 · jasonmarcher/PowerTab · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Completion for cmdlets / scripts doesn't work right after initial configuration #108

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.

Sign up for GitHub

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

Jump to bottom
Open
sba923 opened this issue Dec 1, 2019 · 1 comment
Open

Completion for cmdlets / scripts doesn't work right after initial configuration #108

sba923 opened this issue Dec 1, 2019 · 1 comment
8CE5

Comments

@sba923
Copy link
sba923 commented Dec 1, 2019

I'm discovering PowerTab after seeing it used here

When first imported (without arguments) a wizard is launched that creates initial configuration files.

After this wizard has run, and one imports the modules referencing those configuration files, basic tab completion for cmdlets and scripts on the PATH doesn't work anymore: one gets "[Err]" in the upper left corner instead.

Default configuration should "just work."

IMVHO

Attaching the aforementioned configuration files created by the wizard.

Initial PowerTab configuration files.zip
@thorstenkampe
Copy link

I think PowerTab stopped working (again) with current versions of PowerShell - use PS-GuiCompletion for the moment. Same issue here with PowerShell 7.0.0-rc.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thorstenkampe @sba923
0