Displaying 3 results from an estimated 3 matches for "buildstartupmessage".
2006 May 12
0
New versions for the distr-family of packages, and a new package "startupmsg"
...+conditions: a new sub-condition to 'message' (with a 'types' slot)
is introduced, allowing for scalable startup messages by
condition "catchers" muffleMessage() [for StartupMessage],
onlytypeMessage(), and custom()
additionally:
+ buildStartupMessage: automatically generates a 'complete' start-up message including
*a start-up message of type "version" as to information on the package version
*a start-up message of type "notabene" (optionally)
*a start-up message of "information" m...
2006 May 12
0
New versions for the distr-family of packages, and a new package "startupmsg"
...+conditions: a new sub-condition to 'message' (with a 'types' slot)
is introduced, allowing for scalable startup messages by
condition "catchers" muffleMessage() [for StartupMessage],
onlytypeMessage(), and custom()
additionally:
+ buildStartupMessage: automatically generates a 'complete' start-up message including
*a start-up message of type "version" as to information on the package version
*a start-up message of type "notabene" (optionally)
*a start-up message of "information" m...
2006 Apr 13
4
Wishlist: 'quietly' argument for .onAttach() / .First.lib()
Hi R-devels,
in "Writing R extensions" as well as in the help
to .onAttach(), you mention that one could
use this function to issue a start-up message/banner
for the package.
My little wish for Easter:
a 'quietly'-type argument for .onAttach() / .First.lib()
which is passed through by functions
require() and library() respectively,
and by means of which one could optionally