| Table of Contents |
|---|
...
| Expand | ||
|---|---|---|
| ||
If your Windows version does not have ssh in Command Prompt or PowerShell:
More advanced options for those who want a full Linux environment on their Windows system:
|
From now on, when we refer to "Terminal", it is either the Mac/Linux Terminal program, Windows Command Prompt or PowerShell, or the PuTTY program.
...
| Code Block | ||
|---|---|---|
| ||
cd # hit Tab once after typing "laun" # This will expand to launcher_creator.py |
About command line input
You know the command line is ready for input when you see the command line prompt.
Like everything in Unix, the command line has similarities to a text file. And in Unix, all text file "lines" are terminated by a linefeed character (\n, also called a newline).
| Expand | ||
|---|---|---|
| ||
Note: The Unix linefeed (\n) line delimiter is different from Windows, where the default line ending is carriage-return + linefeed (\r\n), and some Mac text editors that just use a carriage return (\r). |
As mentioned earlier, the shell executes command line input when it sees a linefeed, which happens when you press Enter after entering the command.
But you can enter more than one command on a single line – just separate the commands with a semi-colon ( ; ).
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd; ls -lh |
You can also split a single command across multiple lines by adding a backslash ( \ ) at the end of the line you want to continue, before pressing Enter.
| Code Block | ||||
|---|---|---|---|---|
| ||||
ls6:~$ ls ~/.bashrc \
> local |
Notice that the shell indicates that it is not done with command-line input by displaying a greater than sign ( > ). You just enter more text then Enter when done.
| Tip | ||
|---|---|---|
| ||
At any time during command input, whether on the 1st command line prompt or at a > continuation, you can press Ctrl-c (Control key and the c key at the same time) to get back to the command prompt. |
Command input errors
You don't always type in commands, options and arguments correctly – you can misspell a command name, forget to type a space, specify an unsupported option or a non-existent file, or make all kinds of other mistakes.
What happens? The shell attempts to guess what kind of error it is and reports an appropriate error message as best it can.
Some examples:
| Code Block | ||
|---|---|---|
| ||
# You type the name of a command that is not installed on your system
ls6:~$ lz
Command 'lz' not found, but can be installed with:
apt install mtools
Please ask your administrator.
# You enter something that is close to an existing, or known, command
ls6:~$ catt
Command 'catt' not found, did you mean:
command 'cat' from deb coreutils (8.30-3ubuntu2)
command 'catty' from deb node-catty (0.0.8-1)
command 'ratt' from deb ratt (0.0~git20180127.c44413c-2)
Try: apt install <deb name>
# You try to use an unsupported option
ls6:~$ ls -z
ls: invalid option -- 'z'
Try 'ls --help' for more information.
# You specify the name of a file that does not exist
ls6:~$ ls xxx
ls: cannot access 'xxx': No such file or directory |