APTITUDE(8) Command-line reference APTITUDE(8) NAME aptitude - high-level interface to the package manager SYNOPSIS aptitude [<options>...] {autoclean | clean | forget-new | keep-all | update} aptitude [<options>...] {full-upgrade | safe-upgrade} [<packages>...] aptitude [<options>...] {build-dep | build-depends | changelog | download | forbid-version | hold | install | markauto | purge | reinstall | remove | show | unhold | unmarkauto | versions} <packages>... aptitude extract-cache-subset <output-directory> <packages>... aptitude [<options>...] search <patterns>... aptitude [<options>...] {add-user-tag | remove-user-tag} <tag> <packages>... aptitude [<options>...] {why | why-not} [<patterns>...] <package> aptitude [-S <fname>] [--autoclean-on-startup | --clean-on-startup | -i | -u] aptitude help DESCRIPTION aptitude is a text-based interface to the Debian GNU/Linux package system. It allows the user to view the list of packages and to perform package management tasks such as installing, upgrading, and removing packages. Actions may be performed from a visual interface or from the command-line. COMMAND-LINE ACTIONS The first argument which does not begin with a hyphen (“-”) is considered to be an action that the program should perform. If an action is not specified on the command-line, aptitude will start up in visual mode. The following actions are available: install Install one or more packages. The packages should be listed after the “install” command; if a package name contains a tilde character (“~”) or a question mark (“?”), it will be treated as a search pattern and every package matching the pattern will be installed (see the section “Search Patterns” in the aptitude reference manual). To select a particular version of the package, append “=<version>” to the package name: for instance, “aptitude install apt=0.3.1”. Similarly, to select a package from a particular archive, append “/<archive>” to the package name: for instance, “aptitude install apt/experimental”. You cannot specify both an archive and a version for a package. Not every package listed on the command line has to be installed; you can tell aptitude to do something different with a package by appending an “override specifier” to the name of the package. For example, aptitude remove wesnoth+ will install wesnoth, not remove it. The following override specifiers are available: <package>+ Install <package>. <package>+M Install <package> and immediately mark it as automatically installed (note that if nothing depends on <package>, this will cause it to be immediately removed). <package>- Remove <package>. <package>_ Purge <package>: remove it and all its associated configuration and data files. <package>= Place <package> on hold: cancel any active installation, upgrade, or removal, and prevent this package from being automatically upgraded in the future. <package>: Keep <package> at its current version: cancel any installation, removal, or upgrade. Unlike “hold” (above) this does not prevent automatic upgrades in the future. <package>&M Mark <package> as having been automatically installed. <package>&m Mark <package> as having been manually installed. As a special case, “install” with no arguments will act on any stored/pending actions. Note Once you enter Y at the final confirmation prompt, the “install” command will modify aptitude's stored information about what actions to perform. Therefore, if you issue (e.g.) the command “aptitude install foo bar” and then abort the installation once aptitude has started downloading and installing packages, you will need to run “aptitude remove foo bar” to cancel that order. remove, purge, hold, unhold, keep, reinstall These commands are the same as “install”, but apply the named action to all packages given on the command line for which it is not overridden. The difference between hold and keep is that hold will cause a package to be ignored by future safe-upgrade or full-upgrade commands, while keep merely cancels any scheduled actions on the package. unhold will allow a package to be upgraded by future safe-upgrade or full-upgrade commands, without otherwise altering its state. For instance, “aptitude remove '~ndeity'” will remove all packages whose name contains “deity”. markauto, unmarkauto Mark packages as automatically installed or manually installed, respectively. Packages are specified in exactly the same way as for the “install” command. For instance, “aptitude markauto '~slibs'” will mark all packages in the “libs” section as having been automatically installed. For more information on automatically installed packages, see the section “Managing Automatically Installed Packages” in the aptitude reference manual. build-depends, build-dep Satisfy the build-dependencies of a package. Each package name may be a source package, in which case the build dependencies of that source package are installed; otherwise, binary packages are found in the same way as for the “install” command, and the build-dependencies of the source packages that build those binary packages are satisfied. If the command-line parameter --arch-only is present, only architecture-dependent build dependencies (i.e., not Build-Depends-Indep or Build-Conflicts-Indep) will be obeyed. forbid-version Forbid a package from being upgraded to a particular version. This will prevent aptitude from automatically upgrading to this version, but will allow automatic upgrades to future versions. By default, aptitude will select the version to which the package would normally be upgraded; you may override this selection by appending “=<version>” to the package name: for instance, “aptitude forbid-version vim=1.2.3.broken-4”. This command is useful for avoiding broken versions of packages without having to set and clear manual holds. If you decide you really want the forbidden version after all, “aptitude install <package>” will remove the ban. update Updates the list of available packages from the apt sources (this is equivalent to “apt-get update”) safe-upgrade Upgrades installed packages to their most recent version. Installed packages will not be removed unless they are unused (see the section “Managing Automatically Installed Packages” in the aptitude reference manual). Packages which are not currently installed may be installed to resolve dependencies unless the --no-new-installs command-line option is supplied. If no <package>s are listed on the command line, aptitude will attempt to upgrade every package that can be upgraded. Otherwise, aptitude will attempt to upgrade only the packages which it is instructed to upgrade. The <package>s can be extended with suffixes in the same manner as arguments to aptitude install, so you can also give additional instructions to aptitude here; for instance, aptitude safe-upgrade bash dash- will attempt to upgrade the bash package and remove the dash package. It is sometimes necessary to remove one package in order to upgrade another; this command is not able to upgrade packages in such situations. Use the full-upgrade command to upgrade as many packages as possible. full-upgrade Upgrades installed packages to their most recent version, removing or installing packages as necessary. This command is less conservative than safe-upgrade and thus more likely to perform unwanted actions. However, it is capable of upgrading packages that safe-upgrade cannot upgrade. If no <package>s are listed on the command line, aptitude will attempt to upgrade every package that can be upgraded. Otherwise, aptitude will attempt to upgrade only the packages which it is instructed to upgrade. The <package>s can be extended with suffixes in the same manner as arguments to aptitude install, so you can also give additional instructions to aptitude here; for instance, aptitude full-upgrade bash dash- will attempt to upgrade the bash package and remove the dash package. Note This command was originally named dist-upgrade for historical reasons, and aptitude still recognizes dist-upgrade as a synonym for full-upgrade. keep-all Cancels all scheduled actions on all packages; any packages whose sticky state indicates an installation, removal, or upgrade will have this sticky state cleared. forget-new Forgets all internal information about what packages are “new” (equivalent to pressing “f” when in visual mode). search Searches for packages matching one of the patterns supplied on the command line. All packages which match any of the given patterns will be displayed; for instance, “aptitude search '~N' edit” will list all “new” packages and all packages whose name contains “edit”. For more information on search patterns, see the section “Search Patterns” in the aptitude reference manual. Note In the example above, “aptitude search '~N' edit” has two arguments after search and thus is searching for two patterns: “~N” and “edit”. As described in the search pattern reference, a single pattern composed of two sub-patterns separated by a space (such as “~N edit”) matches only if both patterns match. Thus, the command “aptitude search '~N edit'” will only show “new” packages whose name contains “edit”. Unless you pass the -F option, the output of aptitude search will look something like this: i apt - Advanced front-end for dpkg pi apt-build - frontend to apt to build, optimize and in cp apt-file - APT package searching utility -- command- ihA raptor-utils - Raptor RDF Parser utilities Each search result is listed on a separate line. The first character of each line indicates the current state of the package: the most common states are p, meaning that no trace of the package exists on the system, c, meaning that the package was deleted but its configuration files remain on the system, i, meaning that the package is installed, and v, meaning that the package is virtual. The second character indicates the stored action (if any; otherwise a blank space is displayed) to be performed on the package, with the most common actions being i, meaning that the package will be installed, d, meaning that the package will be deleted, and p, meaning that the package and its configuration files will be removed. If the third character is A, the package was automatically installed. For a complete list of the possible state and action flags, see the section “Accessing Package Information” in the aptitude reference guide. To customize the output of search, see the command-line options -F and --sort. show Displays detailed information about one or more packages, listed following the search command. If a package name contains a tilde character (“~”) or a question mark (“?”), it will be treated as a search pattern and all matching packages will be displayed (see the section “Search Patterns” in the aptitude reference manual). If the verbosity level is 1 or greater (i.e., at least one -v is present on the command-line), information about all versions of the package is displayed. Otherwise, information about the “candidate version” (the version that “aptitude install” would download) is displayed. You can display information about a different version of the package by appending =<version> to the package name; you can display the version from a particular archive or release by appending /<archive> or /<release> to the package name: for instance, /unstable or /sid. If either of these is present, then only the version you request will be displayed, regardless of the verbosity level. If the verbosity level is 1 or greater, the package's architecture, compressed size, filename, and md5sum fields will be displayed. If the verbosity level is 2 or greater, the select version or versions will be displayed once for each archive in which they are found. versions Displays the versions of the packages listed on the command-line. $ aptitude versions wesnoth p 1:1.4.5-1 100 p 1:1.6.5-1 unstable 500 p 1:1.7.14-1 experimental 1 Each version is listed on a separate line. The leftmost three characters indicate the current state, planned state (if any), and whether the package was automatically installed; for more information on their meanings, see the documentation of aptitude search. To the right of the version number you can find the releases from which the version is available, and the pin priority of the version. If a package name contains a tilde character (“~”) or a question mark (“?”), it will be treated as a search pattern and all matching versions will be displayed (see the section “Search Patterns” in the aptitude reference manual). This means that, for instance, aptitude versions '~i' will display all the versions that are currently installed on the system and nothing else, not even other versions of the same packages. $ aptitude versions '~nexim4-daemon-light' Package exim4-daemon-light: i 4.71-3 100 p 4.71-4 unstable 500 Package exim4-daemon-light-dbg: p 4.71-4 unstable 500 If the input is a search pattern, or if more than one package's versions are to be displayed, aptitude will automatically group the output by package, as shown above. You can disable this via --group-by=none, in which case aptitude will display a single list of all the versions that were found and automatically include the package name in each output line: $ aptitude versions --group-by=none '~nexim4-daemon-light' i exim4-daemon-light 4.71-3 100 p exim4-daemon-light 4.71-4 unstable 500 p exim4-daemon-light-dbg 4.71-4 unstable 500 To disable the package name, pass --show-package-names=never: $ aptitude versions --show-package-names=never --group-by=none '~nexim4-daemon-light' i 4.71-3 100 p 4.71-4 unstable 500 p 4.71-4 unstable 500 In addition to the above options, the information printed for each version can be controlled by the command-line option -F. The order in which versions are displayed can be controlled by the command-line option --sort. To prevent aptitude from formatting the output into columns, use --disable-columns. add-user-tag, remove-user-tag Adds a user tag to or removes a user tag from the selected group of packages. If a package name contains a tilde (“~”) or question mark (“?”), it is treated as a search pattern and the tag is added to or removed from all the packages that match the pattern (see the section “Search Patterns” in the aptitude reference manual). User tags are arbitrary strings associated with a package. They can be used with the ?user-tag(<tag>) search term, which will select all the packages that have a user tag matching <tag>. why, why-not Explains the reason that a particular package should or cannot be installed on the system. This command searches for packages that require or conflict with the given package. It displays a sequence of dependencies leading to the target package, along with a note indicating the installed state of each package in the dependency chain: $ aptitude why kdepim i nautilus-data Recommends nautilus i A nautilus Recommends desktop-base (>= 0.2) i A desktop-base Suggests gnome | kde | xfce4 | wmaker p kde Depends kdepim (>= 4:3.4.3) The command why finds a dependency chain that installs the package named on the command line, as above. Note that the dependency that aptitude produced in this case is only a suggestion. This is because no package currently installed on this computer depends on or recommends the kdepim package; if a stronger dependency were available, aptitude would have displayed it. In contrast, why-not finds a dependency chain leading to a conflict with the target package: $ aptitude why-not textopo i ocaml-core Depends ocamlweb i A ocamlweb Depends tetex-extra | texlive-latex-extra i A texlive-latex-extra Conflicts textopo If one or more <pattern>s are present, then aptitude will begin its search at these patterns; that is, the first package in the chain it prints will be a package matching the pattern in question. The patterns are considered to be package names unless they contain a tilde character (“~”) or a question mark (“?”), in which case they are treated as search patterns (see the section “Search Patterns” in the aptitude reference manual). If no patterns are present, then aptitude will search for dependency chains beginning at manually installed packages. This effectively shows the packages that have caused or would cause a given package to be installed. Note aptitude why does not perform full dependency resolution; it only displays direct relationships between packages. For instance, if A requires B, C requires D, and B and C conflict, “aptitude why-not D” will not produce the answer “A depends on B, B conflicts with C, and D depends on C”. By default aptitude outputs only the “most installed, strongest, tightest, shortest” dependency chain. That is, it looks for a chain that only contains packages which are installed or will be installed; it looks for the strongest possible dependencies under that restriction; it looks for chains that avoid ORed dependencies and Provides; and it looks for the shortest dependency chain meeting those criteria. These rules are progressively weakened until a match is found. If the verbosity level is 1 or more, then all the explanations aptitude can find will be displayed, in inverse order of relevance. If the verbosity level is 2 or more, a truly excessive amount of debugging information will be printed to standard output. This command returns 0 if successful, 1 if no explanation could be constructed, and -1 if an error occurred. clean Removes all previously downloaded .deb files from the package cache directory (usually /var/cache/apt/archives). autoclean Removes any cached packages which can no longer be downloaded. This allows you to prevent a cache from growing out of control over time without completely emptying it. changelog Downloads and displays the Debian changelog for each of the given source or binary packages. By default, the changelog for the version which would be installed with “aptitude install” is downloaded. You can select a particular version of a package by appending =<version> to the package name; you can select the version from a particular archive or release by appending /<archive> or /<release> to the package name (for instance, /unstable or /sid). download Downloads the .deb file for the given package to the current directory. If a package name contains a tilde character (“~”) or a question mark (“?”), it will be treated as a search pattern and all the matching packages will be downloaded (see the section “Search Patterns” in the aptitude reference manual). By default, the version which would be installed with “aptitude install” is downloaded. You can select a particular version of a package by appending =<version> to the package name; you can select the version from a particular archive or release by appending /<archive> or /<release> to the package name (for instance: /unstable or /sid). extract-cache-subset Copy the apt configuration directory (/etc/apt) and a subset of the package database to the specified directory. If no packages are listed, the entire package database is copied; otherwise only the entries corresponding to the named packages are copied. Each package name may be a search pattern, and all the packages matching that pattern will be selected (see the section “Search Patterns” in the aptitude reference manual). Any existing package database files in the output directory will be overwritten. Dependencies in binary package stanzas will be rewritten to remove references to packages not in the selected set. help Displays a brief summary of the available commands and options. OPTIONS The following options may be used to modify the behavior of the actions described above. Note that while all options will be accepted for all commands, some options don't apply to particular commands and will be ignored by those commands. --add-user-tag <tag> For full-upgrade, safe-upgrade, forbid-version, hold, install, keep-all, markauto, unmarkauto, purge, reinstall, remove, unhold, and unmarkauto: add the user tag <tag> to all packages that are installed, removed, or upgraded by this command as if with the add-user-tag command. --add-user-tag-to <tag>,<pattern> For full-upgrade, safe-upgrade forbid-version, hold, install, keep-all, markauto, unmarkauto, purge, reinstall, remove, unhold, and unmarkauto: add the user tag <tag> to all packages that match <pattern> as if with the add-user-tag command. The pattern is a search pattern as described in the section “Search Patterns” in the aptitude reference manual. For instance, aptitude safe-upgrade --add-user-tag-to "new-installs,?action(install)" will add the tag new-installs to all the packages installed by the safe-upgrade command. --allow-new-upgrades When the safe resolver is being used (i.e., --safe-resolver was passed, the action is safe-upgrade, or Aptitude::Always-Use-Safe-Resolver is set to true), allow the dependency resolver to install upgrades for packages regardless of the value of Aptitude::Safe-Resolver::No-New-Upgrades. --allow-new-installs Allow the safe-upgrade command to install new packages; when the safe resolver is being used (i.e., --safe-resolver was passed, the action is safe-upgrade, or Aptitude::Always-Use-Safe-Resolver is set to true), allow the dependency resolver to install new packages. This option takes effect regardless of the value of Aptitude::Safe-Resolver::No-New-Installs. --allow-untrusted Install packages from untrusted sources without prompting. You should only use this if you know what you are doing, as it could easily compromise your system's security. --disable-columns This option causes aptitude search and aptitude versions to output their results without any special formatting. In particular: normally aptitude will add whitespace or truncate search results in an attempt to fit its results into vertical “columns”. With this flag, each line will be formed by replacing any format escapes in the format string with the corresponding text; column widths will be ignored. For instance, the first few lines of output from “aptitude search -F '%p %V' --disable-columns libedataserver” might be: disksearch 1.2.1-3 hp-search-mac 0.1.3 libbsearch-ruby 1.5-5 libbsearch-ruby1.8 1.5-5 libclass-dbi-abstractsearch-perl 0.07-2 libdbix-fulltextsearch-perl 0.73-10 As in the above example, --disable-columns is often useful in combination with a custom display format set using the command-line option -F. This corresponds to the configuration option Aptitude::CmdLine::Disable-Columns. -D, --show-deps For commands that will install or remove packages (install, full-upgrade, etc), show brief explanations of automatic installations and removals. This corresponds to the configuration option Aptitude::CmdLine::Show-Deps. -d, --download-only Download packages to the package cache as necessary, but do not install or remove anything. By default, the package cache is stored in /var/cache/apt/archives. This corresponds to the configuration option Aptitude::CmdLine::Download-Only. -F <format>, --display-format <format> Specify the format which should be used to display output from the search and versions commands. For instance, passing “%p %V %v” for <format> will display a package's name, followed by its currently installed version and its available version (see the section “Customizing how packages are displayed” in the aptitude reference manual for more information). The command-line option --disable-columns is often useful in combination with -F. For search, this corresponds to the configuration option Aptitude::CmdLine::Package-Display-Format; for versions, this corresponds to the configuration option Aptitude::CmdLine::Version-Display-Format. -f Try hard to fix the dependencies of broken packages, even if it means ignoring the actions requested on the command line. This corresponds to the configuration item Aptitude::CmdLine::Fix-Broken. --full-resolver When package dependency problems are encountered, use the default “full” resolver to solve them. Unlike the “safe” resolver activated by --safe-resolver, the full resolver will happily remove packages to fulfill dependencies. It can resolve more situations than the safe algorithm, but its solutions are more likely to be undesirable. This option can be used to force the use of the full resolver even when Aptitude::Always-Use-Safe-Resolver is true. The safe-upgrade command never uses the full resolver and does not accept the --full-resolver option. --group-by <grouping-mode> Control how the versions command groups its output. The following values are recognized: · archive to group packages by the archive they occur in (“stable”, “unstable”, etc). If a package occurs in several archives, it will be displayed in each of them. · auto to group versions by their package unless there is exactly one argument and it is not a search pattern. · none to display all the versions in a single list without any grouping. · package to group versions by their package. · source-package to group versions by their source package. · source-version to group versions by their source package and source version. This corresponds to the configuration option Aptitude::CmdLine::Versions-Group-By. -h, --help Display a brief help message. Identical to the help action. --log-file=<file> If <file> is a nonempty string, log messages will be written to it, except that if <file> is “-”, the messages will be written to standard output instead. If this option appears multiple times, the last occurrence is the one that will take effect. This does not affect the log of installations that aptitude has performed (/var/log/aptitude); the log messages written using this configuration include internal program events, errors, and debugging messages. See the command-line option --log-level to get more control over what gets logged. This corresponds to the configuration option Aptitude::Logging::File. --log-level=<level>, --log-level=<category>:<level> --log-level=<level> causes aptitude to only log messages whose level is <level> or higher. For instance, setting the log level to error will cause only messages at the log levels error and fatal to be displayed; all others will be hidden. Valid log levels (in descending order) are off, fatal, error, warn, info, debug, and trace. The default log level is warn. --log-level=<category>:<level> causes messages in <category> to only be logged if their level is <level> or higher. --log-level may appear multiple times on the command line; the most specific setting is the one that takes effect, so if you pass --log-level=aptitude.resolver:fatal and --log-level=aptitude.resolver.hints.match:trace, then messages in aptitude.resolver.hints.parse will only be printed if their level is fatal, but all messages in aptitude.resolver.hints.match will be printed. If you set the level of the same category two or more times, the last setting is the one that will take effect. This does not affect the log of installations that aptitude has performed (/var/log/aptitude); the log messages written using this configuration include internal program events, errors, and debugging messages. See the command-line option --log-file to change where log messages go. This corresponds to the configuration group Aptitude::Logging::Levels. --log-resolver Set some standard log levels related to the resolver, to produce logging output suitable for processing with automated tools. This is equivalent to the command-line options --log-level=aptitude.resolver.search:trace --log-level=aptitude.resolver.search.tiers:info. --no-new-installs Prevent safe-upgrade from installing any new packages; when the safe resolver is being used (i.e., --safe-resolver was passed or Aptitude::Always-Use-Safe-Resolver is set to true), forbid the dependency resolver from installing new packages. This option takes effect regardless of the value of Aptitude::Safe-Resolver::No-New-Installs. This mimics the historical behavior of apt-get upgrade. --no-new-upgrades When the safe resolver is being used (i.e., --safe-resolver was passed or Aptitude::Always-Use-Safe-Resolver is set to true), forbid the dependency resolver from installing upgrades for packages regardless of the value of Aptitude::Safe-Resolver::No-New-Upgrades. --no-show-resolver-actions Do not display the actions performed by the “safe” resolver, overriding any configuration option or earlier --show-resolver-actions. -O <order>, --sort <order> Specify the order in which output from the search and versions commands should be displayed. For instance, passing “installsize” for <order> will list packages in order according to their size when installed (see the section “Customizing how packages are sorted” in the aptitude reference manual for more information). The default sort order is name,version. -o <key>=<value> Set a configuration file option directly; for instance, use -o Aptitude::Log=/tmp/my-log to log aptitude's actions to /tmp/my-log. For more information on configuration file options, see the section “Configuration file reference” in the aptitude reference manual. -P, --prompt Always display a prompt before downloading, installing or removing packages, even when no actions other than those explicitly requested will be performed. This corresponds to the configuration option Aptitude::CmdLine::Always-Prompt. --purge-unused If Aptitude::Delete-Unused is set to “true” (its default), then in addition to removing each package that is no longer required by any installed package, aptitude will also purge them, removing their configuration files and perhaps other important data. For more information about which packages are considered to be “unused”, see the section “Managing Automatically Installed Packages” in the aptitude reference manual. THIS OPTION CAN CAUSE DATA LOSS!  This corresponds to the configuration option Aptitude::Purge-Unused. -q[=<n>], --quiet[=<n>] Suppress all incremental progress indicators, thus making the output loggable. This may be supplied multiple times to make the program quieter, but unlike apt-get, aptitude does not enable -y when -q is supplied more than once. The optional =<n> may be used to directly set the amount of quietness (for instance, to override a setting in /etc/apt/apt.conf); it causes the program to behave as if -q had been passed exactly <n> times. -R, --without-recommends Do not treat recommendations as dependencies when installing new packages (this overrides settings in /etc/apt/apt.conf and ~/.aptitude/config). Packages previously installed due to recommendations will not be removed. This corresponds to the pair of configuration options Apt::Install-Recommends and Apt::AutoRemove::InstallRecommends. -r, --with-recommends Treat recommendations as dependencies when installing new packages (this overrides settings in /etc/apt/apt.conf and ~/.aptitude/config). This corresponds to the configuration option Apt::Install-Recommends --remove-user-tag <tag> For full-upgrade, safe-upgrade forbid-version, hold, install, keep-all, markauto, unmarkauto, purge, reinstall, remove, unhold, and unmarkauto: remove the user tag <tag> from all packages that are installed, removed, or upgraded by this command as if with the add-user-tag command. --remove-user-tag-from <tag>,<pattern> For full-upgrade, safe-upgrade forbid-version, hold, install, keep-all, markauto, unmarkauto, purge, reinstall, remove, unhold, and unmarkauto: remove the user tag <tag> from all packages that match <pattern> as if with the remove-user-tag command. The pattern is a search pattern as described in the section “Search Patterns” in the aptitude reference manual. For instance, aptitude safe-upgrade --remove-user-tag-from "not-upgraded,?action(upgrade)" will remove the not-upgraded tag from all packages that the safe-upgrade command is able to upgrade. -s, --simulate In command-line mode, print the actions that would normally be performed, but don't actually perform them. This does not require root privileges. In the visual interface, always open the cache in read-only mode regardless of whether you are root. This corresponds to the configuration option Aptitude::Simulate. --safe-resolver When package dependency problems are encountered, use a “safe” algorithm to solve them. This resolver attempts to preserve as many of your choices as possible; it will never remove a package or install a version of a package other than the package's default candidate version. It is the same algorithm used in safe-upgrade; indeed, aptitude --safe-resolver full-upgrade is equivalent to aptitude safe-upgrade. Because safe-upgrade always uses the safe resolver, it does not accept the --safe-resolver flag. This option is equivalent to setting the configuration variable Aptitude::Always-Use-Safe-Resolver to true. --schedule-only For commands that modify package states, schedule operations to be performed in the future, but don't perform them. You can execute scheduled actions by running aptitude install with no arguments. This is equivalent to making the corresponding selections in visual mode, then exiting the program normally. For instance, aptitude --schedule-only install evolution will schedule the evolution package for later installation. --show-package-names <when> Controls when the versions command shows package names. The following settings are allowed: · always: display package names every time that aptitude versions runs. · auto: display package names when aptitude versions runs if the output is not grouped by package, and either there is a pattern-matching argument or there is more than one argument. · never: never display package names in the output of aptitude versions. This option corresponds to the configuration item Aptitude::CmdLine::Versions-Show-Package-Names. --show-resolver-actions Display the actions performed by the “safe” resolver and by safe-upgrade. When executing the command safe-upgrade or when the option --safe-resolver is present, aptitude will display a summary of the actions performed by the resolver before printing the installation preview. This is equivalent to the configuration option Aptitude::Safe-Resolver::Show-Resolver-Actions. --show-summary[=<MODE>] Changes the behavior of “aptitude why” to summarize each dependency chain that it outputs, rather than displaying it in long form. If this option is present and <MODE> is not “no-summary”, chains that contain Suggests dependencies will not be displayed: combine --show-summary with -v to see a summary of all the reasons for the target package to be installed. <MODE> can be any one of the following: 1. no-summary: don't show a summary (the default behavior if --show-summary is not present). 2. first-package: display the first package in each chain. This is the default value of <MODE> if it is not present. 3. first-package-and-type: display the first package in each chain, along with the strength of the weakest dependency in the chain. 4. all-packages: briefly display each chain of dependencies leading to the target package. 5. all-packages-with-dep-versions: briefly display each chain of dependencies leading to the target package, including the target version of each dependency. This option corresponds to the configuration item Aptitude::CmdLine::Show-Summary; if --show-summary is present on the command-line, it will override Aptitude::CmdLine::Show-Summary. Example 10.  For instance, “aptitude -t experimental ...” will install packages from the experimental distribution unless you specify otherwise. For the command-line actions “changelog”, “download”, and “show”, this is equivalent to appending /<release> to each package named on the command-line; for other commands, this will affect the default candidate version of packages according to the rules described in apt_preferences(5). This corresponds to the configuration item APT::Default-Release. -V, --show-versions Show which versions of packages will be installed. This corresponds to the configuration option Aptitude::CmdLine::Show-Versions. -v, --verbose Causes some commands (for instance, show) to display extra information. This may be supplied multiple times to get more and more information. This corresponds to the configuration option Aptitude::CmdLine::Verbose. --version Display the version of aptitude and some information about how it was compiled. --visual-preview When installing or removing packages from the command line, instead of displaying the usual prompt, start up the visual interface and display its preview screen. -W, --show-why In the preview displayed before packages are installed or removed, show which manually installed package requires each automatically installed package. For instance: $ aptitude --show-why install mediawiki ... The following NEW packages will be installed: libapache2-mod-php5{a} (for mediawiki) mediawiki php5{a} (for mediawiki) php5-cli{a} (for mediawiki) php5-common{a} (for mediawiki) php5-mysql{a} (for mediawiki) When combined with -v or a non-zero value for Aptitude::CmdLine::Verbose, this displays the entire chain of dependencies that lead each package to be installed. For instance: $ aptitude -v --show-why install libdb4.2-dev The following NEW packages will be installed: libdb4.2{a} (libdb4.2-dev D: libdb4.2) libdb4.2-dev The following packages will be REMOVED: libdb4.4-dev{a} (libdb4.2-dev C: libdb-dev P<- libdb-dev) This option will also describe why packages are being removed, as shown above. In this example, libdb4.2-dev conflicts with libdb-dev, which is provided by libdb-dev. This argument corresponds to the configuration option Aptitude::CmdLine::Show-Why and displays the same information that is computed by aptitude why and aptitude why-not. -w <width>, --width <width> Specify the display width which should be used for output from the search command (by default, the terminal width is used). This corresponds to the configuration option Aptitude::CmdLine::Package-Display-Width -y, --assume-yes When a yes/no prompt would be presented, assume that the user entered “yes”. In particular, suppresses the prompt that appears when installing, upgrading, or removing packages. Prompts for “dangerous” actions, such as removing essential packages, will still be displayed. This option overrides -P. This corresponds to the configuration option Aptitude::CmdLine::Assume-Yes. -Z Show how much disk space will be used or freed by the individual packages being installed, upgraded, or removed. This corresponds to the configuration option Aptitude::CmdLine::Show-Size-Changes. The following options apply to the visual mode of the program, but are primarily for internal use; you generally won't need to use them yourself. --autoclean-on-startup Deletes old downloaded files when the program starts (equivalent to starting the program and immediately selecting Actions → Clean obsolete files). You cannot use this option and “--autoclean-on-startup”, “-i”, or “-u” at the same time. --clean-on-startup Cleans the package cache when the program starts (equivalent to starting the program and immediately selecting Actions → Clean package cache). You cannot use this option and “--autoclean-on-startup”, “-i”, or “-u” at the same time. -i Displays a download preview when the program starts (equivalent to starting the program and immediately pressing “g”). You cannot use this option and “--autoclean-on-startup”, “--clean-on-startup”, or “-u” at the same time. -S <fname> Loads the extended state information from <fname> instead of the standard state file. -u Begins updating the package lists as soon as the program starts. You cannot use this option and “--autoclean-on-startup”, “--clean-on-startup”, or “-i” at the same time. ENVIRONMENT HOME If $HOME/.aptitude exists, aptitude will store its configuration file in $HOME/.aptitude/config. Otherwise, it will look up the current user's home directory using getpwuid(2) and place its configuration file there. PAGER If this environment variable is set, aptitude will use it to display changelogs when “aptitude changelog” is invoked. If not set, it defaults to more. TMP If TMPDIR is unset, aptitude will store its temporary files in TMP if that variable is set. Otherwise, it will store them in /tmp. TMPDIR aptitude will store its temporary files in the directory indicated by this environment variable. If TMPDIR is not set, then TMP will be used; if TMP is also unset, then aptitude will use /tmp. FILES /var/lib/aptitude/pkgstates The file in which stored package states and some package flags are stored. /etc/apt/apt.conf, /etc/apt/apt.conf.d/*, ~/.aptitude/config The configuration files for aptitude. ~/.aptitude/config overrides /etc/apt/apt.conf. See apt.conf(5) for documentation of the format and contents of these files. SEE ALSO apt-get(8), apt(8), /usr/share/doc/aptitude/html/<lang>/index.html from the package aptitude-doc-<lang> AUTHOR Daniel Burrows<EMAIL_ADDRESS>Author. COPYRIGHT Copyright 2004-2011 Daniel Burrows. This manual page is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This manual page is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. aptitude <IP_ADDRESS> 11/05/2012 APTITUDE(8)


The Smugglers
Real Ale, Real Cider, Real Music
Main
Live Music
Food & Drink
Regular Events
Day
Type
Whom
*Except for 1st Tuesday in the Month which is Open Tap
Bands are subject to change please check regularly.
Sunday
Open Mic
Monday
Tuesday *
Open Mic
Pete the Jam
Wednesday
Open Mic
Thursday
Open Mic
Friday
Saturday
Opening Hours
SUN
MON
TUE
WED
THUR
FRI
SAT
Sorry
No Children after 9pm
Ideas
Nav Ideas
a
top
middle
bottom
very long


Next: Sharpsign Vertical-Bar, Previous: Sharpsign Plus, Up: Sharpsign
#- is like #+ except that it skips the expression if the test succeeds; that is,
#-test expression ≡ #+(not test) expression
For examples, see Examples of Feature Expressions.


BillingPlans
public final class BillingPlans: PayPalController
You use billing plans and billing agreements to create an agreement for a recurring PayPal or debit card payment for goods or services.
A billing plan includes payment definitions and other details. A plan must include at least one regular payment definition and, optionally, a trial payment definition. Each definition determines how often and for how long a customer is charged.
A plan can specify a type, which indicates whether the payment definitions in the plan have a fixed or infinite number of payment cycles. The plan also defines merchant preferences including how much it costs to set up the agreement, the links where a customer can approve or can cancel the agreement, and the action if the customer’s initial payment fails.
By default, a plan is not active when you create it. To activate it, you update its state
to ACTIVE.
For more information, see Billing Plans and Agreements.
Warning
The use of the PayPal REST/payments
APIs to accept credit card payments is restricted.
Instead, you can accept credit card payments with Braintree Direct.
-
Declaration
Swift
public let container: Container
-
Value is
"payments/billing-plans"
.See
PayPalController.resource
for more information.Declaration
Swift
public let resource: String
-
Declaration
Swift
public init(container: Container)
-
Creates a billing plan. In the JSON request body, include the plan details. A plan must include at least one regular payment definition and, optionally, a trial payment definition. Each payment definition specifies a billing period, which determines how often and for how long the customer is charged. A plan can specify a fixed or infinite number of payment cycles. A payment definition can optionally specify shipping fee and tax amounts. The default state of a new plan is
CREATED
. Before you can create an agreement from a plan, you must activate the plan by updating itsstate
toACTIVE
.A successful request returns the HTTP 201 Created status code and a JSON response body that shows plan details.
Declaration
Swift
public func create(with plan: BillingPlan) -> Future<BillingPlan>
Parameters
plan
The data for the new billing plan. The
.type
property must have a value before it is sent to the PayPal API.Return Value
The created billing plan wrapped in a future. If an error response was sent back instead, it gets converted to a Swift error and the future wraps that instead.
-
Lists billing plans. To filter the plans that appear in the response, specify one or more optional query and pagination parameters.
A successful request returns the HTTP
200 OK
status code and a JSON response body that lists plans with details.Declaration
Swift
public func list(state: BillingPlan.State? = nil, parameters: QueryParamaters = QueryParamaters()) -> Future<BillingPlanList>
Parameters
state
The state of the billing plans to fetch. PayPal uses
CREATED
if no value is passed in.parameters
The query-string paramaters passed in with the request. The values used for this endpoint are
page
,pageSize
, andtotalCountRequired
.Return Value
A list of the billing plans wrapped in a future. If an error response was sent back instead, it gets converted to a Swift error and the future wraps that instead.
-
Updates fields in a billing plan, by ID. In the JSON request body, include a patch object that specifies the operation to perform, one or more fields to update, and a new value for each updated field.
A successful request returns the HTTP
200 OK
status code with no JSON response body.Declaration
Swift
public func update(plan id: String, patches: [Patch]) -> Future<HTTPStatus>
Parameters
plan
The ID of the billing plan to update.
patches
An array of JSON patch objects to apply partial updates to resources.
Return Value
The HTTP status of the response, in this case
200 OK
. If an error response was sent back instead, it gets converted to a Swift error and the future wraps that instead. -
Shows details for a billing plan, by ID.
A successful request returns the HTTP
200 OK
status code and a JSON response body that shows plan details.Declaration
Swift
public func details(plan id: String) -> Future<BillingPlan>
Parameters
id
The ID of the billing plan for which to show details.
Return Value
The billing plan for the ID passed in, wrapped in a future. If an error response was sent back instead, it gets converted to a Swift error and the future wraps that instead.
-
Sets the state of a billing plan, by ID.
A successful request returns the HTTP
200 OK
status code with no JSON response body.Declaration
Swift
public func setState(of planID: String, to state: BillingPlan.State) -> Future<HTTPStatus>
Parameters
plan
The ID of the billing plan to update.
state
The new state to set the plan to.
Return Value
The HTTP status of the response, in this case
200 OK
. If an error response was sent back instead, it gets converted to a Swift error and the future wraps that instead.


|
UniversalDanmakuEngine
alpha 1.3.0
|
Component that contains informations of movement of the bullet. More...
Public Attributes | |
| UDEBulletMovementECS | Movement |
| Movement of the bullet. More... | |
| int | Phase |
| Phase of the bullet. More... | |
| int | TotalPhase |
| Total phase of the bullet. More... | |
| float | Time |
| Time passed from the initialization. More... | |
| UDETime.TimeScale | UsingTimeScale |
| Time scale the bullet uses. More... | |
| bool | IsSummoning |
| Whether the bullet is in summon phase. More... | |
| float | SummonTime |
| Time the bullet is in summon phase. More... | |
| bool | Loop |
| Whether go back to first phase when last phase ends. More... | |
Component that contains informations of movement of the bullet.
Definition at line 33 of file UDEBulletMovementsComponent.cs.
| bool SansyHuman.UDE.ECS.Object.UDEBulletMovements.IsSummoning |
Whether the bullet is in summon phase.
Definition at line 48 of file UDEBulletMovementsComponent.cs.
| bool SansyHuman.UDE.ECS.Object.UDEBulletMovements.Loop |
Whether go back to first phase when last phase ends.
Definition at line 53 of file UDEBulletMovementsComponent.cs.
| UDEBulletMovementECS SansyHuman.UDE.ECS.Object.UDEBulletMovements.Movement |
Movement of the bullet.
Definition at line 36 of file UDEBulletMovementsComponent.cs.
| int SansyHuman.UDE.ECS.Object.UDEBulletMovements.Phase |
Phase of the bullet.
Definition at line 38 of file UDEBulletMovementsComponent.cs.
| float SansyHuman.UDE.ECS.Object.UDEBulletMovements.SummonTime |
Time the bullet is in summon phase.
Definition at line 50 of file UDEBulletMovementsComponent.cs.
| float SansyHuman.UDE.ECS.Object.UDEBulletMovements.Time |
Time passed from the initialization.
Definition at line 43 of file UDEBulletMovementsComponent.cs.
| int SansyHuman.UDE.ECS.Object.UDEBulletMovements.TotalPhase |
Total phase of the bullet.
Definition at line 40 of file UDEBulletMovementsComponent.cs.
| UDETime.TimeScale SansyHuman.UDE.ECS.Object.UDEBulletMovements.UsingTimeScale |
Time scale the bullet uses.
Definition at line 45 of file UDEBulletMovementsComponent.cs.


Salsabila Azzahra
21
"Everything has an ending, so let it be over and rest assured all will be well."
azzahra07


mkdocs new project_name- Serve the project in the current directory using the mkdocs dev-server:
mkdocs serve- Build the documentation in the current directory:
mkdocs build- Deploy the documentation in the current directory to GitHub pages:
mkdocs gh-deploy


Taste the country's finest seafood cookie, made with all fresh ingredients.
Pat's Salmon Cookies are made with the freshest ingredients from Pike Place Market.
You can trust on our product to deliver the nutrition you need
without artificial additives and preservatives.


RECEIVED with thanks from
Diagnosis.
the sum of Rupees.
by cash/cheque, in part/full payment for consultation / operation.
Rs.
Cheque subject to realisation.
Signature
Dr. {{myprofile['userinfo'].name}} ({{myprofile['usereducation'].doctoreducation}})
RECEIVED with thanks from
Diagnosis.
the sum of Rupees.
by cash/cheque, in part/full payment for consultation / operation.
Rs.
Cheque subject to realisation.


I'm Andrew Blind, a professional photographer since 2012, located in the USA. Welcome to my Website, where you can have a look at my pictures, and even buy them if you like them and want to support my work ! Don't hesitate to contact me for any questions or inquiries ~


Kris van Rens
| SMF | == | Special member function |
| c’tor | == | Constructor |
| d’tor | == | Destructor |
Some member functions are special: under certain circumstances they are defined by the compiler even if not defined by the user.
cppreference.com § Non-static member functions
Let’s first look at ‘declare’:
Declarations introduce (or re-introduce) names into the C++ program. Each kind of entity is declared differently.
cppreference.com § Declarations
Definitions are declarations that fully define the entity introduced by the declaration.
cppreference.com § Definitions and ODR
Declarations:
Original code:
What the compiler will define for X
:
class X {
public:
inline constexpr X() noexcept = default;
// inline ~X() noexcept = default;
inline constexpr X(const X&) noexcept = default;
inline constexpr X& operator=(const X&) noexcept = default;
inline constexpr X(X&&) noexcept = default;
inline constexpr X& operator=(X&&) noexcept = default;
};
Examples are ill-formed, and the default constructors are deleted
For a default-defined SMF: the corresponding action (default construct/copy/move) will be performed on the non-
static
member variables.
For a deleted SMF: the corresponding SMF is defined but may not be used.
There are exceptions.
struct T {
T(); // Default constructor.
~T(); // Destructor.
T(const T& other); // Copy constructor.
T& operator=(const T& other); // Copy assignment operator.
T(T&& other); // Move constructor (C++11 and later).
T& operator=(T&& other); // Move assignment operator (C++11 and later).
};
Mandatory memory material
A constructor is called when initialization of an object takes place.
struct X { /* ... */ };
X a; // Calls default constructor.
X b{}; // Calls default constructor.
auto c = X{}; // Calls default constructor ('copy initialization').
X d{42}; // Calls 'some' (non-default) constructor taking an int.
X e{a}; // Calls copy constructor.
X f{std::move(a)}; // Calls move constructor.
Constructors that may be called without any argument are default constructors.
Any constructor that is not a default constructor.
The destructor is called when object lifetime ends.
| Copy constructor | T(const T&) |
| Copy assignment operator | T& operator=(const T&) |
| Move constructor | T(T&&) |
| Move assignment operator | T& operator=(T&&) |
static
member variable(s),Destruction is order is reverse
Compiler-undeclaration rules are easier to remember
| When user declares.. | Undeclaration of.. |
| Any other constructor | Default constructor |
| Any move operation | Copy operations |
| Any copy/move/destructor | Move operations |
Compiler-undeclaration rules easier to remember
| When user declares.. | Undeclaration of.. |
T(*) |
T() |
*(T&&) |
*(const T&) |
*(const T&) /*(T&&) /~T() |
*(T&&) |
Consider this copy-only class:
C++11 and later will still copy – due to ~X()
and copy fallback
| Rule of zero |
| Rule of zero or all |
| Rule of three |
| Rule of four and a half |
| Rule of five |
| Rule of six |
| Copy-only |
| Move-only |
If you don’t have to implement SMFs…then don’t!
Use the rule of zero for everything else.
Implement all SMFs, or: ‘rule of six’:
Implement as move-only / uncopyable:
struct ResourceManager {
ResourceManager();
~ResourceManager();
ResourceManager(ResourceManager&& other);
ResourceManager& operator=(ResourceManager&& other);
};
The rules/compiler will take care of the rest.
Implement as non-copyable, non-movable:
struct Immobile {
Immobile(const Immobile& other) = delete;
Immobile& operator=(const Immobile& other) = delete;
};
The rules/compiler will take care of the rest.
As a general one-rule-only policy the rule of zero or all can be followed.
Trigger for ‘all’ is any copy/move operations or ~T()
T(){}
private
sectionT() = default;
T() = delete;
in public
sectionvirtual
functions from T()
/~T()
,T()
,explicit
.Make any constructor that takes only one argument an
explicit
constructor.
Unless you intend to write a converting constructor.
Example
Example
Example
Consider this example:
value_
first,More efficient version:
Direct-initializes value_
.
What about this example?
Question: will value_
be initialized twice?
No.
No constructor needed
Strict initialization order is NOT enforced..
Use the member initializer list!
Turn on compiler warnings:
-Wreorder
//w15038
(and look at them..or better even, use -Werror
//WX
)
virtual
functions from T()
/~T()
,virtual
if applicable,virtual
destructorsA base class must have a
virtual
destructor.
virtual
destructorsDon’t throw exceptions from destructors!
terminate()
will be called!
*this
,*this
,Please don’t use them if you can
RAII == Resource Acquisition Is Initialization
std::unique_ptr<>
/std::shared_ptr<>
/std::lock_guard<>
/…
void thread_process() {
static std::mutex mutex;
std::lock_guard<std::mutex> lock(mutex);
// Do dangerous things that may throw an exception..
}
Object lock
will:
lock()
the mutex upon construction,unlock()
the mutex upon destruction.Use this idiom for implementing copy/move operations.
Enable compiler sanitizers! E.g. ASAN, UB, ..
Some static analyzers I’ve worked with:
They all provide rules for checking SMF use
| When user declares.. | Undeclaration of.. |
T(*) |
T() |
*(T&&) |
*(const T&) |
*(const T&) /*(T&&) /~T() |
*(T&&) |
virtual
,throw
from destructors,Thank you


Tic Tac Toe
Click X or O to choose side. X moves first.
X
O
Wins: 0 Draws: 0 Losses: 0
Computer Strategy:
Easy (sequential)
Increase Difficulty
Made by
eqmvii


Preparation time
less than 30 mins
Cooking time
over 2 hours
Serves
Serves 8-10
Goose really ought to rival turkey more as the Christmas bird of choice, if only for the quality of the resulting roast potaoes. A chickpea and sausage stuffing makes a perfect side dish.
Preheat the oven to 220C/425F/Gas 7.

Stir in the chickpeas and crush some of them with a fork or masher, leaving a few whole for texture.
In a bowl, combine the sausagemeat with the lemon juice and zest and the mint. Add the onions and chickpeas to the bowl and mix well by hand. Fry a little of the mixture in the pan and taste for seasoning, adding salt and pepper, to taste.
Place the goose in a large roasting tin and stuff half of the chickpea mixture into the cavity. Add the lemon shells to fill and remaining space. Roll the rest of the stuffing into balls and set aside in the fridge.
Roast the goose for 60 minutes and then reduce the temperature of the oven to 180C/350F/Gas 4.

Return the goose to the oven and continue cooking for 2-2½ hours, until the skin is dark brown and crisp.
Remove the goose from the oven, cover with foil and leave to rest for 15 minutes before carving. Spoon out the stuffing and roast potatoes and keep warm in the oven.
Serve with all the Christmas trimmings.


{% extends 'base.html' %} {% block title %} WhatAreYouDoing {% endblock %} {% block body %} I don't quite understand what you are looking for... {% endblock %}


InterviewMe
About
Profile
Events
Availability
Scheduling
Logout
Availability
Update your availability to be an Interviewer for the week below. Remember that an interview lasts for an hour.
< Previous Week
Next Week >
Loading your interview availability...
Update Availability


New Game
Settings
Player
Name
Level
Player 1(you):
Player 2(East):
Player 3(North):
Player 4(West):
Back
Apply


Switch Sides
Reset Board
Board Size
Undo Move
White to move
Portable Game Notation (PGN):
Forsyth-Edwards Notation (FEN):


* User Name is required
* Full Name is required
Password is required.
Confirm password is required.
Password & Confirm Password does not match.
Email is required.
Email is invalid.
Contact No is required.
Address Is Required.


FEDS A Film Review Copyright Dragan Antulov 2000
Those who have read some of my previous reviews know that I have some problems accepting words like "comedy" and "Ivan Reitman" in the same sentence. In the decade and half after GHOSTBUSTERS, his last truly funny film, Reitman was constantly failing to make any film able to produce laughter among audience. This failure was most the evident case of Hollywood creative bankruptcy associated with "high concept" films, and it wasn't limited only on Reitman's work as director. Reitman record as producer was equally unimpressive, and FEDS, 1988 comedy directed by Dan Goldberg is just another example.
The heroine of this film is Elizabeth De Witt (played by Rebecca de Mornay), former Marine that decides to become an FBI Agent. Before being enrolled in FBI Academy she is told that only a fraction of the class would actually finish the course, graduate and become an agent. Her own prospects seem discouraging, since she lacks school credentials and skills necessary to wrestle with high academic demands. Janis Zuckerman (played by Mary Gross), her nerdish roommate, has quite another problem - she could eat toughest academic courses for breakfast, but her physical skills and fitness seem way bellow high FBI standards. After a while both women decide to compensate each other's flaws with tutoring.
Probably some time during production Goldberg and his screenplay co- writer Len Bloom realised that their gags simply aren't funny and that this rather weak copy of POLICE ACADEMY couldn't work. So, they added some usual story ingredients - action in the form of bank robbery subplot, and some romance for our heroine, although failed one in the form of hunkish would-be agent Brent Shepard, played by Ken Marshall. Even with that, this film remain unattractive and its short length shows the lack of creative juices among its makers. Luckily, charm and tragically underused comedic talent of Rebecca de Mornay save this film from turning into total disaster. Unlike Mary Gross, who has the same facial expression for the most of the film, she gives some realism and humanity for her character.
Another thing that gives some purpose to this film is its educational value. Those who are able to swallow Bloom's and Goldberg's weak attempts on humour could get some interesting insight into the inner workings of world's most famous law enforcement organisation (after LAPD, of course). The training course is presented seriously and realistically with future Senator Fred Dalton Thompson playing quite believable chief instructor and giving lessons usually not applied by most of the on-screen lawmen. FBI, just as any other police organisation in the world, relies on its brains more than its guns, and this film reflects that - good psychological skills, intelligence and mastery of complicated legal procedures are actually more valuable than simple gunplay. This message of FEDS is more important than cliched and unsuccessful attempts to preach feminism.
RATING: 4/10 (+)
Review written on January 13th 2000
Dragan Antulov a.k.a. Drax Fido: 2:381/100 E-mail<EMAIL_ADDRESS>E-mail<EMAIL_ADDRESS>E-mail<EMAIL_ADDRESS>Filmske recenzije na hrvatskom/Movie Reviews in Croatian http://film.purger.com
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


photography
Side Effects
Shanghai is an international metropolis that represents the highest level of urban development in China. Walking in its midst, I cannot help but look up and marvel at the city around me. Undoubtedly, urbanization brings a lot of convenience, and I am one of the beneficiaries. However, having lived in Shanghai for several years and gotten a deep understanding of this city, I start to realize that urbanization also brings side effects.
graphic design
Helium
I often see some teenagers oddly dressed to show their personality. In fact, it is likely that they just blindly follow trend and don't have a deep understanding of their own heart. However, those people who do things in a low-key way-unsocial, not used to be interested in relations with others, deeply know themselves and insist to be themselves. Thus,low key is not without personality but a kind of character.
graphic design
Otl Aicher 2015 Exhibition
OTL AICHER 2015 EXHIBITION IDENTITY is a virtual design project to salute Otl Aicher, who was the master of Modernism graphic design.
Otl Aicher 2015 exhibition fully shows Otl aicher’s design works of his whole life, including overall visual identity of the 1872 Munich Olympics ,Rotis font family, Lufthansa visual identity design, etc. The audience will notice Aicher’s great capability of arragement and plan by visiting the exhibition.
Otl Aicher 2015 exhibition fully shows Otl aicher’s design works of his whole life, including overall visual identity of the 1872 Munich Olympics ,Rotis font family, Lufthansa visual identity design, etc. The audience will notice Aicher’s great capability of arragement and plan by visiting the exhibition.
user interface
Lianlian App User Interface
This project is conducted when I took a job in Shanghai Lianlian Network Technology Co., Ltd. as an UI designer, from November, 2014 to November, 2015. This is my first formal UI work.
Lianlian, a fitness-category app, has gone online in app store of both Android and iOS, with accumulation users of 840,000. I took charge of user interface design of Lianlian 3.0 version, which went online on November, 7th, 2015 and won Apple's official recommendation, making it to the app store home page and the best new app list.
Lianlian, a fitness-category app, has gone online in app store of both Android and iOS, with accumulation users of 840,000. I took charge of user interface design of Lianlian 3.0 version, which went online on November, 7th, 2015 and won Apple's official recommendation, making it to the app store home page and the best new app list.
Education
Shanghai Jiaotong University (SJTU) 09/2011-06/2015
Major: Graphic design
Parsons school of design 08/2016-05/2018
Major:Design and technology
Related experience
Shanghai Lianlian Network Technology Co., Ltd 11/2014-11/2015
Shanghai Willing Information Technology Co., Ltd 03/2014-09/2014
Noppen the Corridor of Insights 08/2014-09/2014
Contact
Tel:(646)-250-3376Email:shil630@newschool.edu


{% blocktrans with ballance=request.user.ballance|floatformat:2 %}Your balance is {{ ballance }}{% endblocktrans %} {% trans 'currency' %}
{% if request.user.is_staff %}
{% blocktrans trimmed %}
Attantion!
You are is admin, and do not be active here, please back to admin side. Client side to you for reference only.
{% endblocktrans %}
{% endif %}
{% blocktrans %}You may add link to this personal page to bookmarks by pressing Ctrl+D{% endblocktrans %}
{% include '_messages.html' %}
{% block client_main %}{% endblock %}


--- layout: post title: 'LIFT07: CERN''s 27km Big Bang machine, Brian Cox' date: 2007-02-09 00:00:00 category: digital-media ---
LIFT07: CERN's 27km Big Bang machine, Brian Cox
Half the particle physicists in the world are connected to CERN.
We're trying to understand the basic building blocks of the universe.
"All science is either physics or stamp collecting" - Ernest Rutherford (who went on to win a Nobel Prize for chemistry).
"We are the little difference in behaviour between matter and anti-matter"
Things that have weight do so because their particles are surrounded by Higgs particles.
Dataflow : 10k encyclopedia britannicas;/second generated by the Hadron Collider.
95% of the universe is made up out of stuff that isn't our matter. 25% dark matter.
Show's a video of two galaxies colliding together. The dark matter just passes on, the normal matter collides and bangs into itself.
"We can see 11 dimensions by making mini-black holes in the Hadron Collider. Which is not dangerous, honest."
"The Higgs is a theory. We got the money on the basis that we'd find it. If we don't we'll have to run away."
My notes for this one are poor because I've spent most of the talk with my mouth open, jaw on desk.


Dear Friend Please accept my apology for contacting this way, it is due to the urgency of my request. I got your contact from an enquiry i placed at the chamber of commerce, trade and industry. i and my partners are in need of a worthy business partner abroad, who can handle the investment of specified funds which have been lying fallow for sometime . If you accept to work with us, you would be our foreign patner to recieve the said funds on our behalf, due to our sensitive position in OUR PLACE OF WORK, and also to hold it in some investment until we can travel to meet with you. At your request i will intimate you with the blueprint when i recieve your mail. NOTE:PLEASE FORWARD YOUR REPLY ONLY TO THIS MAIL BOX STATED HERE<EMAIL_ADDRESS>for security reasons and make sure you include your private telephone number for easy communication. Hoping to hear from you soon. My regards. Mohammed Abacha mohaabacha@netscap.net


Ezekiel 23:31
Thou hast walked in the way of thy sister; therefore will I give her cup into thine hand.


--- layout: default title: St. Paul's Cemetery alias: cemetery img-float: left class: page sitemap: priority: 0.7 changefreq: 'yearly' lastmod: 2017-10-17T19:23:34+00:00 image-array: - img: cem-1.jpg lightbox: cemetery alt: Butterfly and Kubota - img: cem-2.jpg lightbox: cemetery alt: Infant Wilson tombstone - img: cem-3.jpg lightbox: cemetery alt: Raymond Wothe tombstone - img: cem-4.jpg lightbox: cemetery alt: Vatter & Mutter Thuerwachter monument - img: cem-5.jpg lightbox: cemetery alt: tombstones - img: cem-6.jpg lightbox: cemetery alt: Albert Bergen tombstone - img: cem-7.jpg lightbox: cemetery alt: Anna Lohse infant tombstone - img: cem-8.jpg lightbox: cemetery alt: monument - img: cem-9.jpg lightbox: cemetery alt: monument - img: cem-10.jpg lightbox: cemetery alt: Flowers & tombstone - img: cem-11.jpg lightbox: cemetery alt: Mutter tombstone - img: cem-12.jpg lightbox: cemetery alt: Maria Wagner infant tombstone - img: cem-13.jpg lightbox: cemetery alt: John Rothman tombstone - img: cem-14.jpg lightbox: cemetery alt: Charles & Louise Thuerwachter tombstone - img: cem-15.jpg lightbox: cemetery alt: Philip & Barbara Rothman tombstone - img: cem-16.jpg lightbox: cemetery alt: Memorial flowers (geraniums) --- {% include custom-photo.html %}
The St. Paul's cemetery lies at the end of a gravel road, surrounded by farm fields on a wooded slope about a quarter-mile from the present sanctuary.
As best we can tell, the cemetery predates the congregation itself, with burials going back to the 1830's. It is a place of great peace, often visited by members looking for solitude to think, meditate, and pray. The cemetery board has begun a long-term effort to locate and map all the graves. We hope to post the results of this survey and other genealogical data soon.


Agent config file:
/etc/puppetlabs/puppet/puppet.conf
Catalog is saved on the agent as a .json file
/var/lib/puppet/client_data/catalog/$certname.json
# Apply catalog using -verbose, -ignorecache, -no-daemonize
# -detailed-exit-codes, -show_diff
puppet agent --test (or -t)
# Run in debug mode with more output:
puppet agent -t --debug
# Run simulation (no changes to system):
puppet agent -t --noop
# Run catalog for different environment than whats configured
# in Puppet Agent's conf file:
puppet agent -t --environment development
# Disable puppet agent from running on node:
puppet agent --disable (this creates a lock file)
# to enable:
puppet agent --enable
# show all installed packages:
puppet resource package
# install or remove package:
puppet resource package apache ensure=present/absent
# show all managed resources:
puppet resource


Colts lose Mack to hand injury; running game keeps chugging
by The Associated PressAn injury to Marlon Mack did little to slow the Indianapolis Colts’ running game on Sunday.
Mack rushed 14 times for 109 yards and a touchdown before leaving with a hand injury in the third quarter of Indianapolis’ 33-13 victory over the Jacksonville Jaguars. His replacement, Jonathan Williams, had 13 carries for 106 yards, the first 100-yard game of his career.
The Colts also lost rookie cornerback Rock Ya-Sin to an ankle injury in the third quarter.
TOP STORIES
Biden trolls Trump after Stone verdict: 'Zero criminal convictions' for Team Obama
Trump plans Florida 'homecoming' rally to celebrate changing residency from New York
No one is above the law - unless you're a Democrat
For Jacksonville, defensive end Lerentee McCray left in the first half with an injured hamstring, and tight end Josh Oliver left in the fourth quarter with a back injury.
The Minnesota Vikings pulled off a goal-line stand to finish off their comeback victory over the Denver Broncos without strong safety Harrison Smith, who hurt his hamstring in the fourth quarter and didn’t return. Vikings linebacker Ben Gedeon suffered a concussion in the first quarter and was done for the day.
The Broncos got a 1-yard touchdown from fullback Andy Janovich, who later hurt his elbow while being tackled at the end of a short reception and did not return.
In the Dallas’ victory at Detroit, Cowboys left tackle La’el Collins left with a knee injury in the fourth quarter. Three Lions left the game with injuries: free safety Tracy Walker (knee), specialist Jamal Agnew (ankle) and fullback Nick Bawden (knee).
Offensive tackle Ty Nsekhe was carted off the field in the third quarter of Buffalo’s win at Miami with a right ankle injury. The Bills also lost safety Siran Neal to a concussion.
Dolphins wide receiver Gary Jennings didn’t play the second half because of a shoulder injury. Miami also lost safety Bobby McCain to a shoulder injury in the third quarter and tackle Julien Davenport to a right knee injury in the fourth.
In the New York Jets’ victory over the Washington Redskins, Jets right tackle Chuma Edoga and Redskins defensive lineman Daron Payne both left with ankle injuries.
Atlanta defensive end Takk McKinley injured his shoulder on a first-half sack of Carolina quarterback Kyle Allen and did not return in the Falcons’ win over the Panthers.
Problems for the Houston Texans in their blowout loss at Baltimore began in pregame warmups, when safety Mike Adams sustained a concussion. He did not play. The Texans also lost cornerback Lonnie Johnson Jr. to a right foot injury and safety Justin Reed to a shoulder injury, and the Ravens took advantage of Houston’s depleted secondary as they rolled to a 41-7 win.
More AP NFL: https://apnews.com/NFL and https://twitter.com/AP_NFL
Sign up for Daily Newsletters
Copyright © 2019 The Washington Times, LLC.
Please read our comment policy before commenting.


public interface
CharStream
| Modifier and Type | Method and Description |
|---|---|
void
|
backup
(int amount)
Backs up the input stream by amount steps.
|
char
|
BeginToken
()
Returns the next character that marks the beginning of the next token.
|
void
|
Done
()
The lexer calls this function to indicate that it is done with the stream
and hence implementations can free any resources held by this class.
|
int
|
getBeginColumn
()
Returns the column number of the first character for current token (being
matched after the last call to BeginTOken).
|
int
|
getBeginLine
()
Returns the line number of the first character for current token (being
matched after the last call to BeginTOken).
|
int
|
getColumn
()
Deprecated.
|
int
|
getEndColumn
()
Returns the column number of the last character for current token (being
matched after the last call to BeginTOken).
|
int
|
getEndLine
()
Returns the line number of the last character for current token (being
matched after the last call to BeginTOken).
|
String
|
GetImage
()
Returns a string made up of characters from the marked token beginning
to the current buffer position.
|
int
|
getLine
()
Deprecated.
|
char[]
|
GetSuffix
(int len)
Returns an array of characters that make up the suffix of length 'len' for
the currently matched token.
|
char
|
readChar
()
Returns the next character from the selected input.
|
char readChar() throws IOException
IOException
int getColumn()
getEndColumn()
int getLine()
getEndLine()
int getEndColumn()
int getEndLine()
int getBeginColumn()
int getBeginLine()
void backup(int amount)
char BeginToken() throws IOException
IOException
String GetImage()
char[] GetSuffix(int len)
void Done()


Class representing a color.
Iterating through a [name] instance will yield its components (r, g, b) in the corresponding order.
A Color can be initialised in any of the following ways:
//empty constructor - will default white
const color1 = new THREE.Color();
//Hexadecimal color (recommended)
const color2 = new THREE.Color( 0xff0000 );
//RGB string
const color3 = new THREE.Color("rgb(255, 0, 0)");
const color4 = new THREE.Color("rgb(100%, 0%, 0%)");
//X11 color name - all 140 color names are supported.
//Note the lack of CamelCase in the name
const color5 = new THREE.Color( 'skyblue' );
//HSL string
const color6 = new THREE.Color("hsl(0, 100%, 50%)");
//Separate RGB values between 0 and 1
const color7 = new THREE.Color( 1, 0, 0 );
[page:Color_Hex_or_String r] - (optional) If arguments [page:Float g] and
[page:Float b] are defined, the red component of the color. If they are
not defined, it can be a
[link:https://en.wikipedia.org/wiki/Web_colors#Hex_triplet hexadecimal triplet] (recommended),
a CSS-style string, or another `Color` instance.
[page:Float g] - (optional) If it is defined, the green component of the
color.
[page:Float b] - (optional) If it is defined, the blue component of the
color.
Note that standard method of specifying color in three.js is with a
[link:https://en.wikipedia.org/wiki/Web_colors#Hex_triplet hexadecimal triplet],
and that method is used throughout the rest of the
documentation.
When all arguments are defined then [page:Color_Hex_or_String r] is the
red component, [page:Float g] is the green component and [page:Float b] is
the blue component of the color.
When only [page:Color_Hex_or_String r] is defined:
Read-only flag to check if a given object is of type [name].
Red channel value between `0` and `1`. Default is `1`.
Green channel value between `0` and `1`. Default is `1`.
Blue channel value between `0` and `1`. Default is `1`.
Adds the RGB values of [page:Color color] to the RGB values of this color.
Sets this color's RGB values to the sum of the RGB values of [page:Color color1] and [page:Color color2].
Adds [page:Number s] to the RGB values of this color.
Applies the transform [page:Matrix3 m] to this color's RGB components.
Returns a new Color with the same [page:.r r], [page:.g g] and [page:.b b] values as this one.
Copies the [page:.r r], [page:.g g] and [page:.b b] parameters from [page:Color color] in to this color.
Converts this color from linear space to sRGB space.
Converts this color from sRGB space to linear space.
[page:Color color] — Color to copy.
Copies the given color into this color, and then converts this color from
linear space to sRGB space.
[page:Color color] — Color to copy.
Copies the given color into this color, and then converts this color from
sRGB space to linear space.
Compares the RGB values of [page:Color color] with those of this object. Returns true if they are the same, false otherwise.
[page:Array array] - [page:Array] of floats in the form [ [page:Float r],
[page:Float g], [page:Float b] ].
[page:Integer offset] - An optional offset into the array.
Sets this color's components based on an array formatted like [
[page:Float r], [page:Float g], [page:Float b] ].
[page:BufferAttribute attribute] - the source attribute.
[page:Integer index] - index in the attribute.
Sets this color's components from the [page:BufferAttribute attribute].
Returns the hexadecimal value of this color.
Returns the hexadecimal value of this color as a string (for example, 'FFFFFF').
[page:Object target] — the result will be copied into this Object. Adds h,
s and l keys to the object (if not already present).
Convert this Color's [page:.r r], [page:.g g] and [page:.b b] values to
[link:https://en.wikipedia.org/wiki/HSL_and_HSV HSL] format and returns an
object of the form:
{
h: 0,
s: 0,
l: 0
}
[page:Color target] — the result will be copied into this object.
Returns the RGB values of this color as an instance of [page:Color].
Returns the value of this color as a CSS style string. Example: `rgb(255,0,0)`.
[page:Color color] - color to converge on.
[page:Float alpha] - interpolation factor in the closed interval `[0,
1]`.
Linearly interpolates this color's RGB values toward the RGB values of the
passed argument. The alpha argument can be thought of as the ratio between
the two colors, where `0.0` is this color and `1.0` is the first argument.
[page:Color color1] - the starting [page:Color].
[page:Color color2] - [page:Color] to interpolate towards.
[page:Float alpha] - interpolation factor, typically in the closed
interval `[0, 1]`.
Sets this color to be the color linearly interpolated between [page:Color color1]
and [page:Color color2] where alpha is the percent distance along
the line connecting the two colors - alpha = 0 will be [page:Color color1],
and alpha = 1 will be [page:Color color2].
[page:Color color] - color to converge on.
[page:Float alpha] - interpolation factor in the closed interval `[0,
1]`.
Linearly interpolates this color's HSL values toward the HSL values of the
passed argument. It differs from the classic [page:.lerp] by not
interpolating straight from one color to the other, but instead going
through all the hues in between those two colors. The alpha argument can
be thought of as the ratio between the two colors, where 0.0 is this color
and 1.0 is the first argument.
Multiplies this color's RGB values by the given [page:Color color]'s RGB values.
Multiplies this color's RGB values by [page:Number s].
Adds the given [page:Float h], [page:Float s], and [page:Float l] to this color's values. Internally, this converts the color's [page:.r r], [page:.g g] and [page:.b b] values to HSL, adds [page:Float h], [page:Float s], and [page:Float l], and then converts the color back to RGB.
[page:Color_Hex_or_String r] - (optional) If arguments [page:Float g] and [page:Float b] are defined, the red component of the color. If they are
not defined, it can be a [link:https://en.wikipedia.org/wiki/Web_colors#Hex_triplet hexadecimal triplet] (recommended), a CSS-style string, or another `Color` instance.
[page:Float g] - (optional) If it is defined, the green component of the color.
[page:Float b] - (optional) If it is defined, the blue component of the color.
See the Constructor above for full details about possible arguments. Delegates to [page:.copy],
[page:.setStyle], [page:.setRGB] or [page:.setHex] depending on input type.
Sets this colors's [page:.r r], [page:.g g] and [page:.b b] components from the x, y, and z components of the specified [page:Vector3 vector].
[page:Integer hex] —
[link:https://en.wikipedia.org/wiki/Web_colors#Hex_triplet hexadecimal triplet] format.
Sets this color from a hexadecimal value.
[page:Float h] — hue value between `0.0` and `1.0`
[page:Float s] — saturation value between `0.0` and `1.0`
[page:Float l] — lightness value between `0.0` and `1.0`
Sets color from HSL values.
[page:Float r] — Red channel value between `0.0` and `1.0`.
[page:Float g] — Green channel value between `0.0` and `1.0`.
[page:Float b] — Blue channel value between `0.0` and `1.0`.
Sets this color from RGB values.
[page:Float scalar] — a value between `0.0` and `1.0`.
Sets all three color components to the value [page:Float scalar].
[page:String style] — color as a CSS-style string.
Sets this color from a CSS-style string. For example, "rgb(250, 0,0)",
"rgb(100%, 0%, 0%)", "hsl(0, 100%, 50%)", "#ff0000", "#f00", or "red" ( or
any [link:https://en.wikipedia.org/wiki/X11_color_names#Color_name_chart X11 color name] -
all 140 color names are supported ).
Translucent colors such as "rgba(255, 0, 0, 0.5)" and "hsla(0, 100%, 50%,
0.5)" are also accepted, but the alpha-channel coordinate will be
discarded.
Note that for X11 color names, multiple words such as Dark Orange become
the string 'darkorange'.
[page:String style] — color name ( from
[link:https://en.wikipedia.org/wiki/X11_color_names#Color_name_chart X11 color names] ).
Sets this color from a color name. Faster than [page:.setStyle] method if
you don't need the other CSS-style formats.
For convenience, the list of names is exposed in Color.NAMES as a hash:
Color.NAMES.aliceblue // returns 0xF0F8FF
Subtracts the RGB components of the given color from the RGB components of this color. If this results in a negative component, that component is set to zero.
[page:Array array] - An optional array to store the color to.
[page:Integer offset] - An optional offset into the array.
Returns an array of the form [ r, g, b ].
This methods defines the serialization result of [name]. Returns the color as a hexadecimal value.
[link:https://github.com/mrdoob/three.js/blob/master/src/[path].js src/[path].js]


Load this page in two browsers and allow camera access.
You get a video connection and a chat window.


T minus 6 days
Last night we left town late after our day of cleaning, and headed off up the sea to sky for a couple nights of camping on the back way to Kamloops. Even though it's a weeknight, the popular campgrounds (Porteau Cove and Alice Lake) were all full, and so we continued on past Squamish up to Whistler. We stopped at Cal-Cheak Recreation Site, and discovered a beautiful, well-kept, quiet little camping area only a few hundred meters from the highway and right by the river. Just what we wanted for a quick overnight stop.
This morning, we drove back down the road a minute or two to Brandywine Falls. We've never actully stopped here before on our many trips to Whistler, and this was well worth the stop. The 3rd highest waterfall in BC I believe, and a good example of some lava flows (we found the nearby educational earthcache).
We made a short stop in Whistler for groceries for a picnic, and then stopped just before Pemberton at Nairn Falls. This is another provincial park, and the 3rd major waterfall on the sea to sky. Very different to the other two, as this is less about the height of the waterfall and more the cool erosion of the rock and meandering waterway. We had a quick rain shower pass by right near the falls and we had to hide out under some trees for 10 minutes while it went by.
Continuing through Pemberton we started up the Duffey Lake road, passing by Joffre Lakes (we'll have to save that for another time), and Duffey Lake. Dropping into Lillooet we pulled off to check out the views of the BC Hydro resevoir here, and then stopped for groceries for dinner.
We camped tonight at Marble Canyon on my brother's recommendation. A nice enough Provincial Park along the lake, and the tent sites are set away from the parking down by the lake. We made a nice dinner and enjoyed paddling in the lake. As we cleaned up though we could see a storm with lightning and thunder coming down the valley. We hurried to put things away and get ready for bed, and made it into the tent just as the rain arrived. 5 minutes later the torrential downpour started, and we realised it was hailing. The tent held up well, although a lot of hail bounced under the fly and it got a bit cold. The hail soon melted and turned to rain, until we realised there was 2 inches of water sitting in our tent pad not draining away properly. The edges of the tent were floating, and a few flip flops floated away, but again our tent held up admirably and we didn't get wet. The rain eased off and the ground started to drain, so we drifted off to sleep thinking the storm was over...
But at around midnight, we were awakened by a park ranger yelling down the embankment. Apparently a mudslide came down the hill just around the corner, and they were concerned about a second slide possibly near the campsite. We packed up the soaking wet tent in the dark and bundled everything into the car and headed down the road, along with the rest of the campground. In nearby Cache Creek, we learnt the highway was now closed between Lillooet and Cache Creek, and would remain closed for most of the next day. Since we were so close to Kamloops, and didn't really feel like setting up the wet tent, we opted to just drive the rest of the way, and sleep in a real bed. An adventurous day in the end!
BC Highway 99 Mudslides August 2014 by B.C. Ministry of Transportation and Infrastructure, on Flickr


Natural ability
Since its inception, this wild
pokemon
has been holding bones at all times. He knows how to use them as weapons, throwing them with great skill, like boomerangs, against enemies. His attack power doubles when wielding a club.


Make some pictures of some dataset(s). Use either of the two datasets we have provided (questionnaire, and donations-vs-deaths), or acquire one of your own.
- Write about your process and your results using RMarkdown and submit both the Rmd and compiled html as a pull request to the course repository.
- Next week, you will each lead a code review with a group of your peers explaining your implementations. You will then have the opportunity to amend your branch in light of your peers feedback. Pull requests will be merged over the following week when you indicate that they are complete.
This is a many-part assignment. It asks you to do some things that are familiar, to recite some unfamiliar incantations to git, and to follow some strict rules about naming and changes that are appropriate to include in a pull request. On the other hand, the actual work of the assignment making pictures of data is an open, creative exercise and is a chance to share something with your peers and to learn from them.
git checkout -b hw1
qmssviz/hw1/_posts
.published: false
(This prevents gh-pages from trying to re-render your document, and simply use the html one)tags: hw1
(for organization)2014-09-18-HW1-Michael-Malecki.Rmd
. (Uni is fine too. You just can't all give it the same non-unique name hw1
.)git push -u origin hw1
so that your current branch goes live to your fork and the two (local and server) know about each other.If in the first draft of the assignment you cant debug your issues with git or Rmd, you will have time in class to show your broken branch to your peers, who might be able to help, and to try again. Share your frustrations and get them resolved.


Boy, 8, shot in face during Mormon family massacre in Mexico seen for first time
Cody Langford is the last of seven siblings who survived Mexican cartel massacre to be released from hospital where he was treated for multiple gun wounds
by Lila RandallA mormon boy shot in the jaw pictured for first time with siblings after they miraculously survived Mexican cartel’s brutal massacre.
Cody Langford survived being shot in the jaw and right foot, during the Mexican ambush in the Mexican state of Sonora.
Cody was the last of seven children to be released from a Tuscan, Arizona, hospital last Saturday.
The seven Langford survivors were pictured together after losing their mum Dawna and two of their brothers, Trevor, 11, and Rogan, who were among nine killed by a suspected drug cartel gunmen.
Three mums and six children died in the massacre.
A heartwarming snap shows Cody sitting in a wheelchair with his six siblings surrounding him at their home in Arizona, which was published on the family’s GoFundMe page.
The injured boy was travelling in a convoy of SUVs with seventeen members of the LeBaron Mormon community to visit family when they were attacked around 70 miles south of the US border.
The families were travelling from their home on the La Mora ranch to a settlement along a hostile road controlled by men financed by Mexico’s illegal drugs trade, the BBC reported.
Dawna Ray Langford and her sons Trevor, 11, and Rogan, two, were killed in one car while Christina Langford Johnson, 31, was killed in another. Her seven-month-old baby, Faith Langford, survived and was found on the floor of the vehicle.
Mum Rhonita Maria LeBaron, 33, was killed along with her six-month-old twin babies, Titus and Tiana, and two other children - Crystal, eight, and Howard, 10. The others were allegedly taken hostage eight miles up the road.
Mexican reports said the attack could have been a case of mistaken identity, as the family were travelling in SUVs similar to those used by cartel.
Others say they could have been targeted in a crossfire.
Cody’s extraordinary recovery has been documented online.
Earlier this month, the youngster had his jaw wired shut and had to undergo further rounds of surgery after medics located yet another bullet.
Video footage shows Cody in pyshio, his leg bandaged, practising to straighten his legs and learning to walk.
So far the GoFundMe page has raised more than £190,000 which the father, David Langford, will use to cover medical expenses and split with the Miller and Johnson families, who were also caught up in the shooting.
Mr Langford told ABC: "Every one of my children that survived that are living miracles," Langford said. "How many bullet holes were fired into that vehicle … at that horrific scene and how many children were involved. It's amazing. It's amazing. It's beyond amazing that they survived."
Mr Langford said he wants the attackers to face justice. He added: "I believe in forgiveness, but I also believe in justice and forgiveness doesn't rob justice. You don't get justice too much in Mexico," he said.
Most of the extended LeBaron family plan to leave Mexico after the shooting.


We are missionaries called to reach college campuses for Christ. We accomplish our mission by partnering with local churches to evangelize and connect new believers with a Bible-believing church. We’re excited for the opportunity to come to your church and work with you to present the gospel to your local college students.
Listed below is an overview of what a typical full week in your church would look like. Feel free to use this as a menu to pick and choose what best fits your church and availability.
Saturday
Meet with Pastor and scout the school
Sunday
Sunday School Lesson on the topic of “Fishing for Men – Four Styles of Evangelism”. In this lesson I encourage Christians that they don’t have to be an evangelist to share the gospel. God has called everyone to share their testimony.
Sunday Morning Message to stir up the saints to spiritual usefulness and encourage them to be used by God to share their faith.
Sunday Evening Message on the topic of “Wisdom in Winning Souls”. This message incorporates my experiences and what to expect when sharing the gospel with college students.
Monday & Tuesday
Those who will be evangelizing will meet at 10am at the church to go over a brief evangelistic plan for the day and prepare to go on the college campus.
We will typically be on campus between 11a – 2p to hand out tracts and evangelize. We can also go out in the evening from 6-8p, either in addition to the morning time or replacing the morning time on one of the days.
Wednesday
Prayer Meeting – An hour before service we meet to pray for those who participated in evangelism and the college students we reached.
Wednesday Evening Service – We share our ministry presentation and testimonies from the week.
Thursday
Early rise breakfast and prayer for the church with Pastor
Moving on to the next ripe harvest – “…behold, I say unto you, Lift up your eyes, and look on the fields, for they are white already to harvest.” John 4:35
We recognize that your community and local colleges are your Jerusalem. We ask that you prayerfully consider allowing our ministry to partner with your church to fulfill the Great Commission in your area.