altsem / altsem/gitu

feat req. `git config status.showUntrackedFiles all` and tab to expand on untracked folder

Open
#365 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
2.9k
Forks
164
PR merge metrics
No merged PRs in 30d

Description

I assume this is feature parity with emacs magit.

see shell history below for raw git behavior

% mkdir proj
% cd proj
% git init
Initialized empty Git repository in /private/tmp/proj/.git/
% mkdir subdir
% touch a.txt subdir/b.txt  subdir/c.txt
% git status

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        a.txt
        subdir/

% git config status.showUntrackedFiles all

% git status

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        a.txt
        subdir/b.txt
        subdir/c.txt

emacs magit also respect the showUntrackedFiles all setting

hitting [tab] on the untracked dir will now expand

In the beginning there was darkness

Untracked files (2)
a.txt
subdir/
subdir/b.txt
subdir/c.txt

before setting showUntrackedFiles , emacs magit behaves like gitu where you cannot tab expand on untracked dir

I frequently have to selectively add files under untracked dir.

Is it possible to have tab expand like emacs magit?
Or maybe there are other workarounds?

Thanks

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests. Start by tracing the CLI's handling of git status output and the tab interaction for untracked directories, then check how git config status.showUntrackedFiles all is exposed. Done means untracked files appear individually when configured and tab expands an untracked directory for selective staging.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, rust
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.