<-
and
<<-< code=""> get typeset by one symbol each.
For a corresponding TeX preamble combining Sweave and listings ,
we provide command
SweaveListingPreparations
.
As for the Rlanguage definition, we allow for different keywordstyles
to typeset symbols from different packages. This is useful to distinguish
mark-up for newly defined functions and alread existing ones.
More specifically, whenever in some Rcode sniplet in some Sweave chunk, there
is some library
or require
command, the corresponding symbols
found by ls()
afterwords in some search()
entry position, are
registered as (printed as 5 items per line)
as a new "higher order" group of keywords by corresponding
\lstdefinestyle{RstyleO}% RstyleO is the current order of Rstyle
{style = RstyleO,
morekeywords=[]{ },%
sensitive=true,%
keywordstyle=[],%
% [ possibly more
morekeywords=[]{ },%
sensitive=true,%
keywordstyle=[],%
% .... ]
}
\lstdefinestyle{Rstyle}{style = RstyleO}
TeX directives in the automatically generated .tex file
where is incremented (resp. gets looked up from
the global, non-exported variable .alreadyDefinedPkgs
in the package
name space) at each instance of
a library
or require
command; an analogue incrementation
present in is done for subsequent (incremental)
redefinitions of style Rstyle ,
which is controlled by the again non-exported global variable
.numberofRequires
. and will
in general differ, as in one call to require
/library
, several
packages may be registered at once.
To this end commands
library
and
require
are masked. See also
lstsetLanguage
,
changeKeywordstyles
,
and setToBeDefinedPkgs
As for the integration of code sniplets from an url (by default, we use
the svn server at R-forge in its most recent version), this can be
useful to stay consistent with the current version of the code without
having to update vignettes all the time. To this end, besides referencing
by line numbers, lstinputSourceFromRForge
also offers
referencing by matching regular expressions. <-<>