| 19 Dec 2025 |
 lewo | Meme en faisant ce genre de chose:
#! /usr/bin/env awk
#! awk bla bla...
| 11:14:37 |
| lewo | * Meme en faisant ce genre de chose?
#! /usr/bin/env awk
#! awk bla bla...
| 11:15:05 |
| lewo | * Meme en faisant ce genre de chose?
#! /usr/bin/env awk
#! awk -bla -bla
| 11:16:37 |
 Jo.Blade | c'est quoi cette syntaxe ? | 12:14:12 |
| Jo.Blade | parce que moi il me semble que t'es obligé d'utiliser awk -f pour un shebang d'un script | 12:14:36 |
 immae | ça ressemble à une tentative d’imitation de ce qu’on peut faire avec nix, mais je ne crois pas que awk ait ce genre de mécanisme?
| 12:20:43 |
 bew | I'm not sure how standard it is, but env has -S option that allows more that 2-3 params on the shebang, so #!/usr/bin/env -C awk -f should work 🤔 | 12:23:30 |
| bew | * I'm not sure how standard it is, but env has -S option that allows more that 2-3 params on the shebang, so #!/usr/bin/env -S awk -f should work 🤔 | 12:23:43 |
| immae | It should work but I regularly get issues with this syntax where the /usr/bin/env doesn’t know about this -S
| 12:24:20 |
| immae | The easiest is probably to stick with /usr/bin/env bash and call awk in the bash script ;)
| 12:25:21 |
| immae | (you probably lose proper syntax highlight but you’re sure that it works for everyone :p )
| 12:26:09 |
