From: Michael Albinus <michael.albinus@gmx.de>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Tramp problems with Emacs 24
Date: Thu, 04 Nov 2010 20:56:09 +0100 [thread overview]
Message-ID: <87r5f0j21y.fsf@gmx.de> (raw)
In-Reply-To: <4CD307CF.3090101@gmail.com> (Suvayu Ali's message of "Thu, 04 Nov 2010 12:21:51 -0700")
Suvayu Ali <fatkasuvayu+linux@gmail.com> 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 tramp-devel@gnu.org. 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.
next prev parent reply other threads:[~2010-11-04 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 19:21 Tramp problems with Emacs 24 Suvayu Ali
2010-11-04 19:56 ` Michael Albinus [this message]
2010-11-04 19:58 ` Suvayu Ali
2010-11-04 20:03 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r5f0j21y.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=fatkasuvayu+linux@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.