From: Michael Albinus <michael.albinus@gmx.de>
To: Kit-Yan Choi <kit@kychoi.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Patch] org-display-inline-images: Add support for remote images
Date: Sat, 29 Nov 2014 11:50:50 +0100 [thread overview]
Message-ID: <8738922sc5.fsf@gmx.de> (raw)
In-Reply-To: <CAKHbGXWic1MsRjC=7pEsjSgBuYgYEBKg-2Mn8bTAcmEMw4JAzA@mail.gmail.com> (Kit-Yan Choi's message of "Wed, 26 Nov 2014 12:13:15 -0500")
Kit-Yan Choi <kit@kychoi.org> writes:
> But is it theoretically possible to have two remote file paths sharing
> the same local copy file name? i.e. `make-temp-file' generates the
> same temporary file name for two separate calls?
No, never ever. After choosing a random file name, make-temp-file checks
whether there exists already such a file. In case of yes, it chosses
another random file name, and so on.
> As far as org-mode is concerned, and assuming the current stable
> version of tramp, I think there are two options (1) the current
> approach which preserves the path of the remote file and therefore
> avoid unnecessary downloads; however we forgo the capability of
> compression that tramp's file-local-copy offers, (2) use
> `file-local-copy' but risk overwriting (albeit unlikely) downloaded
> local copy; this is possible with or with out a look-up table for
> reusing files.
Again, the risk of overwriting something else does not exist.
> Thanks,
> Kit
Best regards, Michael.
prev parent reply other threads:[~2014-11-29 10:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 4:43 [Patch] org-display-inline-images: Add support for remote images Kit-Yan Choi
2014-11-25 8:32 ` Nicolas Goaziou
2014-11-25 15:15 ` Kit-Yan Choi
2014-11-25 15:23 ` Rasmus
2014-11-25 15:29 ` Kit-Yan Choi
2014-11-25 15:39 ` Michael Albinus
2014-11-25 15:45 ` Kit-Yan Choi
2014-11-25 17:04 ` Michael Albinus
2014-11-26 17:13 ` Kit-Yan Choi
2014-11-29 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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738922sc5.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=kit@kychoi.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).