Timeline for In bash, how to resolve what is actually going to be executed?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 15 at 10:52 | vote | accept | ocroquette | ||
| Mar 14 at 15:16 | comment | added | ocroquette | I am only interested in simple aliases, but as I just found out, the function proposed below did not even work with alias ls="ls [options]", which is pretty common. I updated the code to handle also this case, but of course, it might not work for more complex alias cases. | |
| Mar 14 at 9:03 | comment | added | Fravadona |
"interested in what will actually be executed, [...] I need a type-like tool that resolves the aliases and the links" => I don't think you can "resolve" an "alias" recursively as it can contain shell code.
|
|
| Mar 13 at 7:02 | history | edited | ocroquette | CC BY-SA 4.0 |
added 20 characters in body
|
| Mar 13 at 6:42 | comment | added | ocroquette | My main use cases currently are alias/links to tools in Python virtual environments and links caused by "/etc/alternatives". So resolving simple "mappings" like aliases and links is good enough for me. | |
| Mar 13 at 1:49 | comment | added | Wildcard | What if the symlink points to a file that is a shell script that calls another tool? How far do you want to go, and why? | |
| Mar 12 at 21:38 | history | edited | Kusalananda♦ |
edited tags; edited tags
|
|
| Mar 12 at 20:15 | answer | added | ocroquette | timeline score: 1 | |
| Mar 12 at 19:58 | answer | added | rr0ss0rr | timeline score: 0 | |
| Mar 12 at 19:21 | answer | added | Jukka Matilainen | timeline score: 0 | |
| Mar 12 at 19:17 | history | asked | ocroquette | CC BY-SA 4.0 |