Details
The Edit-Profile command appears to have been removed in the latest version of the PowerShell profile.
In previous versions, this command was part of the documented customization workflow and was used to create/edit a separate user profile.ps1 for overrides and enhancements without modifying upstream project files.
Previous implementation:
# Quick Access to Editing the Profile
function Edit-Profile {
vim $PROFILE.CurrentUserAllHosts
}
Set-Alias -Name ep -Value Edit-Profile
The older profile also explicitly documented this workflow:
“USE THE Edit-Profile FUNCTION TO CREATE YOUR OWN profile.ps1 FILE.”
This worked well alongside the existing _Override architecture (*_Override variables/functions) and made it easy to maintain customizations separately from the main profile.
After updating, running:
now returns:
Edit-Profile: The term 'Edit-Profile' is not recognized as a name of a cmdlet, function, script file, or executable program.
It would be great if this helper could be restored, even as a lightweight optional function/alias, since it was part of the previously documented extension workflow.
Benefits:
- Easier user customization
- Cleaner separation of upstream vs user changes
- Safer updates
- Better discoverability for the override system
- Restores compatibility with previous documented behavior
Thanks for all the work on the project.
Details
The
Edit-Profilecommand appears to have been removed in the latest version of the PowerShell profile.In previous versions, this command was part of the documented customization workflow and was used to create/edit a separate user
profile.ps1for overrides and enhancements without modifying upstream project files.Previous implementation:
The older profile also explicitly documented this workflow:
This worked well alongside the existing
_Overridearchitecture (*_Overridevariables/functions) and made it easy to maintain customizations separately from the main profile.After updating, running:
Edit-Profilenow returns:
It would be great if this helper could be restored, even as a lightweight optional function/alias, since it was part of the previously documented extension workflow.
Benefits:
Thanks for all the work on the project.