-
-
Notifications
You must be signed in to change notification settings - Fork 455
Fix command issue for pswh.exe #3657
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
🥷 Code experts: no user but you matched threshold 10 Jack251970, onesounds have most 👩💻 activity in the files. See details
Activity based on git-commit:
Knowledge based on git-blame: To learn more about /:\ gitStream - Visit our Docs |
|
Be a legend 🏆 by adding a before and after screenshot of the changes you made, especially if they are around UI/UX. |
This comment has been minimized.
This comment has been minimized.
📝 WalkthroughWalkthroughThe change updates the command argument construction for PowerShell Core ( Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant ShellPlugin
participant Terminal
User->>ShellPlugin: Execute command via Shell plugin
ShellPlugin->>ShellPlugin: PrepareProcessStartInfo()
alt UseWindowsTerminal is true
ShellPlugin->>ShellPlugin: Add backslash before semicolon
else UseWindowsTerminal is false
ShellPlugin->>ShellPlugin: No backslash added
end
ShellPlugin->>Terminal: Start process with constructed command
Assessment against linked issues
Assessment against linked issues: Out-of-scope changesNo out-of-scope changes found. Suggested labels
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (4)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR addresses the command issue for pswh.exe by modifying how command strings are built, particularly for Windows Terminal scenarios. Key changes include introducing an escape sequence variable for handling semicolon conflicts and updating command string interpolation in both Powershell and Pwsh cases.
Comments suppressed due to low confidence (2)
Plugins/Flow.Launcher.Plugin.Shell/Main.cs:223
- [nitpick] The variable name 'addedCharacter' might be ambiguous regarding its purpose. Consider renaming it to 'escapeSequence' to better convey that it holds the escape characters.
var addedCharacter = _settings.UseWindowsTerminal ? "\" : "";
Plugins/Flow.Launcher.Plugin.Shell/Main.cs:250
- [nitpick] The same variable 'addedCharacter' is defined here; renaming it to 'escapeSequence' across both cases would improve clarity and maintain consistency.
var addedCharacter = _settings.UseWindowsTerminal ? "\" : "";
@check-spelling-bot Report🔴 Please reviewSee the 📂 files view, the 📜action log, or 📝 job summary for details.
See ❌ Event descriptions for more information. If the flagged items are 🤯 false positivesIf items relate to a ...
|
Follow on with #3225. Resolve #3654.