From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Org-mode Code Blocks Manuscript: Request For Comments
Date: Tue, 07 Dec 2010 23:55:00 +0100 [thread overview]
Message-ID: <80k4jl2ny3.fsf@missioncriticalit.com> (raw)
In-Reply-To: 12760.1291360577@gamaville.dokosmarshall.org
Hi Eric,
Let's see if I'm a good proof-reader. Here are my comments, looking at things
not already said by others:
Page 1 -- "... desirable to mix prose, (add input data?,) code, and
computational results."
Page 3 -- It'd be better not to have commas in front of the Org-mode block in
Figure 1.
Page 9 -- You say that "tags and properties of a node are inherited by its
sub-nodes". I agree for tags, not for properties (at least, by default).
Page 10 -- "Active code blocks are marked with a source line, followed by a
name unique within the document". Why don't you call such "named code blocks"
as in Babel's code base?
BTW, what happens if there is a name clash with other code blocks (in the same
document, or in the LOB)? Though, this is not for your paper...
Page 12 -- When results is set to output, what do you mean by "collected from
STDOUT incrementally"? Not sure about the added value of incrementally...
Page 16 -- I find the name of the code block "ps-to-dot" very badly chosen. PS
makes me think of PostScript, while you mean here Pascal's triangle...
Page 17 -- In the LaTeX ATTR, better use linewidth instead of textwidth. This
is a more secure setting.
Page 18 -- Is the default value of var (1 2 1) compliant with the "pass" table
beneath it?
Side comment -- Wouldn't you use a standard way of handling the acronyms in
LaTeX, so that they're expanded when required, and listed at the end of the
document? Example of such acro: ESS.
For the rest, an excellent document, but not that good (IMHO) for publishing
to a statistics journal. For doing so, I find you'd have to only include R
examples, and show that you can do everything Sweave can do, and even much
more. But I would focus on stats a lot more than it is here.
But, the way it is written, it is much more general, and offers a much widen
view. So, this is excellent, but for another audience.
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-12-07 22:55 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
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 [this message]
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=80k4jl2ny3.fsf@missioncriticalit.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).