Documentation: A "Coming from Perl" section
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 45/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- perl
调研方向
首先定位 Nushell 书中现有的“Coming from ”部分，并阅读它们的结构和示例。添加一个类似的“Coming from Perl”部分，为列出的 Perl 特殊变量提供符合 Nushell 惯用方式的替代方案，然后验证它是否符合本书的文档风格和导航结构。
由索引模型根据 Issue 内容生成。
描述
Related problem
The "Coming from " sections of the Nushell book are a great idea, but there is an obvious "other language" missing- Perl.
As a solution that aims to bridge the gap between shells and programming languages the Pathologically Eclectic Rubbish Lister (PERL) seems to me the natural ancestor/competitor of Nushell. Perl may be long in the tooth but it is still a very widely used tool on Linux / Unix based systems, and has a lot of features designed specifically to make it work well as a "glue" language.
It's not obvious (at least to me as a user new to Nushell) how some of the things Perl can do can be accomplished in Nushell, some specific "getting started" help would be useful.
Describe the solution you'd like
A documentation section on "Coming from Perl" could help open up Nushell to areas where Perl has been the "swiss army knife" of system automation for years.
As an example, it would be particularly helpful to have idiomatic Nushell alternatives for the Perl "special variables" including-
$0 $PROGRAM_NAME Pathname of the current script
$$ $PID The pid of the process running the current script
$^T $BASETIME Timestamp when the current process started
$< $UID Real user ID (uid) of this process
$> $EUID Effective user ID of this process
$( $GID Real group ID
$) $EGID Effective group ID
$! $ERRNO / $OS_ERROR Number or text of the error from the last system call
$? $CHILD_ERROR Status returned by the last child process
Describe alternatives you've considered
No response
Additional context and details
No response
- 主要语言
- TypeScript
- 星标
- 260
- 派生
- 563
- 平均合并
- 4 小时 36 分钟
- 30 天内合并 PR
- 16
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nushell/nushell.github.io 的其他 Issue
-
难度 1/5 1-3 小时 新手友好度 68/100
nushell/nushell.github.io#2081 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 62/100
nushell/nushell.github.io#767 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 58/100
nushell/nushell.github.io#2232 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 58/100
nushell/nushell.github.io#2209 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
nushell/nushell.github.io#2194 ·
维护者通常 1 天内回复
查看 nushell/nushell.github.io 的全部 Issue
相似的 Issue
-
triage
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
agent-ready area: config area: skills type: chore upstream: brain-kit
难度 1/5 1 小时以内 新手友好度 95/100
-
enhancement priority:low ready-for-dev
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
bug escritorio mapa
难度 2/5 1-3 小时 新手友好度 72/100
marcosferr/reporte-ciudadano#4 · 1 条评论 ·
-
area: material/sort gemini-triaged needs triage
难度 2/5 1-3 小时 新手友好度 70/100
angular/components#33933 ·
维护者通常 1 天内回复