为什么 Linux 命令手册页用不同的名称调用相同的东西？
column
-s
Specify a set of characters to be used to delimit columns for the -t option.
sort
-t, --field-separator=SEP
use SEP instead of non-blank to blank transition
cut
-d, --delimiter=DELIM
use DELIM instead of TAB for field delimiter
awk
-F fs
--field-separator fs
Use fs for the input field separator (the value of the FS predefined variable).
记住所有这些确实很难。
column
-s
Specify a set of characters to be used to delimit columns for the -t option.
sort
-t, --field-separator=SEP
use SEP instead of non-blank to blank transition
cut
-d, --delimiter=DELIM
use DELIM instead of TAB for field delimiter
awk
-F fs
--field-separator fs
Use fs for the input field separator (the value of the FS predefined variable).
It's really difficult to remember all of them.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
自然语言有时也会对同一事物有不同的词。为什么信息科学会有所不同？虽然对于同一件事/对象（再看一遍！）可能希望只有一个术语/单词/表达（看！），特别是在科学领域，但这充其量只是一厢情愿的想法。事实上，不同的人同时提出相同的概念，但用不同的词来命名。毕竟我们都是个人主义者。
因此，我的建议是（再次）在您自己的文本中争取一致的命名/术语（尽可能使用现有术语），并且要注意其他人/人们编写的任何文本都存在其他词汇/同侪。
Natural language also sometimes has different words for the same thing. Why would it be different in information science? While it might be desirable to have only one term/word/expression (see!) for the same thing/object (see again!), especially in science, this is wishful thinking at best. It's just a fact that different people come up with the same concepts at the same time but name it with different words. We're all individualists, after all.
So my advice is to strive for consistent naming/terminology (yet again) in your own texts (using existing terminology where possible) and just be aware that other vocabulary exists for any texts written by other people/folks/peers.
我猜想，命令行参数有所不同，因为这些程序都是由（最终）不相关的开发人员为不同的操作系统编写的。
即使在今天，从 GNU/Linux 的角度来看，*BSD 命令的行为常常很奇怪，反之亦然。
Command line arguments differ since these programs were all authored by (terminally) unrelated developers for different operating systems, I guess.
Even these days, *BSD commands often behave strangely from GNU/Linux standpoint and vice versa.