Fix order of arguments to `ln`
See original GitHub issueI have a pathological inability to get the arguments to ln
in the right order.
For some reason I always think it’s ln -s <origin> <destination>
whereas in fact it is ln -s <destination> <origin>
.
Can fuck
fix this?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Tips for remembering the order of parameters for ln?
Does anyone have any tips to help me remember the correct order? You create the second parameter just like with cp, and you...
Read more >I always forget the argument order of the `ln -s` command
An important lesson I learned while programming. The way I remember it is "ln -s target [filename]", where filename is an optional argument...
Read more >Andrew Ayer on Twitter: "Can't remember order of arguments ...
Can't remember order of arguments to ln? It's like cp/mv: first argument is existing file and second argument is file you want to...
Read more >How to remember order of parameters to `ln` command? [closed]
1 Answer 1 ... It takes arguments in the same order as cp and mv . ... I think the reason <existing> <new>...
Read more >[feature request] ln with command line arguments in reverse o
The issue simply is with the mental model made when approaching the "ln" command. In French, the usual way to say when creating...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Added in 3.10
Any of you willing to code it? I’m happy to coach ☺