Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

sdiff: fix the layout of unchanged rows, blank lines and cut tabs

未關閉
#300 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

@sami-daniel 已經在處理了。

開始於 2026年10月6日。

  • #301 來自 @sami-daniel —— 未關閉

評估

難度
2/5
預估耗時
1-3 小時
新手友好度
28/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
停滯
技術堆疊
rust
領域
cli

研究方向

Work is already claimed by open PR 301. The issue names src/side_diff.rs and confines the change to process_half_line and push_output: print each half’s text, keep the column where output stopped, and pad from that column to the marker and to column two. Compare against GNU diff -y with --width and --expand-tabs using the given L/R examples; done when unchanged rows, blank lines, and cut tabs match GNU layout.

由索引模型根據 Issue 內容生成。

描述

src/side_diff.rs pads the left half up to a fixed column and writes the right half after it, instead of padding from the column where the text ended. Three rows come out different from GNU diff:

  • The right half of an unchanged row starts at half_width + 3 instead of column two. The two are the same at the default --width=130, so it only shows at other widths and with --expand-tabs.
  • A blank line common to both files is padded up to column two instead of left empty.
  • A tab that reaches the end of the half is dropped, and the text after it is still printed. GNU diff cuts the row at that tab.

Tabs are shown as ^I and line ends as $:

$ diff -y --width=40 L R | cat -A      # L: a,(blank),b,c   R: a,(blank),c
a^I^I   a$
^I^I   $
b^I^I   <$
c^I^I   c$

$ diff -y --width=10 L R | cat -A      # L: a<TAB>b,c   R: c
ab  <$
c    c$

GNU diff 3.10 prints:

a^I^I^Ia$
$
b^I^I   <$
c^I^I^Ic$

a   <$
c^Ic$

So the change is confined to process_half_line and push_output. Print only the text of each half, keep the column where the output stopped, and pad from that column to the marker and to column two.

主要語言
Rust
星號
276
分支
44
平均合併
1 天 18 小時
30 天內合併 PR
9

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

uutils/diffutils 的其他 Issue

查看 uutils/diffutils 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。