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

TRAMP support #57

Closed
Ambrevar opened this issue Oct 25, 2018 · 9 comments
Closed

TRAMP support #57

Ambrevar opened this issue Oct 25, 2018 · 9 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@Ambrevar
Copy link
Contributor

When running magit-status over TRAMP (ssh connection), I notice that there is a complex grep 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?

@alphapapa
Copy link
Owner

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?

@Ambrevar
Copy link
Contributor Author

I'm not sure either. Any idea how I can inspect the default-directory the command is run in?
I'm not familiar with async.el.

With regular emacs, there is call-process for local processes and process-file for processes over TRAMP.

@alphapapa
Copy link
Owner

How do you know there is a stuck grep process?

@alphapapa alphapapa added the WAITING Waiting for response from someone label Nov 22, 2018
@bascht
Copy link

bascht commented Jul 11, 2019

@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):

Screenshot-2019-07-11-165037

If I check the process via ps it looks like it will just append ./ which will fire up rg for my complete home folder:

bascht   17888  7726 99 16:51 pts/8    00:00:07 rg --no-heading --line-number ^(\*+)[[:blank:]]+(DONT|F(?:AIL|IXME)|H(?:ACK|OLD)|KLUDGE|NEXT|OKAY|PROG|T(?:EMP|HEM|ODO)|(?:XXX|\\\?\\\?\\\?)\+)[[:space:]]+(.+)|(?:^|[[:blank:]]+)(DONT|F(?:AIL|IXME)|H(?:ACK|OLD)|KLUDGE|NEXT|OKAY|PROG|T(?:EMP|HEM|ODO)|(?:XXX|\\\?\\\?\\\?)\+)(?:\([^)]+\))?:(?:[[:blank:]]+(.+))? ./

Which would explain the emacs hang and the fans spinning up. 😬
Let me know if I can supply more information to help debugging this.

@alphapapa
Copy link
Owner

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 alphapapa added enhancement New feature or request help wanted Extra attention is needed and removed WAITING Waiting for response from someone labels Jul 12, 2019
@alphapapa alphapapa changed the title Hanging over TRAMP? TRAMP support Jul 12, 2019
@dieggsy
Copy link
Contributor

dieggsy commented Jul 16, 2019

@alphapapa is there any way to at least disable the package on remote repositories?

@alphapapa
Copy link
Owner

I don't know. I don't know how TRAMP works internally.

@alphapapa
Copy link
Owner

@Ambrevar @bascht @dieggsy I added support for TRAMP and it seems to work for me. Note that you may need to configure it for each repository if the remote machine's configuration differs from yours. Please let me know how it works for you.

@Ambrevar
Copy link
Contributor Author

Ambrevar commented Sep 7, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants