From: Michael Albinus <michael.albinus@gmx.de>
To: mario@lassnig.net
Cc: help-gnu-emacs@gnu.org
Subject: Re: vc-dir (svn) over tramp
Date: Fri, 21 Jan 2011 11:50:00 +0100 [thread overview]
Message-ID: <87hbd2350n.fsf@gmx.de> (raw)
In-Reply-To: <ihbmdr$7lq$1@speranza.aioe.org> (Mario Lassnig's message of "Fri, 21 Jan 2011 11:16:28 +0100")
Mario Lassnig <mario@lassnig.net> writes:
> Hi,
Hi,
> I'm using tramp (ssh) to work with a remote codebase (svn).
>
> When I chuck vc-dir at the main directory, sometimes it just
> hangs when going through the subdirectories and I get that
> "waiting" thing. Other times, it works as advertised. I can't
> really reproduce it.
>
> What would be a clever way to debug this? The ssh connection
> is definitely stable, that's the one thing I can rule out.
Set tramp-verbose to 6, and check the Tramp debug buffer. Messages with
debug level 6 contain sent commands, and the returned output.
> Cheers,
> Mario
Best regards, Michael.
prev parent reply other threads:[~2011-01-21 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 10:16 vc-dir (svn) over tramp Mario Lassnig
2011-01-21 10:50 ` Michael Albinus [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hbd2350n.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=mario@lassnig.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).