"Khamenia, Valery" <[EMAIL PROTECTED]> writes: > > I think just smarter C-c C-r would be kind of trade-off here. > > hm, maybe there are some other voices here similar to mine? > It would be easier to discuss the subj.
Within ESS, you've got the ess-thread-eval (similar to ess-chunk-eval), so the guts for cross-chunk evals are there, so the next part would be as you say, making C-c C-r SWeave-aware. An simpler alternative to code would be to allow one to eval-chunk-and-step, stepping through chunks, similar to C-c C-n for stepping through lines. Would this solve the basic problem? 3 x (2 or 3 keystrokes) for 3 chunks. I can't imagine an evaluation which would cross chunks but use only part of chunks (this suggests bad programming design to me), but perhaps you (or others) have an example of when this functionality would be useful? (i.e. actual regions to eval which cross code-chunk boundaries but contain 1 or 2 incomplete code-chunks?). best, -tony -- Anthony Rossini Research Associate Professor [EMAIL PROTECTED] http://www.analytics.washington.edu/ Biomedical and Health Informatics University of Washington Biostatistics, SCHARP/HVTN Fred Hutchinson Cancer Research Center UW (Tu/Th/F): 206-616-7630 FAX=206-543-3461 | Voicemail is unreliable FHCRC (M/W): 206-667-7025 FAX=206-667-4812 | use Email CONFIDENTIALITY NOTICE: This e-mail message and any attachme...{{dropped}} ______________________________________________ [EMAIL PROTECTED] mailing list https://www.stat.math.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide! http://www.R-project.org/posting-guide.html
