From: Eduardo Ochs <eduardoochs@gmail.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: Sebastien Vauban <sva-news@mygooglest.com>,
Org Mode <emacs-orgmode@gnu.org>
Subject: Re: org mode and eev
Date: Fri, 8 Nov 2013 09:36:15 -0200 [thread overview]
Message-ID: <CADs++6hLpvjvwmBhZa8b+96WegGYEkXpqCO1wxrxhRqoHdXrTQ@mail.gmail.com> (raw)
In-Reply-To: <m2bo1vxpnh.fsf@polytechnique.org>
[-- Attachment #1: Type: text/plain, Size: 2537 bytes --]
On Fri, Nov 8, 2013 at 6:29 AM, Alan Schmitt <alan.schmitt@polytechnique.org
> wrote:
> Hi Eduardo,
>
> eduardoochs@gmail.com writes:
>
> > I am the author of eev...
>
> Nice! I knew I had seen you around here ;-)
>
> > How can I help?
>
> Your message already answered one question I had, but I have still one
> pending.
>
> > I still know far less about org-mode than I would like to - maybe
> > because I have been using Emacs in a very idiosyncratic way for ages
> > 8-\ - but it seems trivial to create code blocks that can be executed
> > by both org and eev. Here is a example - just replace each "*"
> > below with a real char 15.
>
> This was my first question: '*' are not '*' so they won't interfere with
> org-mode. This is great. (Quick question: how do I enter such a char 15
> star?)
>
> > ;; 3. Now the "char 15"s will be displayed as red star glyphs, and the
> > ;; code block above can be executed both with org's `C-c C-c' and with
> > ;; eev's <f8>. Try to type <f8> on each line below, starting on the
> > ;; first one with the "(eepitch-shell)":
> >
> > * (eepitch-shell)
> > * (eepitch-kill)
> > * (eepitch-shell)
> > #+begin_src sh
> > rm -Rv /tmp/eev/
> > mkdir /tmp/eev/
> > cd /tmp/eev/
> > wget http://angg.twu.net/eev-current/eev2.tgz
> > tar -xvzf eev2.tgz
> > #+end_src
>
> This works great because '#' is a comment prefix for shell, so the
> begin_src lines won't be processed. I want to use eev with other
> toplevels, and so I cannot rely on this. Is it possible to tweak eepitch
> so that lines starting with #+begin_src and #+end_src are not sent at
> all?
>
> Thanks,
>
> Alan
>
About the char 15s / red stars: I spent many years inserting them
all "by hand" with C-q C-o... Now there is an easier way to create
what I call "eepitch blocks", which are the things like these:
* (eepitch-foobar)
* (eepitch-kill)
* (eepitch-foobar)
The "easier way" is to create an eepitch block for "foobar" as above
is to type "foobar" in a line and then type M-T (meta-shift-t).
Note that all these things are explained here,
(find-eepitch-intro)
http://angg.twu.net/eev-intros/find-eepitch-intro.html
and that we should definitely create a sandboxed tutorial like that
for using eev with Org... I'm saying "we" just because I'll need
help with (at least) some details!
About ignoring the "#+" lines: this can be done by changing
eepitch-comment-regexp, but there a default way that already
works, which is to skip the "#+" lines with <down> instead of
typing <f8> on them...
Cheers!
Eduardo
[-- Attachment #2: Type: text/html, Size: 4438 bytes --]
prev parent reply other threads:[~2013-11-08 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 13:19 org mode and eev Alan Schmitt
2013-11-07 9:33 ` Sebastien Vauban
2013-11-08 2:30 ` Eduardo Ochs
2013-11-08 8:29 ` Alan Schmitt
2013-11-08 11:36 ` Eduardo Ochs [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADs++6hLpvjvwmBhZa8b+96WegGYEkXpqCO1wxrxhRqoHdXrTQ@mail.gmail.com \
--to=eduardoochs@gmail.com \
--cc=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
--cc=sva-news@mygooglest.com \
/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).