Hi Eduardo, eduardoo...@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