emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [bug?] Tramp tries to open remote file links
Date: Wed, 18 Jun 2014 14:18:46 +0200	[thread overview]
Message-ID: <86y4wuz9zt.fsf@somewhere.org> (raw)
In-Reply-To: 87tx7i1q4g.fsf@gmx.de

Michael Albinus wrote:
> Sebastien Vauban writes:
>> When I just open an Org file that has a link to a remote file, Tramp
>> tries to open it, leading to errors and timeouts when offline, at least.
>>
>> * References
>>
>> Some files of interest:
>>
>> [[file:/me-oHC15RC7JGTNLxjTenLetw@public.gmane.org:papers/current.pdf][paper]]
>>
>> Is this supposed to be normal?  Why does Tramp open the file?
>
> Because Tramp has been instructed so? I suppose, following the above
> link results in

I think we did not understand each other (or did we?) because that's the
thing: I don't follow the link, I just open the file which contains such
a link.

See http://screencast.com/t/aXoxf9D1P.

> (insert-file-contents "/me-oHC15RC7JGTNLxjTenLetw@public.gmane.org:papers/current.pdf")
>
> This is remote file name syntax, and Tramp tries to do its job, using
> the default method "plink". You could avoid Tramp's reaction by a link
> like (untested)
>
> [[file:/:/me-oHC15RC7JGTNLxjTenLetw@public.gmane.org:papers/current.pdf][paper]]
>
> Alternatively, you could choose another file name.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2014-06-18 12:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18  9:08 [bug?] Tramp tries to open remote file links Sebastien Vauban
2014-06-18  9:44 ` Nicolas Richard
2014-06-18 12:29   ` Sebastien Vauban
2014-06-18 13:17     ` Nicolas Richard
2014-06-18 13:25       ` Sebastien Vauban
2014-06-18 13:49         ` Michael Albinus
     [not found]           ` <8761jy1g5f.fsf-Mmb7MZpHnFY@public.gmane.org>
2014-06-18 13:52             ` Sebastien Vauban
2014-06-18 14:03               ` Michael Albinus
2014-06-18 14:20                 ` Sebastien Vauban
2014-06-18 15:11                   ` Michael Albinus
2014-06-18 15:53                     ` Sebastien Vauban
2014-06-18 16:11                       ` Nick Dokos
2014-06-19  8:21                         ` Sebastien Vauban
2014-06-19  9:07                           ` Michael Albinus
2014-06-19 21:59                           ` Andreas Leha
2014-06-20  7:46                             ` Sebastien Vauban
2014-06-20 10:52                               ` Andreas Leha
2014-06-18 14:28         ` Nicolas Richard
2014-06-18 17:25           ` Nicolas Goaziou
2014-06-18 13:26     ` Michael Albinus
2014-06-18 10:14 ` Michael Albinus
2014-06-18 12:18   ` Sebastien Vauban [this message]
2014-06-18 12:49     ` 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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86y4wuz9zt.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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/org-mode.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).