search for: rstyle

...ils to use \lstenvironment * individual markup style for base or recommended packages (checked for with new function isBaseOrRecommended()) is distinct now by default (extra color RRecomdcolor) * temporarily changes (like background color) made easier: by new functions + lstdefRstyle to change Rstyle + lstsetRall to change all R-like styles (i.e. Rstyle, Rinstyle, Routstyle, Rcodestyle) * now can specify markup styles for Sinput, Soutput, Scode, separately as Rin, Rout, Rcode * colors now have suffix "color", i.e. Rcomment -> Rcommentcolor,...

...ils to use \lstenvironment * individual markup style for base or recommended packages (checked for with new function isBaseOrRecommended()) is distinct now by default (extra color RRecomdcolor) * temporarily changes (like background color) made easier: by new functions + lstdefRstyle to change Rstyle + lstsetRall to change all R-like styles (i.e. Rstyle, Rinstyle, Routstyle, Rcodestyle) * now can specify markup styles for Sinput, Soutput, Scode, separately as Rin, Rout, Rcode * colors now have suffix "color", i.e. Rcomment -> Rcommentcolor,...

...into line with the advice of the help page for "if". The output looks more like the a randomly selected R file from the R source or the recommended packages. I'm teaching new users that they should study the R source code itself as a guide for programming (http://pj.freefaculty.org/R/Rstyle.pdf). My argument there would go more smoothly if print.function obeyed the "} else {" policy that most of your source code and packages adhere to. We do see r-help questions about the problem that user code can't be run line-by-line, even when it is styled like the print.function()...