Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Suggestion: Extent interactive mode to enable user input

未关闭
#3,641 0 条评论 3 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
32/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
cli

调研方向

Start by reading the CLI's interactive mode used with -wi2 and trace how it presents and handles correction choices. Determine how a user-entered correction should fit that interaction, then test the flow with a word such as procees. Done means users can enter a custom correction while retaining the existing skip and suggested-correction options.

由索引模型根据 Issue 内容生成。

描述

enhancement

I frequently use codespell with -wi2 to correct multiple typos in long files before committing them. Every now and then, however, codespell (understandably) fails to suggest the desired correction, in which case I'm forced to skip it and manually fix it, which adds quite a bit of of overhead to the process. It would be great if I could provide the desired word on the spot. My suggestion is that given N suggested corrections, codespell would provide an N+1-th option that would prompt the user for the word.

Real example: I typed procees, so codespell gives me the options to type 0 for process or nothing for doing nothing. What it should do is provide the additional option of 1 (or -1 or so), which would then allow me to type proceeds, which is what I actually meant to type.

主要语言
Python
星标
2.4k
派生
531
平均合并
15 小时 5 分钟
30 天内合并 PR
18

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

codespell-project/codespell 的其他 Issue

查看 codespell-project/codespell 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。