unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 6923@debbugs.gnu.org
Subject: bug#6923: 24.0.50; Can't load remote elc.gz file using tramp-ftp
Date: Fri, 27 Aug 2010 12:37:25 +0200	[thread overview]
Message-ID: <87vd6w9w9m.fsf@gmx.de> (raw)
In-Reply-To: <b4maao8jxev.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 27 Aug 2010 17:02:32 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> Hi,

Hi,

> This might not be a bug and there might not be a demand either,
> but loading elc.gz file using tramp-ssh succeeds (you don't have
> access to this, sorry):
>
> (let ((load-path (cons "/ssh:jpl.org:~/ftp/pub/tmp/lisp" load-path)))
>   (load "gnus"))
>
> It seems easy to solve.  How about the attached patch?

Your patch looks OK to me. Loading gnus.el.gz via ssh works, because
tramp-ssh preserves the suffix when applying `file-local-copy'. You get
the same result for `ange-ftp-file-local-copy' with your patch.

Maybe we shall extend the docstring of `file-local-copy', saying that
suffixes must be preserved.

> BTW, after starting Emacs, I needed to do tramp-ftp (e.g. dired)
> to the remote site before testing the above two items.  If not,
> I got the error `Variable binding depth exceeds max-specpdl-size'
> for unknown reason.

This is related to Bug#1529 and Bug#5705. Now, after Tramp 2.1.19 has
been released, I plan to reorganize Tramp's packages and their load
dependencies. Shall be fixed then.

> Regards,

Best regards, Michael.





  reply	other threads:[~2010-08-27 10:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27  8:02 bug#6923: 24.0.50; Can't load remote elc.gz file using tramp-ftp Katsumi Yamaoka
2010-08-27 10:37 ` Michael Albinus [this message]
2011-03-03 21:33   ` Glenn Morris
2011-03-04 19:37     ` Michael Albinus
2011-03-06  0:42       ` Glenn Morris
2011-06-27 21:31     ` Chong Yidong
2011-06-27 23:35       ` Katsumi Yamaoka

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=87vd6w9w9m.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=6923@debbugs.gnu.org \
    --cc=yamaoka@jpl.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).