From: hymie@lactose.homelinux.net
To: emacs-orgmode@gnu.org
Subject: Re: markup text with leading, trailing spaces
Date: Sat, 14 Feb 2015 12:41:35 -0500 [thread overview]
Message-ID: <E1YMgil-0003Or-Ms@lactose.homelinux.net> (raw)
In-Reply-To: <CAGjSdXqZXT8zp=hmtfduo7-Cs8_mdxUS+PLCqWa4NyMthZMsOA@mail.gmail.com>
"darcamo@gmail.com" writes:
>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
That is a very neat feature. However
>if I can ssh to a server called "myserver"
I cannot.
--hymie! http://lactose.homelinux.net/~hymie hymie@lactose.homelinux.net
>> >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'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.
>>
next prev parent reply other threads:[~2015-02-14 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 17:19 markup text with leading, trailing spaces darcamo
2015-02-14 17:41 ` hymie [this message]
-- 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=E1YMgil-0003Or-Ms@lactose.homelinux.net \
--to=hymie@lactose.homelinux.net \
--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).