Re: tramp: Maximum buffer size exceeded

[Kin Cho <kin@techie.com>]

kai.grossjohann@gmx.net (Kai Großjohann) writes:

> Kin Cho <kin@neoscale.com> writes:
> 
> > tramp (2.0.35) seems to have trouble with large file size.
> >
> > I was trying to copy /large-file (210 Meg) from foobar to a local
> > directory.
> 
> It's a pity.  I didn't think of this optimization.  If you look at
> the function tramp-do-copy-or-rename-file, then you will see that it
> deals with the following special cases:
> 
> * Both are Tramp files.  In that case, I look whether they are from
>   the same user/host/method combo.  If so, I invoke "mv"/"cp" on the
>   remote system directly.  If not, see the last case.
> 
> * Neither are Tramp files.  Error.
> 
> * This is the default case: fetch file into a buffer, then save the
>   buffer.
> 
> I should add another case which looks whether exactly one of them is
> remote and the method is an out of band method.  In that case, I can
> invoke rcp/scp/... directly.
> 
> Want to code this?

I'll take a shot at it.

However, since I don't copy these large files often (may be once
a month), and even then it's easy to manually type the scp
command anyway.  My sense of urgency to work on this will be low.

Speaking of urgency, one thing that comes to mind as being more
urgently needed is to optimize tramp startup connection time.

An idea I had was to cache the little things that tramp sends to
the remote host.  That way, tramp would startup much quicker the
next time it connects to the same host.

-kin