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

`magit-status` across file systems and mounts #3869

Closed
Alexander-Shukaev opened this issue May 7, 2019 · 3 comments

Comments

Projects
None yet
2 participants
@Alexander-Shukaev
Copy link

commented May 7, 2019

Magit 20190328.1154, Git 2.21.0, Emacs 26.2, gnu/linux

Initialize a Git repository somewhere and maybe add a file. Then create a mount point inside of this repository, i.e. let some other file system be mounted to some nested directory in the repository. You can then add some files from it as well. Observe that git status works everywhere, either outside of that mount point or inside (as long as it is issued in the repository), while magit-status works only outside of the mount point. Inside of the mount point magit-status offers to initialize a new repository. (setenv "GIT_DISCOVERY_ACROSS_FILESYSTEM" "1") did not help.

@tarsius

This comment has been minimized.

Copy link
Member

commented May 8, 2019

(setenv "GIT_DISCOVERY_ACROSS_FILESYSTEM" "1") did not help.

For me it did. Before I did that it didn't work, afterwards it did.

@tarsius tarsius added the unconfirmed label May 8, 2019

@tarsius tarsius closed this May 13, 2019

@Alexander-Shukaev

This comment has been minimized.

Copy link
Author

commented May 20, 2019

The reason may be that I do it via TRAMP. Could you try via e.g. sudo? The oddity is that the environment variable GIT_DISCOVERY_ACROSS_FILESYSTEM is set even in sudo TRAMP buffer, where I invoke magit-status.

@tarsius

This comment has been minimized.

Copy link
Member

commented May 21, 2019

The oddity is that the environment variable GIT_DISCOVERY_ACROSS_FILESYSTEM is set even in sudo TRAMP buffer,

Are you sure about that? Tramp uses tramp-remote-process-environment, not process-environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.