* How to `git status' without scrambling modified with new, etc
@ 2017-05-05 14:02 Harry Putnam
2017-05-05 14:24 ` Ævar Arnfjörð Bjarmason
0 siblings, 1 reply; 4+ messages in thread
From: Harry Putnam @ 2017-05-05 14:02 UTC (permalink / raw)
To: git
This is probably what everyone sees:
When I run `git status'; I see modified and newfiles scrambled together
Is there a trick or technique to make that output show each category
separately?
Or do folks just a throw a `sort' in there (git status|sort) and lose
the color ouput?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to `git status' without scrambling modified with new, etc
2017-05-05 14:02 How to `git status' without scrambling modified with new, etc Harry Putnam
@ 2017-05-05 14:24 ` Ævar Arnfjörð Bjarmason
2017-05-05 21:06 ` Samuel Lijin
0 siblings, 1 reply; 4+ messages in thread
From: Ævar Arnfjörð Bjarmason @ 2017-05-05 14:24 UTC (permalink / raw)
To: Harry Putnam; +Cc: Git Mailing List
On Fri, May 5, 2017 at 4:02 PM, Harry Putnam <reader@newsguy.com> wrote:
> This is probably what everyone sees:
>
> When I run `git status'; I see modified and newfiles scrambled together
>
> Is there a trick or technique to make that output show each category
> separately?
>
> Or do folks just a throw a `sort' in there (git status|sort) and lose
> the color ouput?
If you set color.ui=auto it'll disable coloring when it detects that
the output isn't to a terminal, i.e. being piped.
It sounds like you want:
git -c color.ui=always status --short|sort
But there's no native option to sort the status output, but that'll do
it for you.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to `git status' without scrambling modified with new, etc
2017-05-05 14:24 ` Ævar Arnfjörð Bjarmason
@ 2017-05-05 21:06 ` Samuel Lijin
2017-05-09 19:42 ` Harry Putnam
0 siblings, 1 reply; 4+ messages in thread
From: Samuel Lijin @ 2017-05-05 21:06 UTC (permalink / raw)
To: Ævar Arnfjörð Bjarmason; +Cc: Harry Putnam, Git Mailing List
On Fri, May 5, 2017 at 9:24 AM, Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> On Fri, May 5, 2017 at 4:02 PM, Harry Putnam <reader@newsguy.com> wrote:
>> This is probably what everyone sees:
>>
>> When I run `git status'; I see modified and newfiles scrambled together
>>
>> Is there a trick or technique to make that output show each category
>> separately?
You can use `git status -s` and match on the modification type (M
corresponds to modified, A to new files). See the man page for more
details on the interface.
>> Or do folks just a throw a `sort' in there (git status|sort) and lose
>> the color ouput?
>
> If you set color.ui=auto it'll disable coloring when it detects that
> the output isn't to a terminal, i.e. being piped.
>
> It sounds like you want:
>
> git -c color.ui=always status --short|sort
>
> But there's no native option to sort the status output, but that'll do
> it for you.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to `git status' without scrambling modified with new, etc
2017-05-05 21:06 ` Samuel Lijin
@ 2017-05-09 19:42 ` Harry Putnam
0 siblings, 0 replies; 4+ messages in thread
From: Harry Putnam @ 2017-05-09 19:42 UTC (permalink / raw)
To: git
Samuel Lijin <sxlijin@gmail.com> writes:
> You can use `git status -s` and match on the modification type (M
> corresponds to modified, A to new files). See the man page for more
> details on the interface.
ahh yes. Just the ticket thanks
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-05-09 19:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-05 14:02 How to `git status' without scrambling modified with new, etc Harry Putnam
2017-05-05 14:24 ` Ævar Arnfjörð Bjarmason
2017-05-05 21:06 ` Samuel Lijin
2017-05-09 19:42 ` Harry Putnam
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).