From: "Thomas S. Dye" <tsd@tsdye.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Org-mode Code Blocks Manuscript: Request For Comments
Date: Thu, 2 Dec 2010 15:17:27 -1000 [thread overview]
Message-ID: <4EEEFB5A-DB23-41E0-ADF2-CC1FF820F6DB@tsdye.com> (raw)
In-Reply-To: <87vd3bpy3q.fsf@ucl.ac.uk>
Hi Eric,
On Dec 2, 2010, at 1:13 PM, Eric S Fraga wrote:
> "Eric Schulte" <schulte.eric@gmail.com> writes:
>
>> Hi,
>>
>> Dan Davison, Tom Dye, Carsten Dominik and myself have been working
>> on a
>> paper introducing Org-mode's code block functionality. We plan to
>> submit this paper to the Journal of Statistical Software. As both
>> Org-mode and the code block functionality are largely products of
>> this
>> mailing list community, and in the spirit of an open peer review
>> process
>> we are releasing the current draft of the paper here to solicit your
>> review and comments.
>>
>> Both the .org and .pdf formats of the paper are available at the
>> following locations.
>>
>> http://cs.unm.edu/~eschulte/org-paper/babel.org
>>
>> http://cs.unm.edu/~eschulte/org-paper/babel.pdf
>>
>> Thanks -- Eric
>
> Thanks for giving us early access to this. Very nice article. I
> particularly like the range of examples you have included. They are
> comprehensive (both the languages illustrated and the types of
> problems)
> and each is nicely self-contained. I am a little surprised at the
> choice of journal, mind you... but best of luck in your submission!
> Send us the citation information when it comes out as I'm sure I'll
> have
> plenty of occasions to cite it (e.g. the paper I am currently writing
> relies strongly on org for the generation of results from octave code
> embedded in the document...).
>
> eric
> --
Would you recommend publishing someplace else? We hoped list members
would have opinions on this and welcome comments and suggestions.
All the best,
Tom
next prev parent reply other threads:[~2010-12-03 1:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 19:28 Org-mode Code Blocks Manuscript: Request For Comments Eric Schulte
2010-12-02 19:36 ` Jeff Horn
2010-12-02 23:13 ` Eric S Fraga
2010-12-03 1:17 ` Thomas S. Dye [this message]
2010-12-03 12:26 ` Eric S Fraga
2010-12-03 17:29 ` Thomas S. Dye
2010-12-03 20:07 ` Eric S Fraga
2010-12-03 7:16 ` Nick Dokos
2010-12-07 22:55 ` Sébastien Vauban
2010-12-08 16:33 ` Thomas S. Dye
2010-12-08 19:55 ` Eric Schulte
[not found] ` <87bp4w0zmx.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-12-09 13:22 ` **: " Sébastien Vauban
2010-12-09 14:46 ` Eric Schulte
2010-12-09 19:48 ` Sébastien Vauban
2010-12-08 19:54 ` Eric Schulte
2010-12-03 7:58 ` Detlef Steuer
2010-12-05 6:03 ` Thomas S. Dye
2010-12-06 19:52 ` Charles C. Berry
2010-12-07 0:13 ` Sunny Srivastava
2010-12-07 4:48 ` Charles C. Berry
2010-12-07 14:24 ` Thomas S. Dye
2010-12-07 17:05 ` Charles C. Berry
2010-12-09 7:20 ` Charles C. Berry
2010-12-09 8:07 ` Thomas S. Dye
2010-12-06 2:02 ` Christopher Allan Webber
2010-12-08 19:54 ` Eric Schulte
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=4EEEFB5A-DB23-41E0-ADF2-CC1FF820F6DB@tsdye.com \
--to=tsd@tsdye.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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).