config options around saving history items particularly when debugging
還沒有人認領這個 Issue。
評估
研究方向
Start by reading PSReadLine's current file-based history implementation and PowerShell's History.cs, which the issue identifies as both needing changes. Determine how debug commands are recorded and how history lookup displays them. Done means the proposed Save-Show, Save-NotShow, and NotSave behaviors are defined and implemented consistently across both components, with coverage for each mode.
由索引模型根據 Issue 內容生成。
描述
Originally raised in the PowerShell/PowerShell repo in issue 24354 by @specerboatepic
Context / Rational
When stepping through a function, one usually "spams" a combination of 'v' 'n' 'c' in debug mode. Once the function ends, or the user enters 'q', debug mode ends but those collection of debug commands are saved in the history of inputted commands, making it harder to find relevant commands in the history (pressing up on the keyboard) while searching through it. These debug commands should be disposed of from the history when debug mode ends because they are no longer useful in the scope of the session.
Thoughts/Findings
This needs work in both PSReadLine and PowerShell's History.cs file hence these issues being linked together
This also opens up the potential for new control mechanisms in PSReadLine for how we handle things like sensitive entries going forward as per #4197 and as such is linked to my issue #1886
Proposed implementation in PSReadLine
- Provide config options to control saving history items when in debug mode - Save-Show/Save-DontShow/DontSave
- When config set to NotSave - do not add items into the current psreadline file implementation or any future db implementation
- When config set to Save-Show - add items into the current psreadline file implementation & show in the history lookup
- When config set to Save-NotShow - add items into the current psreadline file implementation but mark as DontShow or any future db implementation
Similarly we'd need almost same implementation in PowerShell from my understanding
- 主要語言
- C#
- 星號
- 4.4k
- 分支
- 342
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
PowerShell/PSReadLine 的其他 Issue
-
Get-PSReadLineOption emits the ListView window-size warning, so prompt modules trigger it on every shell start可能已有人在做 @thc1006 於 42 天前認領。 未關閉Needs-Triage :mag:
難度 2/5 1-3 小時 新手友好度 78/100
PowerShell/PSReadLine#5205 ·
-
Needs-Triage :mag:
難度 2/5 1-3 小時 新手友好度 68/100
PowerShell/PSReadLine#5195 ·
-
Needs-Triage :mag:
難度 2/5 1-3 小時 新手友好度 72/100
PowerShell/PSReadLine#5121 ·
-
Needs-Triage :mag:
難度 2/5 1-3 小時 新手友好度 64/100
PowerShell/PSReadLine#5045 ·
-
Area-CommandHelp Issue-Enhancement
難度 1/5 1 小時以內 新手友好度 68/100
PowerShell/PSReadLine#3470 · 3 個 reaction ·
查看 PowerShell/PSReadLine 的全部 Issue
相似的 Issue
-
enhancement
難度 2/5 1-3 小時 新手友好度 62/100
維護者通常 1 天內回覆
-
area:re1 bounty help wanted needs-game
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 2/5 1-3 小時 新手友好度 68/100
StackExchange/StackExchange.Redis#3274 ·
維護者通常 1 天內回覆
-
affected/v17 affected/v18 area/frontend type/bug
難度 2/5 1-3 小時 新手友好度 82/100
umbraco/Umbraco-CMS#24186 ·
維護者通常 2 天內回覆
-
bug interpreter silently-wrong small
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆