github
/
the-art-of-command-line
mirror of https://github.com/jlevy/the-art-of-command-line
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Suggest using the keybindings of your favourite editor 

As stated in The Pragmatic Programmer (excerpt here: https://www.oreilly.com/library/view/the-pragmatic-programmer/9780135956977/f_0037.xhtml)
it's beneficial to use the same keybindings everywhere. This is possible in IntelliJ, Eclipse and probably many other IDEs.
pull/845/head
David Burström 2023-02-08 14:10:30 +01:00 committed by GitHub
parent 4d9f5b90bc
commit 5c9c925d76
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -50,7 +50,7 @@ Notes:
- Learn basic Bash. Actually, type `man bash` and at least skim the whole thing; it's pretty easy to follow and not that long. Alternate shells can be nice, but Bash is powerful and always available (learning *only* zsh, fish, etc., while tempting on your own laptop, restricts you in many situations, such as using existing servers).
- Learn at least one text-based editor well. The `nano` editor is one of the simplest for basic editing (opening, editing, saving, searching). However, for the power user in a text terminal, there is no substitute for Vim (`vi`), the hard-to-learn but venerable, fast, and full-featured editor. Many people also use the classic Emacs, particularly for larger editing tasks. (Of course, any modern software developer working on an extensive project is unlikely to use only a pure text-based editor and should also be familiar with modern graphical IDEs and tools.)
- Learn at least one text-based editor well. The `nano` editor is one of the simplest for basic editing (opening, editing, saving, searching). However, for the power user in a text terminal, there is no substitute for Vim (`vi`), the hard-to-learn but venerable, fast, and full-featured editor. Many people also use the classic Emacs, particularly for larger editing tasks. (Of course, any modern software developer working on an extensive project is unlikely to use only a pure text-based editor and should also be familiar with modern graphical IDEs and tools. If possible, reconfigure those to match the keybindings of your favourite editor.)
- Finding documentation:
- Know how to read official documentation with `man` (for the inquisitive, `man man` lists the section numbers, e.g. 1 is "regular" commands, 5 is files/conventions, and 8 are for administration). Find man pages with `apropos`.