From: "darcamo@gmail.com" <darcamo@gmail.com>
To: hymie! <hymie@lactose.homelinux.net>, emacs-orgmode@gnu.org
Subject: Re: markup text with leading, trailing spaces
Date: Sat, 14 Feb 2015 17:19:24 +0000 [thread overview]
Message-ID: <CAGjSdXqZXT8zp=hmtfduo7-Cs8_mdxUS+PLCqWa4NyMthZMsOA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3606 bytes --]
Even if you want to run commands in a different computer you can do that
with "C-c C-c" thanks to the ":dir folder" header argument and tramp.
As an example, suppose I have the code block below
#+begin_src sh
hostname
#+end_src
If I run it I get something like
#+RESULTS:
: my_computer_name
However, if if I can ssh to a server called "myserver" I can change the
code block to
#+begin_src sh :dir /myserver:~/
hostname
#+end_src
Now if I run the code block the code is executed in myserver and I get
#+RESULTS:
: myserver_host_name
Combine this with "C-c C-v b" (org-babel-execute-buffer) and you can easily
run many different commands in different machines. It is really great.
Em Sat Feb 14 2015 at 01:09:02, hymie! <hymie@lactose.homelinux.net>
escreveu:
In our last episode, the evil Dr. Lacto had captured our hero,
> jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo), who said:
> >hymie! writes:
> >
> >> I'd like to be able to have a series of commands in my raw org
> >> file that I can copy-n-paste into my shell window. But I also
> >> like to export my org files to HTML so that I can make ePubs and
> >> keep them in my iPad.
> >
> >> And this
> >>
> >> #+BEGIN_SRC
> >> command1
> >> command2
> >> command3
> >> #+END_SRC
> >>
> >> is just IMO ugly.
> >
> >It shouldn't be. Try adding the word "shell" after BEGIN_SRC, so
> >that it fontifies the code correctly (the variable
> >org-src-fontify-natively should be set to t, but that has been
> >default for a while)
>
> It's not that the font is ugly. It's that
> * (in the epub) the source code appears in a box
> * (in the html/epub) it's impossible to tell the difference between two
> different commands and a single command that was too long and word wrapped
> to fit in the box
> * (in the html/epub) I can't have non-monospace comments between/attached
> to/within the code without drawing four or five separate boxes around my
> code
> * (in the org file) For whatever reason, monospace code appears as a
> light-gray font, which is hard to read against a white background. I'm
> sure that can be changed, but I haven't had time to figure it out yet.
>
> >Also, add shell to the loaded babel
> >languages, so that you can execute the code and get the results
> >right away in org:
> >
> >No need for "copy-n-paste", just do C-c C-c where you have your
> >commands.
>
> I think you are making the incorrect assumption that the machine on
> which I maintain my Org files is the same machine that I wish to execute
> commands on.
>
> >Try copying this example into an org file, it should fontify it
> >nicely, both in the org file and in the html exported.
>
> If my commnds were all 8 characters long or less, it would be fine.
> Some of my commands look like this:
>
> adduser username -d /data/chroot/home/username -s /usr/bin/rssh -m -k
> /dev/null -g rssh
>
> useradd -U -G wheel -p '$6$wcMRrkcdGeNHLT5c$0s4qezb00ISmGZSsILOyV/
> WJn3RnuZPkSEknwoSZ22HvbgkBTe4TQwCz/mpG.3zby.1Jwnmtsq1B.uCbyg5l./' username
>
> pssh -x '-q -t -t' -I -i --hosts hosts_linux_rhel6 'sudo -S wget
> puppet/puppet/pub/system_patch.pl -O /usr/local/bin/system_patch.pl' <
> hostnamefile
>
> While I admit that the "useradd" command is an extreme example,
> this becomes horribly ambiguous:
>
> adduser username -d /data/chroot/home/username -s
> /usr/bin/rssh -m -k /dev/null -g rssh
> pssh -x '-q -t -t' -I -i --hosts hosts_linux_rhel6
> 'sudo -S wget puppet/puppet/pub/system_patch.pl -O
> /usr/local/bin/system_patch.pl' < hostnamefile
>
> --hymie! http://lactose.homelinux.net/~hymie
> hymie@lactose.homelinux.net
>
>
>
[-- Attachment #2: Type: text/html, Size: 5226 bytes --]
next reply other threads:[~2015-02-14 17:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 17:19 darcamo [this message]
2015-02-14 17:41 ` markup text with leading, trailing spaces hymie
-- strict thread matches above, loose matches on Subject: below --
2015-02-13 21:29 hymie!
2015-02-13 22:31 ` Jorge A. Alfaro-Murillo
2015-02-14 4:08 ` hymie!
2015-02-14 19:03 ` Jorge A. Alfaro-Murillo
2015-02-15 0:29 ` hymie!
2015-02-15 1:28 ` hymie!
2015-02-23 14:55 ` hymie!
2015-02-23 15:04 ` Rasmus
2015-02-23 17:31 ` hymie!
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='CAGjSdXqZXT8zp=hmtfduo7-Cs8_mdxUS+PLCqWa4NyMthZMsOA@mail.gmail.com' \
--to=darcamo@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=hymie@lactose.homelinux.net \
/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).