Timeline for Get the canonical path for a command
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 20, 2016 at 22:28 | history | edited | Gilles 'SO- stop being evil' | CC BY-SA 3.0 | remove bad advice to use which |
| May 20, 2016 at 13:09 | vote | accept | mythic | ||
| May 20, 2016 at 12:09 | history | edited | Petr Skocik | CC BY-SA 3.0 | added 156 characters in body |
| May 20, 2016 at 12:07 | comment | added | Stéphane Chazelas | Beware which has a number of issues. The standard command would be command -v (though would return the command name for those commands that are builtin). | |
| May 20, 2016 at 12:06 | comment | added | Stéphane Chazelas | [ ! -L "$cdpath" ] is not a guarantee that the path is canonical or even absolute. The path could still be relative, and another of the components but the last may be a symlink. | |
| May 20, 2016 at 12:01 | history | answered | Petr Skocik | CC BY-SA 3.0 |