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

For some files, the ~ symbol will always be displayed #386

Open
onlycalm opened this issue Nov 12, 2021 · 2 comments
Open

For some files, the ~ symbol will always be displayed #386

onlycalm opened this issue Nov 12, 2021 · 2 comments

Comments

@onlycalm
Copy link

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

@jamessan
Copy link
Collaborator

jamessan commented Dec 5, 2021

Does this only happen if the file is com.h? com is a special device in Windows, so it may be related to that.

The results of :SignifyDebug would be helpful.

@Testspieler09
Copy link

Testspieler09 commented May 22, 2024

I have the same problem with a file named scanner.py. For me it displays "!" which also means modified line. I get

git diff --no-color --no-ext-diff -U0 -- "scanner.py"
=====================================================
diff --git a/scanner.py b/scanner.py
index 161e4e3..eeb9c0e 100644
--- a/scanner.py
+++ b/scanner.py
@@ -1,183 +1,183 @@
-from sys import argv, exit
[...]
+from sys import argv, exit
[...]

from :SignifyDebug.

The file is a fork of another repo and starts to show the "!" on opening the file. Though the fact that the file is forked shouldn't cause the issue. I'm using nvim on Windows but this also shouldn't break it as it works in other git directories.

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