How do I set the Terminal (Layout Tab, Terminal check box) to run my installed and customized Powershell 7 environment? It is defaulting to v5.
Thanks
Thanks
The executable to run on opening the Terminal window is not customizable with a setting as far as I know.
I suggest reading the existing topics:
There is always started powershell.exe which is found first according to the environment variable PATH in the environment variables memory of UltraEdit. That is by Windows default powershell.exe in the directory: %SystemRoot%\System32\WindowsPowerShell\v1.0\
There could be modified the environment variable PATH used by UltraEdit to find a different powershell.exe.
For example, there is used by most UltraEdit users the shortcut file UltraEdit.lnk with the shortcut property Target being defined by default with "C:\Program Files\IDM Computer Solutions\UltraEdit\uedit64.exe". That string could be modified to:
%SystemRoot%\System32\cmd.exe /D /S /C "set "PATH=C:\Other PowerShell Directory;%PATH%" & "C:\Program Files\IDM Computer Solutions\UltraEdit\uedit64.exe""
The shortcut property Run should be changed to Minimized because of Windows File Explorer calls the Windows kernel function CreateProcess with a filled out structure STARTUPINFO instructing the kernel function to start cmd.exe with creation of a minimized console window displayed just for a short time. The Windows Command Processor is used in this case just to redefine the environment variable PATH in its own memory before UltraEdit is started with that modified PATH and cmd.exe closes itself while UltraEdit continues running as detached process.
Another solution would be running with the shortcut %SystemRoot%\System32\wscript.exe with a fully qualified VBScript file name and the Windows Script Host options //B //Nologo. That opens no console window on use of the shortcut file. The VBScript file requires a few lines to redefine the environment variable PATH in memory of this instance of Windows Script Host and next start uedit64.exe as detached process by calling also CreateProcess before wscript.exe terminates itself while UltraEdit runs with a PATH configured different than usually.
In the first specified PowerShell directory in PATH must be a file powershell.exe which could be also a hard link or a symbolic link to pse.exe.
Well, it would be also possible to replace in the system environment variable PATH the folder path %SystemRoot%\System32\WindowsPowerShell\v1.0\ by a different folder path containing powershell.exe (or a symbolic link or a hard link with that name linking to pse.exe) to always use PowerShell 7.x independent on which process runs powershell.exe like UltraEdit or just powershell without path.
set "PATH=C:\Other PowerShell Directory;%PATH%" could be also set "PATH=%PATH:C:\Windows\System32\WindowsPowerShell\v1.0\=C:\Other PowerShell Directory%" to replace the default PowerShell path by a different one just for PATH used by UltraEdit (and all processes started by UltraEdit).
There can be of course also send a feature request email to UltraEdit support for requesting a configuration to define the PowerShell executable used on opening the Terminal window or running a *.ps1 file which is edited in UltraEdit.
I suggest reading the existing topics:
There is always started powershell.exe which is found first according to the environment variable PATH in the environment variables memory of UltraEdit. That is by Windows default powershell.exe in the directory: %SystemRoot%\System32\WindowsPowerShell\v1.0\
There could be modified the environment variable PATH used by UltraEdit to find a different powershell.exe.
For example, there is used by most UltraEdit users the shortcut file UltraEdit.lnk with the shortcut property Target being defined by default with "C:\Program Files\IDM Computer Solutions\UltraEdit\uedit64.exe". That string could be modified to:
%SystemRoot%\System32\cmd.exe /D /S /C "set "PATH=C:\Other PowerShell Directory;%PATH%" & "C:\Program Files\IDM Computer Solutions\UltraEdit\uedit64.exe""
The shortcut property Run should be changed to Minimized because of Windows File Explorer calls the Windows kernel function CreateProcess with a filled out structure STARTUPINFO instructing the kernel function to start cmd.exe with creation of a minimized console window displayed just for a short time. The Windows Command Processor is used in this case just to redefine the environment variable PATH in its own memory before UltraEdit is started with that modified PATH and cmd.exe closes itself while UltraEdit continues running as detached process.
Another solution would be running with the shortcut %SystemRoot%\System32\wscript.exe with a fully qualified VBScript file name and the Windows Script Host options //B //Nologo. That opens no console window on use of the shortcut file. The VBScript file requires a few lines to redefine the environment variable PATH in memory of this instance of Windows Script Host and next start uedit64.exe as detached process by calling also CreateProcess before wscript.exe terminates itself while UltraEdit runs with a PATH configured different than usually.
In the first specified PowerShell directory in PATH must be a file powershell.exe which could be also a hard link or a symbolic link to pse.exe.
Well, it would be also possible to replace in the system environment variable PATH the folder path %SystemRoot%\System32\WindowsPowerShell\v1.0\ by a different folder path containing powershell.exe (or a symbolic link or a hard link with that name linking to pse.exe) to always use PowerShell 7.x independent on which process runs powershell.exe like UltraEdit or just powershell without path.
set "PATH=C:\Other PowerShell Directory;%PATH%" could be also set "PATH=%PATH:C:\Windows\System32\WindowsPowerShell\v1.0\=C:\Other PowerShell Directory%" to replace the default PowerShell path by a different one just for PATH used by UltraEdit (and all processes started by UltraEdit).
There can be of course also send a feature request email to UltraEdit support for requesting a configuration to define the PowerShell executable used on opening the Terminal window or running a *.ps1 file which is edited in UltraEdit.