Version: 1.0.0 Date: 2025-01-12 Category: under the hood Text: Version: 1.0.0 Date: 2025-01-12 Category: We instantiated a more refined mechanism for startup messages, to avoid Text: Version: 1.0.0 Date: 2025-01-12 Category: unnecessary pkg version updates just triggered by startup messages issuing Text: Version: 1.0.0 Date: 2025-01-12 Category: version information of attached packages upstream, which changes the Text: Version: 1.0.0 Date: 2025-01-12 Category: reference output of the attaching package and hence creates diffs when Text: Version: 1.0.0 Date: 2025-01-12 Category: tested on CRAN Text: Version: 1.0.0 Date: 2025-01-12 Category: Somewhat more detailed, in the prior regime, suppose we had pkgs pkgA and pkgB on Text: Version: 1.0.0 Date: 2025-01-12 Category: CRAN, pkgB importing the NAMESPACE of pkgA via depends, and both pkgs pkgA and pkgB Text: Version: 1.0.0 Date: 2025-01-12 Category: had startup messages including version information, and pkgB used the reference Text: Version: 1.0.0 Date: 2025-01-12 Category: output -Ex.Rout.save as a unit test for pkgB. Then, whenever we submitted an Text: Version: 1.0.0 Date: 2025-01-12 Category: updated version of pkgA to CRAN, we had to also submit a new version of pkgB to CRAN Text: Version: 1.0.0 Date: 2025-01-12 Category: regardless whether we had changed anything in pkgB, because of the changed version Text: Version: 1.0.0 Date: 2025-01-12 Category: information in the startup message of pkgA which showed up in the reference output Text: Version: 1.0.0 Date: 2025-01-12 Category: when pkgA was attached at loading pkgB Text: Version: 1.0.0 Date: 2025-01-12 Category: To avoid this, by default our startup messages no longer issue version information Text: Version: 1.0.0 Date: 2025-01-12 Category: of the attached packages, but --only once per session-- we show a startup message Text: Version: 1.0.0 Date: 2025-01-12 Category: indicating how to show the prior behaviour, i.e., show the version information Text: Version: 1.0.0 Date: 2025-01-12 Category: of attached packages in the startup messages Text: Version: 0.9.7 Date: 2024-08-29 Category: under the hood Text: Version: 0.9.7 Date: 2024-08-29 Category: with the help of K. Hornik identified spurious, platform dependent LF/CR issue Text: Version: 0.9.7 Date: 2024-08-29 Category: and capsulated calls to infoShow() in Rd files by Text: ## IGNORE_RDIFF_BEGIN ## IGNORE_RDIFF_END Version: 0.9.6 Date: 2019-03-11 Category: user-visible CHANGES Text: DESCRIPTION tag SVNRevision changed to VCS/SVNRevision Version: 0.9 Date: 2013-09-13 Category: user-visible CHANGES Text: title changed to title style / capitalization Version: 0.9 Date: 2013-09-13 Category: GENERAL ENHANCEMENTS Text: Version: 0.9 Date: 2013-09-13 Category: under the hood Text: Version: 0.9 Date: 2013-09-13 Category: added .Rbuildignore Text: Version: 0.9 Date: 2013-09-13 Category: BUGFIXES Text: Version: 0.8 Date: 2013-02-07 Category: under the hood: Text: startupmsg gains a namespace Version: 0.8 Date: 2013-02-07 Category: under the hood: Text: added DESCRIPTION tag "ByteCompile" to all our packages Version: 0.8 Date: 2013-02-07 Category: under the hood: Text: updating maintainer email address and URL. Version: 0.8 Date: 2013-02-07 Category: under the hood: Text: deleted no longer needed chm folders Version: 0.7 Date: 2009-11-03 Category: user-visible CHANGES Text: new command TOBEDONE() --- similarly to NEWS() to access TOBEDONE file Version: 0.7 Date: 2009-11-03 Category: GENERAL ENHANCEMENTS Text: added tests/Examples folder with file startupmsg-Ex.Rout.save to have some automatic testing Version: 0.7 Date: 2009-11-03 Category: GENERAL ENHANCEMENTS Text: added field "Encoding: latin1" to all DESCRIPTION files in order to avoid problems with e.g. Windows locale when svn replaces $LastChangedDate Version: 0.7 Date: 2009-11-03 Category: GENERAL ENHANCEMENTS Text: added TOBEDONE (sic!) files for each package (by accident also in trunc; these are empty so far) Version: 0.6 Date: 2009-04-15 Text: Rd-style: + several buglets detected with the fuzzier checking mechanism cf [Rd] More intensive checking of R help files, Prof Brian Ripley, 09.01.2009 10:25) [Rd] Warning: missing text for item ... in \describe? , Prof Brian Ripley, Version: 0.5.3 Date: 2008-11-29 Text: new issuer 'mySMHandler' to cope with long package names and variable "paper" widths acc. to getOption("width") (automatically inserts line breaks...) Version: 0.5.3 Date: 2008-11-29 Text: moved license to LGPL-3 Version: 0.5 Date: 2007-07-27 Text: startup messages are now also of S3-class 'packageStartupMessage' and hence may now also be suppressed by suppressPackageStartupMessages() (from package 'base') Version: 0.4 Date: 2006-11-23 Text: deleted: import "methods" from Namespace Version: 0.4 Date: 2006-11-23 Text: included: argument "VIGNETTE" in function "buildStartupMessage" Version: 0.3 Date: 2006-05-12 Text: inserted references to the mail thread "Wishlist: 'quietly' argument for .onAttach() / .First.lib()" on r-devel, April 2006 into seealso Version: 0.2 Text: abolished: S3 class StartupVersionMessage with corresponding constructor Version: 0.2 Text: abolished: call startupVersionMessage Version: 0.2 Text: abolished: control for linestarter (anyone could do this himself: + the developper using his own SMHandler + the user by specifying a suitable custom restart Version: 0.2 Text: abolished: wrapper onlyversionStartupMessages Version: 0.2 Text: abolished: modified output in startMessage Version: 0.2 Text: instead: extended S3 class StartupMessage by a slot 'type' with corresponding accessor startupType Version: 0.2 Text: instead: onlytypeStartupMessages with an atypes argument to filter out types that are to be shown Version: 0.2 Text: instead: introduction of mystartMessage with a Version: 0.2 Text: instead: startMessage now comes with a type argument Version: 0.2 Text: instead/new: SMHandler argument for mystartupMessage and buildStartupMessage defaulting to mySMHandler Version: 0.2 Text: clarified: code to buildStartupMessage Version: 0.2 Text: new: separation into "general routines" documented in ?"startmsg" and an illustration covering mystartupMessage and buildStartupMessage documented in ?"mystartupMessage" Version: 0.2 Text: new: custom restart (idea: Seth Falcon) Version: 0.1 Text: defined S3 classes StartupMessage, StartupVersionMessage with corresponding constructors Version: 0.1 Text: accessor startupPackage Version: 0.1 Text: wrappers suppressStartupMessages, onlyversionStartupMessages Version: 0.1 Text: calls startupMessage, startupVersionMessage Version: 0.1 Text: utilities readVersionInformation, readURLInformation, pointertoNEWS, infoShow, NEWS Version: 0.1 Text: main function buildStartupMessage (also controllable by options "StartupBanner" resp. "StartupLinestarter")