writing about PATH is so funny, it's like
1. just add “PATH=$PATH:/my/dir" to your shell config, no big deal
2. ok but uh also you need to worry about path ordering, maybe it has to be `PATH=/my/dir:$PATH` instead
3. oh also bash sometimes caches PATH lookups, so if that happens then you need to run `rehash`
4. oh yeah and also if there are spaces in your PATH, then you need to quote it every time you add to it, like `PATH=/my/dir:”$PATH”`
5. also sometimes commands are aliases or builtins
Julia Evans /
npub1ym…nlm9y
2024-09-11 18:47:54
Author Public Key
npub1ym9ddu2qh7rda8pxklq4gxw2kxhtm4cgvdvdy64z6agwy88nhuhqcnlm9ySeen on
wss://relay.mostr.pubPublished at
2024-09-11 18:47:54Event JSON
{
"id": "5c56a616a3590195866ce6b103ae15cbddc5dfc1d53869cc947a5388baba0ac8",
"pubkey": "26cad6f140bf86de9c26b7c15419cab1aebdd7086358d26aa2d750e21cf3bf2e",
"created_at": 1726080474,
"kind": 1,
"tags": [
[
"proxy",
"https://social.jvns.ca/users/b0rk/statuses/113120409968129146",
"activitypub"
]
],
"content": "writing about PATH is so funny, it's like\n\n1. just add “PATH=$PATH:/my/dir\" to your shell config, no big deal\n2. ok but uh also you need to worry about path ordering, maybe it has to be `PATH=/my/dir:$PATH` instead\n3. oh also bash sometimes caches PATH lookups, so if that happens then you need to run `rehash`\n4. oh yeah and also if there are spaces in your PATH, then you need to quote it every time you add to it, like `PATH=/my/dir:”$PATH”`\n5. also sometimes commands are aliases or builtins",
"sig": "2682dba4fcd5a1cf6a6dc6d1039e689d0754afb2a4b7a0d01b49009b4c3e90583968eef9d838875ec9271b387098c68aef9681214ee4419bbdd1449e679292c5"
}