From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Remote temporary directory
Date: Wed, 27 Jul 2016 14:42:49 +0300 [thread overview]
Message-ID: <70b010b2-ee2c-470b-bfed-7ab37c8de934@gmail.com> (raw)
In-Reply-To: <87k2g7pfmx.fsf_-_@gmx.de>
Another way would be abstracting away the remoteness and creating a
function that makes a temporary file based on some filepath regardless
of whether it's local or not.
In particular case of that bug, you still have to strip tramp method and
host when passing path to git, but in general I think such a function
would work well.
--
Best Regards,
Nikolay Kudryavtsev
next prev parent reply other threads:[~2016-07-27 11:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <acdfa136-1d37-a920-b572-fdd0f6e11257@gmail.com>
[not found] ` <837fch1vmw.fsf@gnu.org>
2016-07-25 18:46 ` bug#23076: 24.5; vc-git: add a new variable for log output coding system Nikolay Kudryavtsev
2016-07-25 19:10 ` Eli Zaretskii
2016-07-26 19:01 ` Michael Albinus
2016-07-27 2:36 ` Eli Zaretskii
2016-07-27 9:57 ` Remote temporary directory (was: bug#23076: 24.5; vc-git: add a new variable for log output coding system) Michael Albinus
2016-07-27 11:42 ` Nikolay Kudryavtsev [this message]
2016-07-27 12:27 ` Remote temporary directory Michael Albinus
2016-07-27 16:09 ` Remote temporary directory (was: bug#23076: 24.5; vc-git: add a new variable for log output coding system) Eli Zaretskii
2016-07-27 16:56 ` Remote temporary directory Michael Albinus
2016-07-27 17:37 ` Eli Zaretskii
2016-07-27 18:14 ` Michael Albinus
2016-07-29 20:15 ` Michael Albinus
2016-07-29 21:02 ` Stefan Monnier
2016-07-31 11:26 ` Michael Albinus
2016-07-31 14:19 ` Stefan Monnier
2016-07-31 14:45 ` Michael Albinus
2016-07-30 6:58 ` Eli Zaretskii
2016-08-07 12:08 ` bug#23076: 24.5; vc-git: add a new variable for log output coding system 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70b010b2-ee2c-470b-bfed-7ab37c8de934@gmail.com \
--to=nikolay.kudryavtsev@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.