From: Michael Albinus <michael.albinus@gmx.de>
To: joakim@verona.se
Cc: help-gnu-emacs@gnu.org
Subject: Re: eshell shortcuts for remote tramp paths?
Date: Wed, 27 May 2015 09:41:50 +0200 [thread overview]
Message-ID: <87mw0qjwld.fsf@gmx.de> (raw)
In-Reply-To: <m3iobeim5z.fsf@exodia.verona.se> (joakim@verona.se's message of "Wed, 27 May 2015 08:12:24 +0200")
joakim@verona.se writes:
Hi Joakim,
> Say that I open an eshell and do:
>
> cd /scp:joakim@192.168.201.58:/home/joakim/nextv
>
> My commands now work remotely. nice.
>
> However, I now want to do ~/bin/lein on the remote. Is there some
> shorcut for this? otherwise I need to type:
> /scp:joakim@192.168.201.58:/home/joakim/bin/lein run
>
> Its the same when trying to refer to the remote root path, /.
- You could use relative paths:
../bin/lein run
- You could add "/home/joakim/bin/" to your remote $PATH env var
- You could try one of the tricks (not tested in eshell) described in
(info "(tramp) Frequently Asked Questions")
Best regards, Michael.
prev parent reply other threads:[~2015-05-27 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 6:12 eshell shortcuts for remote tramp paths? joakim
2015-05-27 7:41 ` 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.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=87mw0qjwld.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=joakim@verona.se \
/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.
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).