From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Schmitt Subject: Re: org mode and eev Date: Fri, 08 Nov 2013 09:29:22 +0100 Message-ID: References: <86mwlg8skv.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46021) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VehRa-0003Kx-5c for emacs-orgmode@gnu.org; Fri, 08 Nov 2013 03:29:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VehRT-0007X8-Gd for emacs-orgmode@gnu.org; Fri, 08 Nov 2013 03:29:30 -0500 Received: from mail2-relais-roc.national.inria.fr ([192.134.164.83]:25821) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VehRT-0007X2-8q for emacs-orgmode@gnu.org; Fri, 08 Nov 2013 03:29:23 -0500 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: Eduardo Ochs Cc: Sebastien Vauban , Org Mode 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