mirror of
https://codeberg.org/Mo8it/How_To_Linux.git
synced 2024-11-23 15:01:34 +00:00
Replace we did X
This commit is contained in:
parent
dd981a8ba8
commit
9a29ee859e
2 changed files with 6 additions and 6 deletions
|
@ -134,7 +134,7 @@ $ ls happy_house
|
||||||
friend1.txt friend2.txt
|
friend1.txt friend2.txt
|
||||||
```
|
```
|
||||||
|
|
||||||
We did verify that `friend2.txt` was moved.
|
We verified that `friend2.txt` was moved.
|
||||||
Let's move `friend3.txt`, too.
|
Let's move `friend3.txt`, too.
|
||||||
Enter `mv friend3.txt happy_house/loud_friend.txt`.
|
Enter `mv friend3.txt happy_house/loud_friend.txt`.
|
||||||
Take a look at the content of your directory now:
|
Take a look at the content of your directory now:
|
||||||
|
@ -322,7 +322,7 @@ No zombies!
|
||||||
No loud housemates!
|
No loud housemates!
|
||||||
```
|
```
|
||||||
|
|
||||||
We did use `cat` 😺 to only print the content of the file `rules.txt` without opening it with an editor.
|
We used `cat` 😺 to only print the content of the file `rules.txt` without opening it with an editor.
|
||||||
`cat` 🐈️ stands for _concatenate_.
|
`cat` 🐈️ stands for _concatenate_.
|
||||||
This does not sound like printing file content!?
|
This does not sound like printing file content!?
|
||||||
This is because `cat` 🐱 can be used to concatenate the content of multiple files.
|
This is because `cat` 🐱 can be used to concatenate the content of multiple files.
|
||||||
|
@ -434,7 +434,7 @@ $ wc -l -w rules.txt
|
||||||
|
|
||||||
We see that we get the number of lines and then the number of words.
|
We see that we get the number of lines and then the number of words.
|
||||||
|
|
||||||
We did learn how to access and read the manual, but how do we navigate the manual?
|
We learned how to access and read the manual, but how do we navigate the manual?
|
||||||
|
|
||||||
If you open a manual with `man`, you can scroll up and down using the arrow keys.
|
If you open a manual with `man`, you can scroll up and down using the arrow keys.
|
||||||
You can search by pressing `/`, then enter what you are search for, `lines` for example, and then press `Enter`.
|
You can search by pressing `/`, then enter what you are search for, `lines` for example, and then press `Enter`.
|
||||||
|
@ -493,10 +493,10 @@ No zombies!
|
||||||
No loud housemates!
|
No loud housemates!
|
||||||
```
|
```
|
||||||
|
|
||||||
We did copy the rules, but did you notice the dot at the end of the command `cp`?
|
We copied the rules, but did you notice the dot at the end of the command `cp`?
|
||||||
What does it mean?
|
What does it mean?
|
||||||
|
|
||||||
We did learn that the two dots `..` refer to the parent directory (one directory back).
|
We learned that the two dots `..` refer to the parent directory (one directory back).
|
||||||
One dot `.` refers to the current directory.
|
One dot `.` refers to the current directory.
|
||||||
|
|
||||||
Here are some **equivalent** commands that might help you understand paths in Linux:
|
Here are some **equivalent** commands that might help you understand paths in Linux:
|
||||||
|
|
|
@ -195,7 +195,7 @@ For example, if you don't care about the errors that some command throughs, then
|
||||||
|
|
||||||
### More details
|
### More details
|
||||||
|
|
||||||
We did discuss the most important cases for redirections.
|
We discussed the most important cases for redirections.
|
||||||
But there are some less important details like the following:
|
But there are some less important details like the following:
|
||||||
|
|
||||||
- `command &>filename` is equivalent to `command >filename 2>&1`, but not to `command 2>&1 >filename` because the order matters.
|
- `command &>filename` is equivalent to `command >filename 2>&1`, but not to `command 2>&1 >filename` because the order matters.
|
||||||
|
|
Loading…
Reference in a new issue