Jumping around on my ramdisk got harder after a period of time, due to constantly changing and growing file system. There were a lot of pointless entries in the Jump-Location database, so I believe a kind of filtering would make sense.
I've added an -Exclude parameter, which defines the directories to be excluded. For example:
will exclude every node_modules, jspm_packages and their subfolders from the scan. Note that subfolders exclusion differs from the Get-ChildItem's -Exclude behavior.
I'm using currently the following command to scan (.NET and web development area):
PS:> jumpstat -Scan . -Exclude packages,node_modules,jspm_packages,testresults,`$tf,.vs,.git,bin,obj
Please note, that I've added this only in combination with -Scan. I prefer to decide on my own, when to save, so I turned off the autosave functionality in my profile.
Jumping around on my ramdisk got harder after a period of time, due to constantly changing and growing file system. There were a lot of pointless entries in the Jump-Location database, so I believe a kind of filtering would make sense.
I've added an -Exclude parameter, which defines the directories to be excluded. For example:
PS :\> jumpstat -Scan . -Exclude node_modules,jspm_packageswill exclude every node_modules, jspm_packages and their subfolders from the scan. Note that subfolders exclusion differs from the Get-ChildItem's -Exclude behavior.
I'm using currently the following command to scan (.NET and web development area): PS:> jumpstat -Scan . -Exclude packages,node_modules,jspm_packages,testresults,`$tf,.vs,.git,bin,obj
Please note, that I've added this only in combination with -Scan. I prefer to decide on my own, when to save, so I turned off the autosave functionality in my profile.
This enhancement partially solves #15.