From: Robert Pluim <rpluim@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: New functions remote-exec-path and remote-executable-find
Date: Mon, 18 Jun 2018 17:59:22 +0200 [thread overview]
Message-ID: <8736xkcch1.fsf@gmail.com> (raw)
In-Reply-To: <87po0oi0qa.fsf@gmx.de> (Michael Albinus's message of "Mon, 18 Jun 2018 17:16:29 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> Hi,
>
> these days I'm working on bug#31704. The point is, that for searching of
> programs, always `exec-path' (a list of local directories) is taken,
> even if the shell runs on a remote host. Therefore, I propose a new
> function `remote-exec-path'. In case of a remote `default-directory',
> the function returns a list of directories which belong to that
> host. Implemented via file name handlers. For a local
> `default-directory', `exec-path' is returned.
>
> And while we are at this, a second new function `remote-executable-find'
> comes to mind. Like `executable-find', it returns the local absolute
> file name of a command, also determined by `default-directory'. This
> function doesn't need file name handlers, it would use
> `remote-exec-path' for its implementation.
>
> I don't need `remote-executable-find' for fixing bug#31704, but I
> remember that such a function has been asked for in the past.
Hmm, is this not what connection-local variables are for?
Robert
next prev parent reply other threads:[~2018-06-18 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 15:16 New functions remote-exec-path and remote-executable-find Michael Albinus
2018-06-18 15:59 ` Robert Pluim [this message]
2018-06-18 16:47 ` Michael Albinus
2018-06-19 1:19 ` Stefan Monnier
2018-06-19 8:16 ` Michael Albinus
2018-06-19 12:52 ` Michael Albinus
2018-07-01 17:27 ` Philipp Stephani
2018-07-01 17:41 ` 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=8736xkcch1.fsf@gmail.com \
--to=rpluim@gmail.com \
--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.