Timeline for How do I explicitly and safely force the use of a built-in command in bash
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Feb 16, 2024 at 18:48 | history | edited | G-Man Says 'Reinstate Monica' | CC BY-SA 4.0 |
Fixed punctuation error; improved formatting.
|
| S Feb 16, 2024 at 18:48 | history | suggested | Bangkit Pratama | CC BY-SA 4.0 |
putting oxford comma in answer.
|
| Feb 16, 2024 at 17:30 | review | Suggested edits | |||
| S Feb 16, 2024 at 18:48 | |||||
| Mar 5, 2015 at 12:16 | review | Low quality posts | |||
| Mar 5, 2015 at 12:18 | |||||
| Mar 5, 2015 at 12:13 | comment | added | odc | Damn! And listing defined functions also relies on a builtin. I give up! | |
| Mar 5, 2015 at 12:00 | comment | added | falstro |
sorry, unset() { true; } takes care of that.
|
|
| Mar 5, 2015 at 11:58 | history | answered | odc | CC BY-SA 3.0 |