Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

config options around saving history items particularly when debugging

Aberta
#4,198 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Stack de tecnologia
csharp, powershell
Domínio
cli, tooling

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Needs-Triage :mag:

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
  1. Provide config options to control saving history items when in debug mode - Save-Show/Save-DontShow/DontSave
  2. When config set to NotSave - do not add items into the current psreadline file implementation or any future db implementation
  3. When config set to Save-Show - add items into the current psreadline file implementation & show in the history lookup
  4. 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

Linguagem predominante
C#
Estrelas
4.4k
Forks
341
Nenhum PR com merge em 30d

Guia de contribuição

Abrir o guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de PowerShell/PSReadLine

Todas as issues de PowerShell/PSReadLine

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.