Timeline for Bash function that accepts input from parameter or pipe
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 2, 2020 at 14:47 | answer | added | Stéphane Chazelas | timeline score: 11 | |
| Sep 2, 2020 at 5:24 | history | edited | G-Man Says 'Reinstate Monica' | CC BY-SA 4.0 | Fixed data. |
| Sep 2, 2020 at 0:43 | answer | added | G-Man Says 'Reinstate Monica' | timeline score: 6 | |
| Aug 25, 2020 at 0:35 | answer | added | Mohsen Banan | timeline score: -5 | |
| Jun 19, 2020 at 16:02 | answer | added | kbulgrien | timeline score: 3 | |
| Apr 26, 2020 at 20:12 | comment | added | Pablo A | Probably duplicate on stackoverflow | |
| Jun 9, 2019 at 20:35 | answer | added | TomRoche | timeline score: 6 | |
| Aug 5, 2016 at 22:45 | vote | accept | tyrondis | ||
| Aug 5, 2016 at 22:45 | comment | added | tyrondis | You are right, this was just used as an example, though. | |
| Aug 5, 2016 at 13:47 | comment | added | cas | seems like a pointless function when base64 and bash can do all that anyway. why write a function just to avoid using the -d or --decode option? if you really must have something called b64decode then alias b64decode='base64 --decode'. b64d would be shorter, though and save even more typing. | |
| S Aug 5, 2016 at 5:28 | history | suggested | Sundeep | CC BY-SA 3.0 | code formatting and added tag |
| Aug 5, 2016 at 5:09 | review | Suggested edits | |||
| S Aug 5, 2016 at 5:28 | |||||
| Aug 5, 2016 at 4:36 | answer | added | Sundeep | timeline score: 31 | |
| Aug 5, 2016 at 3:58 | review | First posts | |||
| Aug 5, 2016 at 4:10 | |||||
| Aug 5, 2016 at 3:55 | history | asked | tyrondis | CC BY-SA 3.0 |