Difference between revisions of "Ittcl"

From LibrePlanet
Jump to: navigation, search
(Added background about the process.)
Line 8: Line 8:
 
[[Action description:: Introduction to the Command Line (2nd ed.)]]
 
[[Action description:: Introduction to the Command Line (2nd ed.)]]
  
This page lists proposed changes we are considering making to the second edition of <a href="https://shop.fsf.org/books-docs/introduction-command-line">Introduction to the Command Line</a>.
+
This page lists proposed changes we are considering making to the second edition of [https://shop.fsf.org/books-docs/introduction-command-line Introduction to the Command Line].
 +
 
 +
The [http://write.flossmanuals.net/command-line/introduction/ current draft] is on the [http://flossmanuals.net/ FLOSS Manuals] site. You can sign up for an account on FLOSS Manuals and edit the book.
 +
 
 +
The following ideas for changes have been proposed so far. We do not want to make the book longer, though.
 +
 
 +
* Add a one-page quick-ref sheet to chapters on key tools.
 +
* Add Git and perhaps a reference to GitLab
 +
* Vi, nano should be the two editors covered, with pointers to others such as Emacs, Kedit, Gedit, and Puma. The latter two are graphical, should not be a focus.
 +
* Drop the discussion of file descriptors (beyond 0, 1, 2) as too advanced. Add the <(command) feature as an alternative to piping.
 +
* Consider Visual Bash
 +
* Reduce the languages covered to Python and Ruby. Mention IDEs but do not cover any.
 +
* Mention but do not cover telnet. FTP and Rsync are useful and should be covered
 +
* Along with screen, mention Tmux, Byobu.
 +
* Mention the Fish simple scripting.
 +
* Mention Pipe Viewer (pv).
 +
* Consider advanced tools: network tools such as ip and tracenet, strace, systemd.
 +
* Add a history of the shell.
 +
* Point to more web resources.

Revision as of 15:13, 11 May 2018


Introduction to the Command Line (2nd ed.)

This page lists proposed changes we are considering making to the second edition of Introduction to the Command Line.

The current draft is on the FLOSS Manuals site. You can sign up for an account on FLOSS Manuals and edit the book.

The following ideas for changes have been proposed so far. We do not want to make the book longer, though.

  • Add a one-page quick-ref sheet to chapters on key tools.
  • Add Git and perhaps a reference to GitLab
  • Vi, nano should be the two editors covered, with pointers to others such as Emacs, Kedit, Gedit, and Puma. The latter two are graphical, should not be a focus.
  • Drop the discussion of file descriptors (beyond 0, 1, 2) as too advanced. Add the <(command) feature as an alternative to piping.
  • Consider Visual Bash
  • Reduce the languages covered to Python and Ruby. Mention IDEs but do not cover any.
  • Mention but do not cover telnet. FTP and Rsync are useful and should be covered
  • Along with screen, mention Tmux, Byobu.
  • Mention the Fish simple scripting.
  • Mention Pipe Viewer (pv).
  • Consider advanced tools: network tools such as ip and tracenet, strace, systemd.
  • Add a history of the shell.
  • Point to more web resources.