From: Brett Viren <bv@bnl.gov>
To: David Bjergaard <david.b@duke.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Executing org shell blocks on remote machine over ssh
Date: Tue, 18 Nov 2014 10:43:24 -0500 [thread overview]
Message-ID: <ir4vbmczf8j.fsf@lycastus.phy.bnl.gov> (raw)
In-Reply-To: <874mtxx18q.fsf@duke.edu> (David Bjergaard's message of "Mon, 17 Nov 2014 11:04:05 -0500")
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
David Bjergaard <david.b@duke.edu> writes:
> I use org mode as a lab notebook. I write org-src blocks to keep track
> of tasks I do at the command line, and then I copy paste them into the
> terminal. I would really like to hit "C-c C-c" on the source block and
> have it executed on the remote machine. I know that you can specify
> the remote machine according to [1], however the software I use requires
> a fairly complicated setup to get going.
Is it just complicated, or is it also prohibitively long-running?
If just the former, you could maybe bundle the setup into some shell
script and source it in each of your sh source blocks. Eg:
#+BEGIN_SRC sh :results output :dir /ssh:lycastus:/home/bviren
/bin/pwd
echo $HOSTNAME
ls -l foo.sh
echo "---"
cat foo.sh
echo "---"
source ./foo.sh
echo $FOO
#+END_SRC
#+RESULTS:
: /home/bviren
: lycastus
: -rw-rw-r-- 1 bviren bviren 16 Nov 18 10:27 foo.sh
: ---
: export FOO=bar
:
: ---
: bar
If the setup is purely environmental, and it takes a long time to
perform, maybe you could do the set up once and then cache the resulting
environment using the output of "env".
-Brett.
[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]
next prev parent reply other threads:[~2014-11-18 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 16:04 Executing org shell blocks on remote machine over ssh David Bjergaard
2014-11-17 22:50 ` Myles English
2014-11-18 15:55 ` Andreas Leha
2014-11-18 15:43 ` Brett Viren [this message]
2014-11-18 18:12 ` Ista Zahn
2014-11-18 18:23 ` David Bjergaard
2014-11-18 18:31 ` Ista Zahn
2014-11-18 19:03 ` Brett Viren
2014-11-18 19:52 ` Subhan Michael Tindall
2014-11-18 20:58 ` Brady Trainor
2014-11-18 22:01 ` Andreas Leha
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=ir4vbmczf8j.fsf@lycastus.phy.bnl.gov \
--to=bv@bnl.gov \
--cc=david.b@duke.edu \
--cc=emacs-orgmode@gnu.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).