Follow Up from https://lists.debian.org/debian-user/2021/03/msg01459.html,
Motivation: https://lists.debian.org/debian-user/2021/03/msg01358.html https://lists.debian.org/debian-user/2021/03/msg01362.html https://lists.debian.org/debian-user/2021/03/msg01365.html https://lists.debian.org/debian-user/2021/03/msg01435.html Wiki is not only about wikipedia, Word wiki to signify a collaborative effort in stockpiling code lines (Section 2 to be referred to, for elaboration). With minimal explanation. Only lines of codes (more in Section 2). The best possible method of learning appears to be minimal explanation, but exhaustive implementation of code lines in a console/terminal. Let (!@#$%) be replaced by the following phrase without [quote], [/quote]. [quote] with a list of all possible permutations / combinations (henceforth, abbreviated as PC) [of options, switches, RegEx, et al,] of basic, single code lines. List. Only. Minimal explanation. The console shall self-explain through output.[/quote] Section 2 ------------ The wiki would be one page for one Man Command (internal/external). But radically different from Man Page. Minimal(or zero) explanatory texts (!@#$%) Then an Upper Tier of wiki page having unique combination of two commands (internal/external) with (!@#$%) Then a still Upper Tier of wiki page having unique combination of three commands (internal/external) with (!@#$%) But we could stop at some Tier until further need for complexity arises. Books (or online bash scripting pages) are considered horrible, in the matter of wastage of time. For coding a different set of NeuNet are developed for abstract multi-dimensional memory space, while our intellect tries all sorts of possible PC of each sector of this memory space(MS) and could redefine/reorganise/compress this MS. Books address filling up this MS inefficiently. It also causes so much wastage of paper for so little purpose. In order for Debian books to explain things to us, our wiki should have specific line, section, page reference for any unique single line of code. Then books could be compressed to a minimal size. Wiki could be expanded, if required.
