{"thread":{"id":"45876","subject":"How to `git status' without scrambling modified with new, etc","startedAt":"2017-05-05T14:03:08Z","lastAt":"2017-05-09T19:42:44Z","messageCount":4,"participants":["Harry Putnam","Ævar Arnfjörð Bjarmason","Samuel Lijin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"318837","messageId":"86bmr7xuy9.fsf@local.lan","threadId":"45876","inReplyTo":null,"subject":"How to `git status' without scrambling modified with new, etc","fromName":"Harry Putnam","fromEmail":"reader@newsguy.com","sentAt":"2017-05-05T14:02:54Z","receivedAt":"2017-05-05T14:03:08Z","isPatch":false,"sender":{"key":"reader@newsguy.com","avatar":null},"body":"This is probably what everyone sees:\n\nWhen I run `git status'; I see  modified and newfiles scrambled together\n\nIs there a trick or technique to make that output show each category\nseparately?\n\nOr do folks just a throw a `sort' in there (git status|sort) and lose\nthe color ouput?\n\n"},{"id":"318839","messageId":"CACBZZX7Q36rFiO9SwBCzM2M3ae=vOPJ2dfaVQ6=geZLgkLAuWA@mail.gmail.com","threadId":"45876","inReplyTo":"86bmr7xuy9.fsf@local.lan","subject":"Re: How to `git status' without scrambling modified with new, etc","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2017-05-05T14:24:50Z","receivedAt":"2017-05-05T14:25:40Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Fri, May 5, 2017 at 4:02 PM, Harry Putnam <reader@newsguy.com> wrote:\n> This is probably what everyone sees:\n>\n> When I run `git status'; I see  modified and newfiles scrambled together\n>\n> Is there a trick or technique to make that output show each category\n> separately?\n>\n> Or do folks just a throw a `sort' in there (git status|sort) and lose\n> the color ouput?\n\nIf you set color.ui=auto it'll disable coloring when it detects that\nthe output isn't to a terminal, i.e. being piped.\n\nIt sounds like you want:\n\n    git -c color.ui=always status --short|sort\n\nBut there's no native option to sort the status output, but that'll do\nit for you.\n"},{"id":"318898","messageId":"CAJZjrdVSX_HB0O_eiQk6bg_UF0=71PNVa1rBwSbpHFCbOrpAOQ@mail.gmail.com","threadId":"45876","inReplyTo":"CACBZZX7Q36rFiO9SwBCzM2M3ae=vOPJ2dfaVQ6=geZLgkLAuWA@mail.gmail.com","subject":"Re: How to `git status' without scrambling modified with new, etc","fromName":"Samuel Lijin","fromEmail":"sxlijin@gmail.com","sentAt":"2017-05-05T21:06:32Z","receivedAt":"2017-05-05T21:07:21Z","isPatch":false,"sender":{"key":"sxlijin@gmail.com","avatar":"https://gravatar.com/avatar/01777bf1eae64e2b4dca97dcac182a6abbcf6fd8cb4d5b8fa33edf9f8cc21746?d=mp&s=160"},"body":"On Fri, May 5, 2017 at 9:24 AM, Ævar Arnfjörð Bjarmason\n<avarab@gmail.com> wrote:\n> On Fri, May 5, 2017 at 4:02 PM, Harry Putnam <reader@newsguy.com> wrote:\n>> This is probably what everyone sees:\n>>\n>> When I run `git status'; I see  modified and newfiles scrambled together\n>>\n>> Is there a trick or technique to make that output show each category\n>> separately?\n\nYou can use `git status -s` and match on the modification type (M\ncorresponds to modified, A to new files). See the man page for more\ndetails on the interface.\n\n>> Or do folks just a throw a `sort' in there (git status|sort) and lose\n>> the color ouput?\n>\n> If you set color.ui=auto it'll disable coloring when it detects that\n> the output isn't to a terminal, i.e. being piped.\n>\n> It sounds like you want:\n>\n>     git -c color.ui=always status --short|sort\n>\n> But there's no native option to sort the status output, but that'll do\n> it for you.\n"},{"id":"319222","messageId":"86k25pkeaj.fsf@local.lan","threadId":"45876","inReplyTo":"CAJZjrdVSX_HB0O_eiQk6bg_UF0=71PNVa1rBwSbpHFCbOrpAOQ@mail.gmail.com","subject":"Re: How to `git status' without scrambling modified with new, etc","fromName":"Harry Putnam","fromEmail":"reader@newsguy.com","sentAt":"2017-05-09T19:42:28Z","receivedAt":"2017-05-09T19:42:44Z","isPatch":false,"sender":{"key":"reader@newsguy.com","avatar":null},"body":"Samuel Lijin <sxlijin@gmail.com> writes:\n\n> You can use `git status -s` and match on the modification type (M\n> corresponds to modified, A to new files). See the man page for more\n> details on the interface.\n\nahh yes.  Just the ticket thanks\n\n"}]}