-
Notifications
You must be signed in to change notification settings - Fork 48
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
TRAMP support #57
Comments
Actually I have no idea how TRAMP behaves with respect to this package. Is the grep command running on the local machine or the remote one? |
I'm not sure either. Any idea how I can inspect the default-directory the command is run in? With regular emacs, there is |
How do you know there is a stuck grep process? |
@alphapapa I think I ran into the same issue as @Ambrevar. It looks like emacs will start the process on my local machine (screenshot from htop): If I check the process via
Which would explain the emacs hang and the fans spinning up. 😬 |
Sorry, I have no idea how to deal with TRAMP, and I'm reluctant to complicate the code by adding TRAMP-specific workarounds. I also don't use git over TRAMP, so I don't need to use this package over TRAMP. If someone is interested in contributing patches, I'll be glad to consider them. |
@alphapapa is there any way to at least disable the package on remote repositories? |
I don't know. I don't know how TRAMP works internally. |
Thanks a lot!
|
When running
magit-status
over TRAMP (ssh connection), I notice that there is a complexgrep
command (I use that) hanging in the background eating a whole CPU.I haven't started investigating yet, just letting you know in case you are aware of this and if you have suggestions how to handle this gracefully.
Is it possible to disable magit-todos over TRAMP?
The text was updated successfully, but these errors were encountered: