Add chapter on using bash #226
Conversation
| - `chmod` - Change the permissions on a file or directory | ||
| - `chown` - Change the owner of a file or directory | ||
| - `find` - Search for files and directories on the file system | ||
| - `locate`, `updatedb` - Search for files and directories quickly using a database |
There was a problem hiding this comment.
Locate is not essential, especially not when talking about Bash scripting (which I think is the main purpose of this guide?). It would be more apt when trying to argue that people don't need their graphical OS'es but can do everything from the command line.
There was a problem hiding this comment.
No, the main purpose of chapter would be to encourage people to know the functionality available from the (bash) command line, so they can work more efficiently. I wouldn't want to argue that you don't need a graphical OS, but I would like to argue that you can do lots of stuff much faster when you're proficient at using the command line.
There was a problem hiding this comment.
Ok, this is fine. So, do I understand correctly (also from other comments) that with this chapter you want to stimulate command line usage but discourage use of bash as a (scripting) language? In that case, maybe it shouldn't go under languages, but rather on some higher level or under some kind of directly under good practices section.
There was a problem hiding this comment.
Ok, this is fine. So, do I understand correctly (also from other comments) that with this chapter you want to stimulate command line usage but discourage use of bash as a (scripting) language?
Yes
In that case, maybe it shouldn't go under languages, but rather directly under good practices section.
Maybe I could add a note with a link there?
There was a problem hiding this comment.
Added a link from the best practices overview document (and also a short section on editors).
|
Ah, one other useful command to add may be |
Add chapter on using bash
Closes #215