nvbn/thefuck

Feature Request: Correct me when I type `figlet moo | cowsay`

Open

#1,159 建立於 2021年1月11日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Python (96,953 star) (3,949 fork)batch import
help wanted

描述

I would love for fuck to fix when I forget the -n piping figlet into cowsay:

⋊> ~ figlet moo | cowsay -n                                             15:38:05
 _________________________
/                         \
|  _ __ ___   ___   ___   |
| | '_ ` _ \ / _ \ / _ \  |
| | | | | | | (_) | (_) | |
| |_| |_| |_|\___/ \___/  |
\                         /
 -------------------------
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||
⋊> ~ figlet moo | cowsay                                                15:38:09
 _________________________________________
/                                         \
|                                         |
| _ __ ___ ___ ___ | '_ ` _ \ / _ \ / _ \ |
| | | | | | | (_) | (_) | |_| |_|         |
\ |_|\___/ \___/                          /
 -----------------------------------------
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||
⋊> ~ fuck                                                               15:38:10
No fucks given

I'll write a custom rule for this after work today for my own system, I'm more just checking if anyone else wants a copy when I'm done.

貢獻者指南

技術棧
pythonshell
領域
clitooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Python basicsthefuck rule structure
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
85
研究方向
The issue requests a new rule in thefuck to correct the command `figlet moo | cowsay` by adding the ` n` flag. To implement, study existing rules in the `thefuck/rules/` directory, create a Python function that matches the command pattern, and returns the corrected command. Add tests following the project's testing conventions. No linked PRs or complex dependencies exist.