github / github/copilot-cli

Single tilde `~` is being used as markdown strikethrough markup when it should be double-tilde `~~`

Aberta
#1,936 3 comentários 3 reações 0 responsáveis Ver no GitHub
area:terminal-rendering
Linguagem predominante
Shell
Estrelas
11.2k
Forks
1.9k
Merge médio
14h 16min
PRs com merge (30d)
6

Descrição

### Describe the bug

When AI agent is writing about approximates it uses a single tilde `~` e.g., ~2000. When it does a few approximations in one line it gets rendered as markdown strikethrough. However, according to my research (see sites like https://www.markdownguide.org/extended-syntax/#strikethrough) it should only do strikethrough if we bookend with double tilde `~~`.
Please fix the renderer so it requires double tilde and doesn't strikethrough random parts of output.

Additional note: it seems to only happen if the tildes are inside parentheses: "Make a fix (~2000 lines) and delete old file (~5000 lines)", rendering tilde outside the parentheses works fine. I think it's probably a regex bug or something.

### Affected version

1.0.2

### Steps to reproduce the behavior

1. Use this prompt: `I'm testing a bug with your markdown rendering, print this line exactly: "Make a fix (~2000 lines) and delete old file (~5000 lines)"
2. You can also have it test another line like "There are ~100 ways this bug might appear and ~5 ways to fix it ~10% of the time" and see that it renders fine

### Expected behavior

Make sure the markdown only does strikethrough when `~~` is used.

### Additional context

Image

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

Locate the markdown renderer and its strikethrough parsing, then reproduce the reported strings with single tildes inside and outside parentheses. Confirm that single tildes remain literal while double tildes still produce strikethrough, and add or update coverage for both cases if the renderer has tests.

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

Avaliação

Stack de tecnologia
markdown
Domínio
cli
Tipo de issue
Bug
Dificuldade
3/5
Tempo estimado
1-2 dias
Status de atividade
Pouca atividade
Clareza
Razoavelmente clara
Facilidade para iniciantes
48/100

Receba novas issues na sua caixa de entrada

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