From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Ochs Subject: Re: org mode and eev Date: Fri, 8 Nov 2013 09:36:15 -0200 Message-ID: References: <86mwlg8skv.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11367c1c3fa7db04eaa8cac1 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33238) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VekMM-0004xq-0P for emacs-orgmode@gnu.org; Fri, 08 Nov 2013 06:36:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VekMK-0001wE-49 for emacs-orgmode@gnu.org; Fri, 08 Nov 2013 06:36:17 -0500 Received: from mail-qe0-x22c.google.com ([2607:f8b0:400d:c02::22c]:37885) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VekMJ-0001w9-Ut for emacs-orgmode@gnu.org; Fri, 08 Nov 2013 06:36:16 -0500 Received: by mail-qe0-f44.google.com with SMTP id 6so1762117qeb.3 for ; Fri, 08 Nov 2013 03:36:15 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Alan Schmitt Cc: Sebastien Vauban , Org Mode --001a11367c1c3fa7db04eaa8cac1 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Nov 8, 2013 at 6:29 AM, Alan Schmitt 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 . Try to type 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 instead of typing on them... Cheers! Eduardo --001a11367c1c3fa7db04eaa8cac1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Fri, Nov 8, 2013 at 6:29 AM, Alan Schmitt <alan.schmitt@polytechnique.org> wrote:
Hi Eduardo,

eduardoochs@gmail.com writes:<= br>
> 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<= br> > by both org and eev. Here is a example - just replace each "*&quo= t;
> below with a real char 15.

This was my first question: '*' are not '*' so they w= on'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 glyph= s, 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, st= arting on the
> ;; first one with the "(eepitch-shell)":
>
> * (eepitch-shell)
> * (eepitch-kill)
> * (eepitch-shell)
> #+begin_src sh
> rm -Rv /tmp/eev/
> mkdir =A0/tmp/eev/
> cd =A0 =A0 /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, s= o 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 c= reate
what I call "eepitch blocks", which ar= e the things like these:

* (eepitch-foobar)
<= div class=3D"gmail_extra"> * (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,

=A0=A0(find-eepitch-intro)
for using eev with Org... I'm saying "we&= quot; just because I'll need
help with = (at least) some details!

About ignor= ing the "#+" lines: this can be done by changing
eepitch-comment-regexp, but there a default way that alrea= dy
works, which is to skip the "#+" lines= with <down> instead of
typing <f8= > on them...

=A0 Cheers!
=A0 =A0 Eduardo
--001a11367c1c3fa7db04eaa8cac1--