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

The Windows path in 2.1 is using the wrong path separator

未关闭 适合新手
#2,091 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
git
领域
documentation

调研方向

从链接的第 2.1 节开始,在书籍源代码中搜索包含 C:/Users/user/my_project 的 Windows 示例。更新该示例,使其使用预期的 Windows 路径分隔符,然后验证渲染后的网站和 PDF 是否显示更正后的路径。

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

描述

bug
There's no existing/similar bug report.
  • I have searched the existing issues
This report is about a single actionable bug.
  • I'm reporting a single actionable bug
This report is about the ProGit book, version 2, English language.
  • This bug is not about a translation or old version
Bug covers book website/pdf
  • I confirm the bug is about the book as found on the website/pdf
Problem is present in the Pro Git book on the website?
  • This bug also affects the Pro Git book as published on the website.
Which version of the book is affected?

Source files

Describe the bug:

The book shows in section 2.1:

Initializing a Repository in an Existing Directory

If you have a project directory that is currently not under version control and you want to start controlling it with Git, you first need to go to that project’s directory. If you’ve never done this, it looks a little different depending on which system you’re running:

for Linux:

cd /home/user/my_project

for macOS:

cd /Users/user/my_project

for Windows:

cd C:/Users/user/my_project

The path separator in Windows is wrong - it should be C:\Users\user\my_project, not C:/Users/user/my_project

Steps to reproduce:
  1. Go to 'section 2.1, initializing a repository in an existing directory'
  2. See error
Expected behavior:

I expected the path separator \ to show.

Screenshots:
Image
Additional context:

No response

Device

laptop

Operating system

macOS 27.2 Beta 1

Browser/application + version

Safari 27.2

主要语言
CSS
星标
6.6k
派生
2.1k
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

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

progit/progit2 的其他 Issue

查看 progit/progit2 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

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