Timeline for How to use a variable in a command inside of a bash file
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 6 at 14:43 | comment | added | Stéphane Chazelas |
@GillesQuénot, I try to avoid -v in general as it mangles backslashes (not a problem here).
|
|
| Feb 6 at 14:43 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 |
added 5 characters in body
|
| Feb 6 at 14:43 | comment | added | Gilles Quénot |
Then, awk -v today=xxx looks more the way to go.
|
|
| Feb 6 at 14:42 | comment | added | Stéphane Chazelas |
@GillesQuénot because that's passed as an environment variable to awk (thanks for the edit btw)
|
|
| Feb 6 at 14:42 | history | edited | Gilles Quénot | CC BY-SA 4.0 |
added 5 characters in body
|
| Feb 6 at 14:40 | comment | added | Gilles Quénot |
Why TODAY UPPER CASE? Looks like they are used by system variables, maybe better to not using those?
|
|
| Feb 6 at 14:35 | history | answered | Stéphane Chazelas | CC BY-SA 4.0 |