mirror of
https://codeberg.org/Mo8it/How_To_Linux.git
synced 2024-11-24 02:01:34 +00:00
Fix typos
This commit is contained in:
parent
72f484ee78
commit
35e6ecc0c4
2 changed files with 5 additions and 5 deletions
|
@ -90,7 +90,7 @@ The easiest option to get started with for programming on your own machine is [V
|
||||||
For a more advanced option, the next section will present another modal terminal editor that has even more features out of the box compared with Vim.
|
For a more advanced option, the next section will present another modal terminal editor that has even more features out of the box compared with Vim.
|
||||||
|
|
||||||
So why do we bother learning Vim then?
|
So why do we bother learning Vim then?
|
||||||
Althought you don't have to use Vim, you should at least learn it and be familiar with its basic keybindings.
|
Although you don't have to use Vim, you should at least learn it and be familiar with its basic keybindings.
|
||||||
Not only to be able to use it when you have to, but also because Vim keybindings are widely used by other programs, especially terminal user interfaces.
|
Not only to be able to use it when you have to, but also because Vim keybindings are widely used by other programs, especially terminal user interfaces.
|
||||||
|
|
||||||
Do you remember how we learned to navigate the manual when using `man`?
|
Do you remember how we learned to navigate the manual when using `man`?
|
||||||
|
@ -110,7 +110,7 @@ You can even use Vim keybindings in other editors to boost your editing efficien
|
||||||
In VS-Code for example, you get Vim keybindings by installing a plugin like [this](https://marketplace.visualstudio.com/items?itemName=vscodevim.vim).
|
In VS-Code for example, you get Vim keybindings by installing a plugin like [this](https://marketplace.visualstudio.com/items?itemName=vscodevim.vim).
|
||||||
|
|
||||||
> **Note**: Vim is the successor of `vi`.
|
> **Note**: Vim is the successor of `vi`.
|
||||||
> If you are using a system that doesn't have `vim` preinstalled and you don't have superuser priviliges to install it,
|
> If you are using a system that doesn't have `vim` preinstalled and you don't have superuser privileges to install it,
|
||||||
> then you will most probably at least find `vi` installed.
|
> then you will most probably at least find `vi` installed.
|
||||||
|
|
||||||
## Helix
|
## Helix
|
||||||
|
|
|
@ -11,7 +11,7 @@ Write a Bash script that installs the following _essential_ Linux packages for y
|
||||||
- `lolcat`
|
- `lolcat`
|
||||||
- `cbonsai`
|
- `cbonsai`
|
||||||
|
|
||||||
After the installation is done, the script should let `cowsay` inform the user that the insallation was successful.
|
After the installation is done, the script should let `cowsay` inform the user that the installation was successful.
|
||||||
|
|
||||||
Test your script!
|
Test your script!
|
||||||
|
|
||||||
|
@ -59,7 +59,7 @@ It should ask the user for a web page link and then download the PDF if a PDF li
|
||||||
|
|
||||||
The script should exit with the status code 1 while printing an error message to stderr in case no PDF link was found on the web page ❌
|
The script should exit with the status code 1 while printing an error message to stderr in case no PDF link was found on the web page ❌
|
||||||
|
|
||||||
Otherwise, it should print a message to stdout that the download was sucessful ✔️
|
Otherwise, it should print a message to stdout that the download was successful ✔️
|
||||||
|
|
||||||
## Task: Job scheduler
|
## Task: Job scheduler
|
||||||
|
|
||||||
|
@ -83,7 +83,7 @@ We will use the program `inotifywait`.
|
||||||
This program can monitor a directory and notify on changes within this directory.
|
This program can monitor a directory and notify on changes within this directory.
|
||||||
|
|
||||||
1. Start Zellij if you are not already using it.
|
1. Start Zellij if you are not already using it.
|
||||||
1. Find out which package porvides the program `inotifywait` and install it.
|
1. Find out which package provides the program `inotifywait` and install it.
|
||||||
1. Read the manual of `inotifywait` for a better understanding of what it does.
|
1. Read the manual of `inotifywait` for a better understanding of what it does.
|
||||||
1. Find out what events mean in the context of `inotifywait`.
|
1. Find out what events mean in the context of `inotifywait`.
|
||||||
1. Find out how to tell `inotifywait` to keep monitoring a directory and not exit after the first event.
|
1. Find out how to tell `inotifywait` to keep monitoring a directory and not exit after the first event.
|
||||||
|
|
Loading…
Reference in a new issue