docs: add Cygwin terminal configuration for Windows users

[KJ7LNW]

Context

This PR adds documentation for configuring Cygwin as a terminal in VS Code for Windows users in the shell integration guide.

Implementation

The implementation adds a new section under 'Additional Troubleshooting for Windows Users' that includes:

• Installation steps for Cygwin
• VS Code settings.json configuration with explanation of parameters
• Instructions for setting Cygwin as the default terminal
• Guidance on opening Cygwin terminals
• Note about shell integration compatibility

This helps Windows users who prefer Cygwin's Unix-like environment to properly configure it with shell integration support.

How to Test

1. Review the added documentation in docs/shell-integration.md
2. Verify the instructions are clear and accurate
3. If possible, test the configuration on a Windows system with Cygwin installed

Get in Touch

Discord: KJ7LNW

---

Important

Adds Cygwin terminal configuration for Windows users in shell-integration.md, including installation and setup instructions.

• Documentation:
  • Adds Cygwin configuration section to shell-integration.md for Windows users.
  • Includes installation steps, settings.json configuration, and setting Cygwin as default terminal.
  • Provides guidance on opening Cygwin terminals and notes on shell integration compatibility.

^{This description was created by for 49a8cb4. You can customize this summary. It will automatically update as commits are pushed.}

[vercel]

Someone is attempting to deploy a commit to the Roo Code Team on Vercel.

A member of the Team first needs to authorize it.

[daniel-lxs]

cc: @hannesrudolph

[KJ7LNW]

@hannesrudolph this PR is broken, can you add this somewhere in the shell integration section?

### Cygwin (bash, zsh)

Cygwin provides a Unix-like environment on Windows systems. To configure Cygwin as your terminal in VS Code:

1. Install Cygwin from [https://www.cygwin.com/](https://www.cygwin.com/)

2. Open VS Code settings:
   - Select File > Preferences > Settings
   - Click the "Open Settings (JSON)" icon in the top right corner
   
3. Add the following configuration to your `settings.json` (inside the top-level curly braces `{}`):
   ```json
   {
     "terminal.integrated.profiles.windows": {
       "Cygwin": {
         "path": "C:\\cygwin64\\bin\\bash.exe",
         "args": ["--login"],
         "env": {"CHERE_INVOKING": "1"}
       }
     },
     "terminal.integrated.defaultProfile.windows": "Cygwin"
   }
   ```

   > Note: If you have 32-bit Cygwin installed, use `"C:\\cygwin\\bin\\bash.exe"` for the path.

4. Understanding the configuration:
   - `path`: Points to the Bash executable in your Cygwin installation
   - `args`: The `--login` flag ensures the shell reads profile files
   - `env`: The `CHERE_INVOKING` environment variable tells Cygwin to use the current directory as the working directory
   - `terminal.integrated.defaultProfile.windows`: Sets Cygwin as the default terminal profile

5. To open a new Cygwin terminal:
   - Press Ctrl+Shift+(backtick) to open a new terminal, or
   - Press `F1`, type "Terminal: Create New Terminal (with Profile)", and select "Cygwin"

While our testing shows that this works out of the box, if you encounter shell integration issues with Cygwin, ensure you have added the appropriate shell integration hooks to your Cygwin bash profile as described in the "Manual Shell Integration Installation" section.

[KJ7LNW]

thank you just make sure it does what you want because it looks like some of the files may have moved around since I pushed this

[hannesrudolph]

yeah i was looking at that

[hannesrudolph]

ok @KJ7LNW is that proper now?

[Copilot]

Pull Request Overview

This PR enhances the shell integration guide by adding instructions for configuring Cygwin as a terminal in VS Code on Windows, and refines existing troubleshooting sections.

• Introduces a new “Cygwin (bash, zsh)” section with installation steps and settings.json configuration.
• Explains how to set Cygwin as the default terminal and open new Cygwin shells.
• Updates the command chaining example under Known Issues for proper encoding.

Comments suppressed due to low confidence (1)

docs/features/shell-integration.md:421

• Using && inside backticks will render as literal && instead of &&. Replace with backtick-escaped && without HTML escaping to display the intended operator.

**Workaround**: Instead of multi-line commands, use command chaining with `&&` to keep everything on one line (e.g., `echo a && echo b` instead of typing each command on a separate line).

[KJ7LNW]

Other than that missing header it looks great. Thank you for cleaning that up!

[KJ7LNW]

I think you want to keep this header:

---
## Known Issues and Workarounds