mhinz / mhinz/vim-signify

For some files, the ~ symbol will always be displayed

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

Nobody has claimed this yet.

Dominant language
Vim Script
Stars
2.7k
Forks
113
PR merge metrics
No merged PRs in 30d

Description

Perform the following operations to reproduce the problem:

  1. Create new files main.c and com.h under the test directory structure. (test/main.c test/com.h)
  2. The content of the document is arbitrary, for example
1
2
3
3
4
5
  1. And then execute the instructions. (git init git add --all `git commit -m "test")
  2. You will see that all lines in com.h display the ~ symbol
    image

It should not display the ~ symbol.The prompt for the main.c file is normal.
I also found similar problems in my other warehouses, some of the file prompt is abnorma.

The following projects reproduce this problem
test.zip

Contributor guide

Open the contributing guide

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

Reproduce the issue with test/main.c and test/com.h, then run the listed git init, git add --all, and git commit commands. Start by tracing how vim-signify assigns signs to these files and compare the behavior for main.c and com.h. Done means com.h no longer shows persistent ~ signs while the normal prompt for main.c remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, vim
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.