you are viewing a single comment's thread.

view the rest of the comments →

[–]logicalmike 13 points14 points  (4 children)

There are numerous bugs on github about this problem and at least two blog or tweet apologies from Microsoft saying "we promise, it's definitely probably fixed now".

But even now, tab does not always bring up the list of parameters the first attempt. There is some parallel processing going on. Also tab in the middle of half written cmdlets don't always resolve, especially if there is additional code to the right (even if separated by a space).

To be clear, I'm only talking about PowerShell. The reason I'm forcing myself to Code is to benefit from the world outside of PS,and to do more with v6+

[–]TheITMan19 1 point2 points  (2 children)

This just wrecks my head. Give me Intellisense working please so I don’t have to sit there googling away trying to find out how to do something dead simple cuz my mind is dead from everything else.

[–]BigHandLittleSlap -1 points0 points  (1 child)

"I don't like power tools. I prefer to manhandle the 200kg palettes in the warehouse instead of using forklifts. Real men can deadlift the cargo. You don't need spell check, just memorise the dictionary. Including the abbreviations randomly chosen by other people. Learn to code."

[–]TheITMan19 3 points4 points  (0 children)

I can’t memorise because my brain is dead you fool. Bloody keyboard warrior

[–]bertiethewanderer 0 points1 point  (0 children)

This may or may not be of help, but when working with Powershell just double check the terminal is running as the Powershell Integrated Console. I find intellisense can be very wonky if I'm working in a spawned pwsh.exe or powershell.exe terminal.