From: "Sean O'Halpin" <sean.ohalpin@gmail.com>
To: julia.jacobson@arcor.de
Cc: emacs-orgmode@gnu.org
Subject: Re: Code for feature for showing progress in lisp code for creation of Gantt charts
Date: Sun, 27 May 2012 09:37:49 +0100 [thread overview]
Message-ID: <CAOXM+eUY6idbGJgh80QQA9pANTHsy8Fn-_Td2Yd6nMpGuAoCHQ@mail.gmail.com> (raw)
In-Reply-To: <756350209.602318.1337932165852.JavaMail.ngmail@webmail21.arcor-online.net>
On Fri, May 25, 2012 at 8:49 AM, <julia.jacobson@arcor.de> wrote:
>
> Thanks for your answer. The key-combination C-c C-c unfortunately creates the new additional block of code surrounded by the lines
> #+RESULTS:
> #+begin_latex
> Here's the created LaTeX code
> #+end_latex
> right after the lisp function.
>
> This code block has to be moved just before the line beginning with
> #+ \\draw...
> to get the order right again.
>
> I tried to include the results of the evaluation of the lisp function there by placing
> #+RESULTS: elispgantt
> there (because there's a line saying #+source: elispgantt), but for unknown reasons,
> the results of code evaluation are always placed just after the elispgantt function.
> Any help to fix that is appreciated.
>
Use
#+name: elispgantt
instead of
#+source: elispgantt
I've tried it with your example and it works. AFAIR #+source was
deprecated a while ago.
Regards,
Sean
next prev parent reply other threads:[~2012-05-27 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 15:00 Code for feature for showing progress in lisp code for creation of Gantt charts julia.jacobson
2012-05-24 21:10 ` John Hendy
2012-05-25 7:49 ` julia.jacobson
2012-05-25 13:21 ` John Hendy
2012-05-27 8:37 ` Sean O'Halpin [this message]
2012-08-04 8:01 ` Bastien
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=CAOXM+eUY6idbGJgh80QQA9pANTHsy8Fn-_Td2Yd6nMpGuAoCHQ@mail.gmail.com \
--to=sean.ohalpin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=julia.jacobson@arcor.de \
/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).