I think one of my package is interacting wrongly with TRAMP and it is too often freezing. It is difficult to debug as it freezes totally and quite annoying as I cannot interrupt with C-g. Are there options to run tramp in a way it does not collapse the whole emacs? I could then try to guess which package interact with it by deactivating/activating them…

It seems to work properly if I open emacs with emacs -Q

  • madnificent@lemmy.world
    2·
    18 days ago

    I did not receive a ping because it was a nested comment (TIL)

    I tend to start digging into the source (with M-. to jump to definitions and M-, to pop back). I also tend to break, press c to continue, then break again and see if I’m still in the same spot. I don’t see much wrong with this. It looks like you’re opening a file on a remote host and it seems to be rendering these files. Perhaps that always happens.

    I do see an advice dired-details-hide. I vaguely recall there being an issue with something with pretty dired (but I think that was with all-the-icons).

    It could also be that tramp’s connection broke. Then call tramp-cleanup-this-connection. Something else is probably going haywire, but using ssh’s ControlMaster and reusing the sockets can help with slowdowns then. Using tramp is always going to be slower due to the connection, yet if something freezes it’s probably a package interfering and here possibly fontification.