Timeline for Bash script for referencing git status output files
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 24 at 18:51 | review | Suggested edits | |||
Jun 24 at 20:20 | |||||
Aug 21, 2017 at 17:27 | comment | added | janos |
@C.Sano cool, didn't know that about export
|
|
Aug 21, 2017 at 15:59 | comment | added | C. Sano | you can replace set with export and it should work in general (referring to when you mentioned set didn't work on yours). | |
Aug 21, 2017 at 15:32 | comment | added | janos | @C.Sano you're right, the empty output needed to be handled. Thanks, and I improved your edit a bit. I'm not sure what you mean by "export" there... | |
S Aug 21, 2017 at 15:29 | history | edited | janos | CC BY-SA 3.0 |
added check for git status -> empty case (the while loop still runs once with an empty string)
|
S Aug 21, 2017 at 15:29 | history | suggested | C. Sano | CC BY-SA 3.0 |
added check for git status -> empty case (the while loop still runs once with an empty string)
|
Aug 21, 2017 at 15:21 | review | Suggested edits | |||
S Aug 21, 2017 at 15:29 | |||||
Aug 21, 2017 at 15:09 | comment | added | C. Sano | wow great! It looks so much cleaner now. Also, regarding the set part, it worked on the computer I was writing this on but didn't work for another. Changing it to export also worked, although I didn't want that because it should really be local. One thing though: this does not handle the case when git status -s is empty (ie: no change), which can be common. I know it doesn't really matter because you can ignore the message, but for completion, I added: if [ "${line}" = "" ] then continue fi at the beginning of the loop | |
Aug 21, 2017 at 15:06 | vote | accept | C. Sano | ||
Aug 19, 2017 at 11:57 | history | answered | janos | CC BY-SA 3.0 |