Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Git status highlighting in tree mode #340

Open
notramo opened this issue Jan 16, 2018 · 2 comments
Open

Git status highlighting in tree mode #340

notramo opened this issue Jan 16, 2018 · 2 comments

Comments

@notramo
Copy link

notramo commented Jan 16, 2018

The git status in the output of exa -T --git -l isn't clear enough.
It should highlight the git status of the modified file, but not the parent directories.
It is good to easily see the parent directory of the modified file, so exa should print the modified mark, but it should be printed with a decreased intensity color (e.g. file in blue, parent directories in grey)

For example:
I have a git repo with only one file modified: src/neph/parser.cr
When I run exa -T --git -l, it highlights the git status of the src, and src/neph directory too, although only src/neph/parser.cr should be highlighted (src/neph/parser.cr → blue, src, src/neph → grey).

@kbd
Copy link

kbd commented Feb 1, 2018

Came here to open a similar ticket. Here's an example:

$ .../gittest[git:master]$ exa -T -l --git
... 1 Feb 15:23 -- .
... 1 Feb 15:23 -- ├── js
... 1 Feb 15:23 -- │  ├── ourstuff.js
... 1 Feb 15:23 -- │  └── vendor
... 1 Feb 15:23 -- │     └── 3rdparty.js
... 1 Feb 15:23 -- └── readme.txt
$ .../gittest[git:master]$ git add -f js/vendor/3rdparty.js
$ .../gittest[git:master +]$ exa -T -l --git
... 1 Feb 15:23 N- .
... 1 Feb 15:23 N- ├── js
... 1 Feb 15:23 -- │  ├── ourstuff.js
... 1 Feb 15:23 N- │  └── vendor
... 1 Feb 15:23 N- │     └── 3rdparty.js
... 1 Feb 15:23 -- └── readme.txt

So, the desired behavior is that 'N' should only be on '3rdparty.js', right?

Two more things:

  • exa needs documentation on what the git statuses mean. I had to read the source code to find out definitively what the letters mean.
  • It would be great if there was a U status for "untracked". Dunno if this is reasonable to get from the underlying git library though.

@ariasuni
Copy link
Collaborator

I opened #778 for the documentation issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants