Documentation | user/start: Add WSL path warning and clarify config.ini step (!202)

[Muhammad Kamran Khan (@Muhammad-Kamran-Khan)]

Muhammad Kamran Khan commented on a discussion on user/start/bsp-build.md: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/202#note_138361

 >  ```none
 >  export PATH=$HOME/quick-start/rtems/@rtems-ver-major@/bin:"$PATH"
 >  ```
 > +> **Warning for Windows (WSL) Users:**
 > +> If you are using Windows Subsystem for Linux (WSL), ensure that you append to your existing PATH (using `:$PATH`) rather than overwriting it. Overwriting the PATH will cause Windows tools like `explorer.exe` or VS Code (`code`) to stop working from the terminal.
 > +>
 > +> **Solution:** If you lose access to these tools, you can still execute them using their absolute path (e.g., `/mnt/c/Windows/explorer.exe`) or restore access by restarting your terminal session.

Hi @joel, thanks for the guidance.

Restructuring Chapter 4 to add a centralized 'Common Issues' section is definitely the right approach for the long term. However, I currently do not have the time/bandwidth to undertake that larger refactoring task.

Since this MR is now technically correct (pipeline passing) and fixes a specific pain point for WSL users, could we merge this as is?

I am happy to open a separate Issue ticket for the 'Common Issues' restructuring so it can be tracked and picked up by someone else (or me) in the future.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/202#note_138361
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260110/5939a862/attachment-0001.htm>