Is it possible we could organize this article **not** in alphabetical order?
For new users seeing a list of random 2-3 letter words in the ToC is hardly useful. Maybe we could have sections instead such as "Directories" with things like mkdir and ls, "Permissions" with chown, chmod, and "View files" with head, tail, cat, pagers, etc This would make it much easier for someone to learn how to do something like create/delete/edit a file. It would also make it much easier for a person to look up a command they have forgot the name of. This document organizes the core utils by function: https://www.gnu.org/software/coreutils/manual/coreutils.html#touch-invocation so maybe we could so something like that but much simpler and focus on tools people would need to know to install and configure Arch initially. Meskarune (talk) 03:05, 13 March 2018 (UTC)
- Past discussion: https://wiki.archlinux.org/index.php?title=Talk:Core_utilities&oldid=334765 -- Lahwaacz (talk) 07:18, 13 March 2018 (UTC)
- I see, it sounds like they couldn't decide on groupings back then. I would propose just using the gnu groupings and only include the utils needed to install/configure and troubleshoot arch from the live CD. Keep the list some what small and then link to gnu's documentation. Meskarune (talk) 15:55, 5 April 2018 (UTC)
- It could be added, yes. Problem I see with crosslinking is that it is not easy to construct a sentence around it, because the target is the first argument. For example, try to crosslink
ln -s /dev/null /etc/pacman.d/hooks/70-dkms-install.hook..
- "To disable the
70-dkms-install.hookhook, symlink its name from
/dev/null." - works but is complicated. --Indigo (talk) 17:24, 19 May 2016 (UTC)
- I don't know, a new section can indeed be useful to mention the counterintuitive syntax and the smart cp -s alternative, but about replacing symlink instructions with verbose instructions I tend to be against: compared to the more famous similar cases, I've always totally supported Help:Style#Package management instructions because it allows to easily link to packages and make sure that users are aware of all the package management best practices, but for example since the switch to systemd (with the short rc.d transition), I've always found it slightly hard to systematically enforce Help:Style#systemd units operations, which — I have to be honest — exists only as an adaptation of the older rule that was used to describe the more complex initscripts method to enable/disable daemons. Introducing a new similar rule for symlinks would feel even less natural to me, IMHO reducing the readability of articles. — Kynikos (talk) 05:07, 21 May 2016 (UTC)
- I don't see how cp is better:
cp -s foo bardoes exactly the same as
ln -s foo bar. Both tools have the
-tflag to potentially swap the order of arguments.
- I agree with Kynikos: there are no gotchas to be described, so the explicit command is as clear and brief as it can be. As for Help:Style#systemd units operations, I believe one of its points is to provide a choice between starting and enabling units, which is very cumbersome to describe with explicit code blocks.
- -- Lahwaacz (talk) 11:22, 21 May 2016 (UTC)
- I don't see how cp is better: