The PowerShell Guy

Welcome to my New Blog "The PowerShell Guy" With ( I hope and think ) : A Better Name and address ( http://ThePowerShellGuy.com

hiya, Jacques

thanks for the reaction

the Tabexpansion should work in the first session as the setupscripts loads it also.

so it is not expected

about the documentation

I wan't to make a page on my blog with usage information and examples.

I added the exmaples to the setup,as a first primer to get users started, but there is some information still missing and as you mentioned its not so easy to read this way.

as I do not much time yet, hope it still helps a bit to get started with the tabcompletion.

Greetings /\/\o\/\/

As I allready mentioned in my welcome post Welcome to The PowerShell Guy blog , I made a new version

This is part 3 of a series, about PowerTab an extended PowerShell TabExpansion Function for more information

PingBack from http://www.leadfollowmove.com/?p=6

I updated the PowerTab, PowerShell TabExpansion function and library, the new version is PowerTab 0.8

Hiya Alexander,

I did supply a way to do the latter by using % at the end :

ne%[tab]

New-Alias

I can do this without the % but that would be awkward for directory completion hence this solution.

about the first remark :

also you can make the completion for applications but you will get to much see :

Get-Command pi*

that is the reason I did not add applications to the tabcompletion,

but you can add it very simple by replacing this line :

Get-Command -commandType Function,Filter, Cmdlet -Name "$($matches[1])*" |% {$_.Name}

by

Get-Command -commandType Function,Filter, Cmdlet,application -Name "$($matches[1])*" |% {$_.Name}

you could also use a different completion char for this e.g. !

h.t.h.

thanks for the comment

Greetings /\/\o\/\/

This is the Second entry, of a series of posts indexing the PowerShell Blogitems on my Old Blog /\/\o\/\/

Hi SQL guru,

yes, you can do that reason that I do not use this is that I have no PowerShell scripts in my path anyway ;-)

actualy I did add completion for scripts and external commands to my current version (not posted yet) only I application and added a ! behind it, this also get external scripts,

to get not to much false positives, expanding to Command name when I need a dir expansion.

Also I filtered out DLL's and stuff.

Greetings /\/\o\/\/

@ Alex and SQL guru,

It's implemented in current version 0.9

Greetings /\/\o\/\/

And another version of the PowerShell tabExpansion script library PowerTab is released, with some really

Adam,

See the last tip in the blogentry about it :

http://thepowershellguy.com/blogs/posh/archive/2007/04/22/powershell-tabextension-part-7-powertab-0-91-released.aspx

Add-PSSnapin lerchsnapin

$TabExpansionDoubleTabLock = $false

$TabExpansionAlternateHandler = 'intellisense'

$TabExpansionDoubleTabEnabled = $true

the DoubleTabLock = $false is needed as it's on default to enable alias completion on singleTab

DoubleTabEnabled = $true is needed as doubleTab support is Off now by Default to improve performance

try $[tab]tab to see what config parameters are available.

Enjoy,

Greetings /\/\o\/\/

As a developer one of the features that I used daily was to drag files from Windows Explorer onto a command

Hiya, Serge.

This is correct, there is a bug in the installer, when it creates a new directory it outputs the raw Object

I will release 0.92 this week that will add amonst others Tabcompletion on Function and Script parameters and also solves this bug,

you can fix this in current version by changing the following line :

 New-Item -type directory -path $ProfileDir -confirm

to :

 New-Item -type directory -path $ProfileDir -confirm | FL

did not spot this bug before as I added extra information to the installer and it only happens when the profile directory is not there yet.

Thanks for the input.

Greetings /\/\o\/\/

The 0.92 Update is there, problem with nex directory is fixed, also cleaned up rest of installer a bit

Greetings /\/\o\/\/

Juneb,

You can just run the setup again,

only need to clean old profile information.

never tested the current version against B2

Greetings /\/\o\/\/

Around TabExpansion.ps1:323, I modified the line that sends parameter names for tab expansion so that it only shows parameters that match the starting characters typed before <TAB>ing.  I invite you to include this fix in the next version.

# BEGIN ALA ENHANCEMENT

$patNoWildcard = $pat.substring(0,$pat.length-1)

get-ScriptParameters $path |? { $_.StartsWith(($patNoWildcard)) } |% {"-$_"}

# END ALA ENHANCEMENT

MOW, our company likes to place as much as possible into a Read Only store that is globaly replicated so that we can easily provide people with updates and control elements of the configuration.

Do you see any immediate issues with taking the complete PowerTab (post install) configuration and placing it into a Read Only location and simply updating the local profile to use the Read Only copy?

Thanks for your hard work and passion.

I gave it a go and with some minor changes to the "hard coded paths" it works as expected and we now have PowerTab running from a read only repository by taking the lines from the profile, adding them to a specific PS1 file on the network and dot sourcing that from our personal profiles.

For anyone interested

1. Expand powertab into a new folder

2. Execute the installer, all of it.

3. Copy the whole install folder to your network share

3. Copy the TabExpansion.xml file from you $profile folder to the network share

4. Edit TabExpansionLib.ps1

comment out the Export-tabExpansionDataBase Function and Edit the Import-TabExpansionDataBase Function to use your new path to the TabExpansion.xml file.

5. Move the additional lines created by the installer in your $profile to a new ps1 file in the new share, for example powertab_profile.ps1

6. Add a line to your $profile like . /<newsharepath>/powertab_profile.ps1.

7. Restart PowerShell and see MOW's PowerTab welcome.

The only real drawback will be that the TabExpansion.xml file is specific to the host it was created on. You could add come logic to Import-TabExpansionDataBase to look in the profile folder for the TabExpansion.xml first and then load it if it find it. This would allow people to execute the PowerTabSetup.ps1 themselves to get a host specific XML and then edit their $profile to remove the added lines leaving just the network loadable portion.

Just a though.

PowerTab 0.96 Beta 3b is released,( PowerTab.Zip Download )if you are already at 0.96 nothing much has

Hiya, AJ

Thanks for the comment,

Powertab does add a lot of functionality t o the standard tabexpansion function of Powershell, like

[math]:: completion on static members

[system. completion on .NET types

completion possibilities ar show in a list.

and much much more

on this overview page you can find a lot of links to former blogentries with examples and explaining the added functionality

Problem with the PowerTab script library is that it did grow massive over a year, so added functionality is massive and the information about is a bit scattered over the blog the updates are described per version.

with the links on this page is a short description what is mentioned in each entry

it started with the addition of static members : http://mow001.blogspot.com/2006/05/powershell-tab-completion.html

for a good example of the there are also links to 3 flash movies for example :

http://thepowershellguy.com/blogs/posh/archive/2007/06/02/powertab-flash-exampes.aspx

I also started working on a quick sheet, but not enough time to finish yet.

h.t.h

enjoy,

Greetings /\/\o\/\/

PingBack from http://www.aaronlerch.com/blog/2007/03/06/powertab-powershell-intellisense/

PingBack from http://mpitalianblog.wordpress.com/2007/08/27/powershell/

First off, thanks for your brilliant work.

I was wondering though, why you don't sign your scripts.  I run Powershell under the "AllSigned" execution policy.  This means that to upgrade PowerTab I have to sign all of the .PS1 scripts.  Not a big price to pay for the functionality, but I would love to just be able to *Trust* your signature.

Perhaps I know enough about PoSh security to be careful but am missing the reason you don't sign your scripts.  I just thought that it couldn't hurt to ask.  

Matt,

The scripts are not signed, but unblocked and with executionpolicy remotesigned it should work OK.

note, that when you unblock files you sometimes need to start a new shell.(install should do this allready)

Jason,

I did not sign the scripts, as I'm not sure how much value a selfsigned signature would really add, Not much people run allSigned and the ones that do mostly know adn want to check the scipt and sign thereself anyway I figured, and ofcourse I'm lazy myself also ;-)

Greetings Marc

Powertab 0.98 is released ( Download it from the PowerTab Overview Page ) I have recieved some bug reports

Sekhmet :

here the autocomplete works, also when using a \ to complte the path will expand the path automaticly again

e.g.

c:\[tab]pr\

Greetings /\/\o\/\/

Links of the week #3 (week 37/07)

I hate to talk about another guy's tool, but...

Windows PowerShell ist eine offene Plattform, um das Leben der IT Pros im Bereich Systems Management

Thanks, this is going to really make it easier to switch to PowerShell.

I didn't see any other posts on this; I hope I'm not covering old ground.

When the list is visible and I type an invalid character (something that isn't in the list) I get a hard beep (not through windows - it doesn't obey the windows mute).

Is this caused by powerTab? I didn't notice it before. Is there any way to get rid of it?

Thanks for any help you can provide,

Josh

Josh,

Yes the beep is triggered by powertab,

you can configure it with this setting :

[PoSH]> $PowerTabConfig.CloseListOnEmptyFilter

True

to stop beeps in common, stop the beep service ;-) :

net stop beep

Greetings /\/\o\/\/

If you aren't using PowerShell you should be. If you are using PowerShell then you need to check out

PingBack from http://HuddledMasses.org/installing-a-clean-development-box/

Recently I received a mail from one of my colleagues with some links to PowerShell stuff. I just wanted

PingBack from http://www.devslife.com/?p=52

PingBack from http://www.devslife.com/?p=92

PingBack from http://www.devslife.com/?p=95

PingBack from http://www.chinhdo.com/20071216/finds-of-the-week-december-15-2007/

PingBack from http://www.foxdm.cn/?p=139

This one was very challenging and got me puzzling for way to deep into the night morning last Friday,

Did you realize that you can use Wildcards with our tab completion? At the very beginning of the project,

I have a busy time catch up with all info in the video and audio releases about PowerShell over the weekend,