tldr/pages/common/ln.md

# ln

> Creates links to files and folders.

- Create a symbolic link to a file or directory:

`ln -s {{path/to/file_or_directory}} {{path/to/symlink}}`

- Overwrite an existing symbolic to point to a different file:

`ln -sf {{path/to/new_file}} {{path/to/symlink}}`

- Create a hard link to a file:

`ln {{path/to/file}} {{path/to/hardlink}}`
Adds some examples for ln Hopefully this will help people remember if the source is the first or second argument 2014-02-17 16:59:07 +00:00			`# ln`

Formatted all pages according to guidelines. 2016-01-07 17:31:27 +00:00			`> Creates links to files and folders.`
Adds some examples for ln Hopefully this will help people remember if the source is the first or second argument 2014-02-17 16:59:07 +00:00
Refactor: add missing `or_directory` where needed. This commit adds the missing `_or_directory` to any example which is specifying an action affecting a file or a directory, but uses the token `{{path/to/file}}` instead of `{{path/to/file_or_directory}}`. 2019-02-08 00:31:19 +00:00			`- Create a symbolic link to a file or directory:`
Adds some examples for ln Hopefully this will help people remember if the source is the first or second argument 2014-02-17 16:59:07 +00:00
Refactor: add missing `or_directory` where needed. This commit adds the missing `_or_directory` to any example which is specifying an action affecting a file or a directory, but uses the token `{{path/to/file}}` instead of `{{path/to/file_or_directory}}`. 2019-02-08 00:31:19 +00:00			`ln -s {{path/to/file_or_directory}} {{path/to/symlink}}`
Adds some examples for ln Hopefully this will help people remember if the source is the first or second argument 2014-02-17 16:59:07 +00:00
reword to prevent ambiguity "original" can be associated with the origin of the link and lead to confusion if not read carefully. Also, the third example seems to have been copied from the prior example but not fully adapted: "original/file" should have said (if I'm reading this correctly) "original/folder". 2015-08-10 19:03:34 +01:00			`- Overwrite an existing symbolic to point to a different file:`
add a separate example for overwriting a symlink to make it clear what the -T option does, as discussed in #180 2015-03-15 11:40:20 +00:00
Applying the snake_case convention throughout the repo (#967) * Applying the snake_case convention throughout the repo - Also removing the file extension where not needed - Adding {{ }} on a few old pages * Addressing concerns - Added {{ }} where they were missed out - Removed spaces inside {{ }} - Reverting "file" to "filename" to make it clearer * Fixing the comments on nc page 2016-07-22 21:24:06 +01:00			`ln -sf {{path/to/new_file}} {{path/to/symlink}}`
add a separate example for overwriting a symlink to make it clear what the -T option does, as discussed in #180 2015-03-15 11:40:20 +00:00
Formatted all pages according to guidelines. 2016-01-07 17:31:27 +00:00			`- Create a hard link to a file:`
Adds some examples for ln Hopefully this will help people remember if the source is the first or second argument 2014-02-17 16:59:07 +00:00
reword to prevent ambiguity "original" can be associated with the origin of the link and lead to confusion if not read carefully. Also, the third example seems to have been copied from the prior example but not fully adapted: "original/file" should have said (if I'm reading this correctly) "original/folder". 2015-08-10 19:03:34 +01:00			`ln {{path/to/file}} {{path/to/hardlink}}`