This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn More
Automating the world one-liner at a time…
December 28, 2006Dec 28, 200612/28/06$hay has a new scripting blog at http://scriptolog.blogspot.com/ . His first blog entry Restart your engine – The PowerShell Way, talks about how he frequently edits his PowerShell profile file and then restarts his session. In his directions he says:
2: type: Notepad $profile to open your profile file
I looked at this and thought about my Philosophy of Automation post and thought,
October 11, 2006Oct 11, 200610/11/06Well folks, at long last, my book is almost done 🙂
Before it goes out for print, you can get electronic copies through Manning’s early access program:
http://www.manning.com/payette/
The early access program is a chance for readers to provide feedback on a book so the author can fix things.
July 21, 2006Jul 21, 200607/21/06jmanning wrote:
Also, given how common the request is, I’d ask Jeffrey to (pretty-please) also include in this post a prompt function that sets the title to include pwd.
Ask and yea shall receive:
function Prompt{ $host.ui.RawUI.WindowTitle = $(get-location) “PS> “}
If you want to see a bunch of great prompt examples,
July 15, 2006Jul 15, 200607/15/06In my blog entry regarding Cascading Type Casts ( http://blogs.msdn.com/powershell/archive/2006/07/15/Cascading_Type_Casts.aspx ) there was an example:
PS> [string][char[]][int[]][char[]]”PowerShell” P o w e r S h e l l
And in a comment was a question asking why there were spaces between the letters.
July 1, 2006Jul 1, 200607/1/06<Edited 7/2/2006 to add tags and Categories>
Ben Winzenz didn’t like the fact that Windows PowerShell did not maintain history lists between sessions (http://winzenz.blogspot.com/2006/06/cool-mshpowershell-tidbit.html) . We hear you Ben. Back to my least favorite phrase, “to ship is to choose”. That said,
June 23, 2006Jun 23, 200606/23/06Over the course of time, I’ve written a number of functions & cmdlets and then created aliases for those. Many of those where Ad Hoc and I’ve since thrown them away but I still have the aliases sticking around. Here is a quick and easy way to determine the validity of your aliases
gal |%{if (!(gcm $_.Definition -ea SilentlyContinue)) {$_}}
Enjoy!Jeffrey SnoverWindows PowerShell Architect
PSMDTAG:ENVIRONMENT: cleaning up Aliases
