-
Notifications
You must be signed in to change notification settings - Fork 37
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
Handle UNC paths #6
Comments
Check details from users here: http://danspowershellstuff.blogspot.com/2012/03/powershell-pretty-printer-code-cleaner.html |
I have worked around this issue by wrapping it in a function that moves it local then runs Edit-DTWBeautifyScript I am also using this function found here
|
Hey @justusiv Sorry I haven't looked into this one yet; I've been crazy busy. Hoping things quiet down for me in a few weeks and I'll have time to work on this. In the meantime, have you tried VS Code with the PowerShell extension yet? I used to use ISE with ISESteroids (a great plug-in) but after trying VS Code I'm hooked. You do have to spend a some time learning how it works; basic editing and such is obvious but there are many hidden gems that you have to search for - my favorite is Show References Shift-F12. It's worth reading a few blogs about editing & debugging PowerShell in VS Code, you will definitely learn some new tricks. Also, VS Code gets a new release once a month or so - so it's constantly being updated with new functionality. There is one giant drawback; code folding doesn't currently work for regions, etc. They are working on this (see project Microsoft/vscode issues 3422) so perhaps the next release or two will fix it. |
@DTW-DanWard |
@justusiv No problem. When I get time I can look into it; copying to local temp is straight-forward but I also want to check out the System.IO library a little more closely to make sure there isn't anything I'm missing that I could be doing. |
@DTW-DanWard Absolutely. Its a work-around for sure but i am happy with it :) |
See original issue record on blog; not sure of exact issue.
The text was updated successfully, but these errors were encountered: