this post was submitted on 26 Mar 2026
37 points (95.1% liked)
Linux
64114 readers
794 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You can use long option names instead too, as each capital letter mode has a long option name, such as
-R --removeand-S --sync.My problem is that it's a flag and not like
# pacman removeI don't get why that is a problem. It's just an option name with 2 dashes in front. In fact, that is the "correct" way of handling options, as in standard option processing in GNU / Linux. I personally dislike options without dash, but on the other hand it does not bother me enough to be bothered by it.
pacman --removeis almost identical topacman remove, so I don't know why that is a "problem".Because it's not an option but a subcommand.
Guix and standard tooling like perf also use subcommands. I'm used to flags/options modifying the way the same inputs are processed, not completely changing what you give as $1.
But its just a matter of 2 dashes. It shouldn't be a problem.
You misunderstand me. It's not about typing it. It's not conforming to prevalent Linux paradigms which creates artificial confusion and learning difficulties. There's a reason it's
git pulland notgit -L,perf annotateand notperf -A. It's a great semantic difference like<b>vs<h3>. I'm saying this as an Arch user.I don't think it would make ANY difference if the option was named
git --pullinsteadgit pull(you don't have to use the single uppercase). That is NOT the same semantic difference between and , because it (the pull example) operates the same as before. The only difference are the two dashes. I don't see how this creates confusion or learning difficulties.The prevalent way (except for ancient tools like tar), and thus the norm, is that options are meant to be optional and subcommands are like old "do one thing" Unix commands (do completely different things, can have completely different set of arguments) but you prepend the name of the software in front of them. You can see the impact of this reflected in documentation for argument parsers: https://docs.python.org/3.14/library/argparse.html#%3A%7E%3Atext=Required+options+are+generally+considered+bad+form+because+users+expect+options+to+be+optional https://gobyexample.com/command-line-subcommands#%3A%7E%3Atext=Command-Line+Subcommands-%2CGo+by+Example%3A+Command-Line+Subcommands%2Cthat+have+their+own+flags.
I know how subcommands work. But that is not the point I am making. Having two dashes in front of it or not like
pacman removeorpacman --removedoes not change how the command operates. It is literally having two dashes or not and therefore is not an issue.Hmm, I don't know about Pacman, but for example openSUSE's
zypper removehas a--clean-depsflag, which doesn't exist on the other subcommands. So, it wouldn't make sense to have it bezypper --remove --clean-deps...