[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tramp problems with Emacs 24

From: Michael Albinus
Subject: Re: Tramp problems with Emacs 24
Date: Thu, 04 Nov 2010 20:56:09 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

Suvayu Ali <address@hidden> writes:

> I use TRAMP quite a bit, but lately I have noticed often it fails to
> write the files when I save from time to time with `C-x C-s'.Sometimes
> it hangs trying to save and I have to quit with `C-g' and repeat the
> command. Rarely I even need to kill the buffer and reopen it to go
> back to normal. Also I can't use many of the vc-git-* comands like,
> `(vc-print-log)' or `(vc-print-root-log)'. It gets stuck with a
> message like this,
>> WARNING: terminal is not fully functional
>>  -  (press RETURN)
> The buffer then gets stuck and I have to kill it. On doing so, I get
> prompted like this "Buffer has a running process; kill it? (y or n) y"
> Is anyone else experiencing these issues? I am using emacs with
> `(setq debug-on-error t)', but still I don't see a backtrace when
> these happen. Any ideas how to debug this?

With (setq debug-on-quit t) you get a backtrace when you apply C-g.

The usual way debugging Tramp is to set tramp-verbose to 6. This will
produce a debug buffer, which you can show at address@hidden The
best way to report a Tramp bug is to call "M-x tramp-bug"; this prepares
an email, including information for analysis.

Best regards, Michael.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]