[ESS] 2 things I wish ESS would do
A.J. Rossini
blindglobe at gmail.com
Wed May 7 12:41:33 CEST 2008
(only answering one of Tyler's questions)
On 5/6/08, tyler <tyler.smith at mail.mcgill.ca> wrote:
> David Whiting <david.whiting at ncl.ac.uk> writes:
> Is there a good reason to keep the ess-transcript functions and
> inferior-ess-prompt hidden from ESS[S] mode? Appropriate helper
> functions would be easy to cook up if the these items were available. I
> imagine a single command to collect the current region in the process
> buffer, prompt for the destination buffer, possibly with a default, and
> then paste and clean the kill-ring at point in the destination buffer.
To answer your question: there are reasons, "goodness" being in the
eye of the beholder.
Originally (1994-1996 era), we (at least I) wanted to ensure
workflow/process restrictions on what you could do in a particular
mode, to simplify training.
That has proven to be rather old fashioned and restrictive, as new
workflows/processes for doing statistical activities are
created/desired, as more and more people use this tool.
So refactoring those functions into a general support location would
be a great idea, for reuse by the various modes.
best,
-tony
blindglobe at gmail.com
Muttenz, Switzerland.
"Commit early,commit often, and commit in a repository from which we
can easily roll-back your mistakes" (AJR, 4Jan05).
Drink Coffee: Do stupid things faster with more energy!
More information about the ESS-help
mailing list