Post reply

Name:
Email:
Subject:
Message icon:
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What is the last letter in the word "SlickEdit":
How many LETTERS are in the following? "a1b2c3":
Which number is missing?  "12345689":

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: jorick
« on: November 14, 2025, 07:03:11 PM »

I'll keep that in mind, but I try to avoid rebooting whenever possible because I have WSL with a bunch of serial ports passed through via usbipd, and it takes a while to set them up again.

Yes, Windows is a pane...
Posted by: Clark
« on: November 14, 2025, 06:59:25 PM »

I do know that after modifying environment variables on Windows, it's a good idea to reboot because they don't always get updated everywhere.
Posted by: jorick
« on: November 14, 2025, 06:56:02 PM »

When I started with a clean config, the Windows path and SE's path were exactly the same.  Then I launched SE normally and the paths were also the same but with an extra SE v30 path at the start.

There may have been a reboot before I tried your suggestion.  When I came in this morning, my apps looked like a reboot had happened.  Sorry, I have no control over when updates are pushed to my work computer.
Posted by: Clark
« on: November 13, 2025, 09:42:26 PM »

Because SlickEdit's builds are very free form (unstructured), the PATH is modified so certain tools can be found. Although, I don't understand why "C:\Program Files\SlickEdit Pro 29.0.4\win\" is getting added if you running v30.

Try starting SlickEdit with a clean config. Then immediately check the value of your PATH in SlickEdit's Build window.

"C:\Program Files\SlickEdit Pro 30.0.0\win\vs" -sc c:\temp\newconfig

It is possible to modify the PATH in user.cfg.xml and certain project build commands will force the PATH to get modified.
Posted by: jorick
« on: November 13, 2025, 09:15:25 PM »

I ran it from the command prompt in Windows Terminal, then did an "echo %PATH% from the SE terminal window, and I get a hodge-podge of paths where some are new and some are old, but it doesn't match what's actually defined.  Here's the path in SE's terminal window:

Quote
C:\Program Files\PowerShell\7;C:\Program Files\SlickEdit Pro 30.0.0\win\;C:\Program Files\SlickEdit Pro 29.0.4\win\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\WindowsPowerShell\Scripts;C:\Program Files\CMake\bin;C:\Program Files\PuTTY\;C:\Program Files\doxygen\bin;C:\Windows\System32\wbem;C:\Program Files\Git\cmd;C:\Program Files\usbipd-win\;C:\Program Files (x86)\SimplySerial\;C:\Users\RickyBennett\AppData\Local\Microsoft\WindowsApps;C:\Users\RickyBennett\OneDrive - Privoro\Commands;C:\Program Files\SEGGER\JLink_V886;C:\Users\RickyBennett\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\RickyBennett\AppData\Local\GitHubDesktop\bin;C:\Users\RickyBennett\AppData\Local\Microsoft\WinGet\Links;C:\Users\RickyBennett\AppData\Local\Microsoft\WinGet\Packages\oss-winget.dtc_Microsoft.Winget.Source_8wekyb3d8bbwe\usr\bin;C:\Users\RickyBennett\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.13_qbz5n2kfra8p0\LocalCache\local-packages\Python313\Scripts;C:\Program Files\7-Zip;W:\firmware_ate;C:\Program Files\LLVM\bin;C:\Program Files\TortoiseGit\bin;C:\Program Files\PowerShell\7\;C:\Users\RickyBennett\AppData\Local\Microsoft\WindowsApps;C:\Users\RickyBennett\OneDrive - Privoro\Commands;C:\Program Files\SEGGER\JLink_V886;C:\Users\RickyBennett\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\RickyBennett\AppData\Local\GitHubDesktop\bin;C:\Users\RickyBennett\AppData\Local\Microsoft\WinGet\Links;C:\Users\RickyBennett\AppData\Local\Microsoft\WinGet\Packages\oss-winget.dtc_Microsoft.Winget.Source_8wekyb3d8bbwe\usr\bin;C:\Users\RickyBennett\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.13_qbz5n2kfra8p0\LocalCache\local-packages\Python313\Scripts;C:\Program Files\7-Zip;C:\Program Files\doxygen\bin;W:\firmware_ate;C:\Users\RickyBennett\AppData\Local\Microsoft\WinGet\Packages\MartinStorsjo.LLVM-MinGW.UCRT_Microsoft.Winget.Source_8wekyb3d8bbwe\llvm-mingw-20251021-ucrt-x86_64\bin;

And here's the system path:

Quote
C:\Program Files\SlickEdit Pro 30.0.0\win\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\WindowsPowerShell\Scripts;C:\Program Files\CMake\bin;C:\Program Files\PuTTY\;C:\Program Files\doxygen\bin;C:\Windows\System32\wbem;C:\Program Files\Git\cmd;C:\Program Files\usbipd-win\;C:\Program Files (x86)\SimplySerial\;C:\Users\RickyBennett\AppData\Local\Microsoft\WindowsApps;C:\Program Files\SEGGER\JLink_V886;C:\Users\RickyBennett\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\RickyBennett\AppData\Local\GitHubDesktop\bin;C:\Users\RickyBennett\AppData\Local\Microsoft\WinGet\Links;C:\Users\RickyBennett\AppData\Local\Microsoft\WinGet\Packages\oss-winget.dtc_Microsoft.Winget.Source_8wekyb3d8bbwe\usr\bin;C:\Users\RickyBennett\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.13_qbz5n2kfra8p0\LocalCache\local-packages\Python313\Scripts;C:\Program Files\7-Zip;C:\Program Files\LLVM\bin;C:\Program Files\TortoiseGit\bin;C:\Program Files\PowerShell\7\;

And here's the user path:

Quote
%USERPROFILE%\AppData\Local\Microsoft\WindowsApps;C:\Users\RickyBennett\OneDrive - Privoro\Commands;C:\Users\RickyBennett\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\RickyBennett\AppData\Local\GitHubDesktop\bin;C:\Users\RickyBennett\AppData\Local\Microsoft\WinGet\Links;C:\Users\RickyBennett\AppData\Local\Microsoft\WinGet\Packages\oss-winget.dtc_Microsoft.Winget.Source_8wekyb3d8bbwe\usr\bin;C:\Program Files\doxygen\bin;W:\firmware_ate;C:\Users\RickyBennett\AppData\Local\Microsoft\WinGet\Packages\MartinStorsjo.LLVM-MinGW.UCRT_Microsoft.Winget.Source_8wekyb3d8bbwe\llvm-mingw-20251021-ucrt-x86_64\bin;

Note that the SE v29 path appears in the SE path but doesn't appear in either the system or user path.
Posted by: Clark
« on: November 13, 2025, 09:03:16 PM »

Are you running vs.exe from the terminal? If not, try starting SlickEdit from your terminal window.
Posted by: jorick
« on: November 13, 2025, 06:05:38 PM »

My PATH environment variable has changed but SE isn't picking up the changes.  I still see the old values in the Terminal window, and project commands are failing because they are using the old PATH variable.  I've restarted SE but it's still picking up the old PATH variable on restart. 

If I open a normal command window, it has the new path in it.  I have custom icons that run a batch file in a new window and they all have the new path.  But internal SE commands (project-execute and the like) all have the old path.

How do I get SE to use the new PATH variable?

==========

SlickEdit Pro 2025 (v30.0.0.0 64-bit Qt5)

Serial number: [redacted]
Licensed number of users: Single user
License file: C:\ProgramData\slickedit\30\slickedit.lic

Build Date: October 18, 2025
Emulation: CodeWright

OS: Windows 11 x64
OS Version: 11.00.0 
Memory: 42% Load, 27558MB/64980MB Physical, 27504MB/69076MB Page File, 4613MB/134217727MB Virtual
Shell Information: C:\WINDOWS\system32\cmd.exe /q
Screen Size: 1920 x 1080 (0 0 1920 1080), 3840 x 2160 (-2835 -2160 3200 1800), 3840 x 2160 (1005 -2170 3200 1800)

Project Type: Gnuc
Language: .txt (Plain Text)
Encoding: ACP (1252)

Installation Directory: C:\Program Files\SlickEdit Pro 30.0.0\ (non-removable drive,NTFS,708750MB free)
Configuration Directory: C:\Users\RickyBennett\AppData\Local\SlickEdit\30.0.0\ (non-removable drive,NTFS,708750MB free)
Migrated from: C:\Users\RickyBennett\AppData\Local\SlickEdit\29.0.4\