similar to: install.packages() / update.packages() sometimes outputs to stdout and sometimes to stderr [and menu() & readline()]

SEND TO STDERR: Currently utils::menu() and utils::select.list() with graphics=FALSE queries the user via the standard output (stdout). I'd like to suggest to do this via standard error (stderr) instead, or at least have an option to choose which output stream. If they would send to stderr, they could also be used in various report generators that capture stdout and redirect to the generated

Why do you need this? The sink system is often specifically needed to capture such messages and display them to the user, for example in an embedded environment. Many applications would not work when you bypass the stdout/stderr set by the system. For example tools like knitr or rapache need to capture stdout to get the output and insert it in a report or webpage. If you really want to, perhaps

Hello dear R developers, I recently found out that it is not possible to limit update.packages() to update only a few packages at a time. The patch offered simply adds a 'subset' parameter and the statement bounded within "if(!missing(subset))" to implement it. The code is pasted bellow (and also attached as an .r file). Might this patch be considered valuable to be added to

In R, there's readline(), which is great because you can prompt the user, e.g. ans <- readline("Would you like to install Pandoc? [y/N]: ") without having to worry the message is intercepted by capture.output(), sink() or similar (which is used by dynamic report generators among other things). The message will always reach the user. (You can use sink(...,

Contrary to other functions in 'base', attach() output messages to stdout instead of stdout, e.g. > a <- 1 > capture.output(attach(list(a=1))) [1] "The following object is masked _by_ .GlobalEnv:" [2] "" [3] " a" Shouldn't this message go to stderr? Here's a patch for the local function checkConflicts() of base::attach(), cf. ditto for

Dear All I'm logging the stdout and stderr of an R program into two separate files (stderr.txt and stdout.txt) using sink() I would like to append extra information such as "date", "memory usage" etc to every line of output that goes to stdout or stderr. For example > cat("hello \n") should give output that looks something like: "hello --- Thu Jun 19

Hello, There appears to be an error in the stderr redirection of the crontab rsync entry. In Bourne shell and compatibles (crontab entries are run by the Bourne shell) redirections are processed from left to right and "2>&1" redirects the stderr to the same location stdout is currently directed and not to stdout. Hence: cmd 2>&1 > log directs stderr to the

I maintain the geometry package, which integrates the Qhull C library (http://qhull.org) into R. The Qhull function I hook into requires an open FILE handle as one of its arguments. I had set this file handle to stdout, but now R check NOTEs the presence of stdout, and the CRAN maintainers asked me to get rid of these NOTEs. Including the following defines means the checks are passed on CRAN:

When the COMMAND_FLAG_FOLD_STDOUT_ON_STDERR flag is passed to command*(), indicate that as stdout=e in debugging message. --- daemon/command.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/daemon/command.c b/daemon/command.c index 73fce56..2423a4e 100644 --- a/daemon/command.c +++ b/daemon/command.c @@ -185,6 +185,7 @@ commandrvf (char **stdoutput, char **stderror,

"Alexander Georgiev" <alexander.georgiev at gmail.com> wrote: > I want to run a rsync-ing script in cron, generating a very verbose > -vv rsync log in a log file. The log file should combine both stderr > and stdin, which is easy: > > backup.sh >>/var/log/backup.log 2>&1 > > However, I would like to propagate only stderr to cron - in case

$ ./nbdkit ssh host=localhost /nosuchfile password=-0 --run 'qemu-img info $nbd' abc fcntl: Bad file descriptor The reason for this is that we close the file descriptor after reading the password. Closing stdin causes bad stuff to happen. --- docs/nbdkit-plugin.pod | 5 +++++ server/public.c | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git

It seems that under Windows, some UTF-8 strings that print OK to stdout do not print correctly to stderr. To reproduce: x <- "\ub124" cat(x, file = stdout()) ## ? cat(x, file = stderr()) ## <U+B124> Original motivating problem here: https://stackoverflow.com/questions/32696241/how-to-display-a-message-warning-error-with-unicode-characters-under-windows How does printing to

Running rsync 3.0.6 on OS X 10.5.7 (on a MacBook Pro) and using the -b flag (and -v --verbose), the "backup_dir" is reported in the output, but sometimes on STDOUT and sometimes somewhere else. Note that the rsync daemon running on the "server" is 2.6.9 (on another MacBook Pro, OS X 10.5.7) For example, in bash, this happens: axe-MBP:bin work$ /usr/local/bin/rsync

Apparent newer versions of that report everything on stdout, including error messages; since we only print something on failure, fold stdout to stderr so we can see everything on failure. --- daemon/xfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daemon/xfs.c b/daemon/xfs.c index abc2736..7f72e6a 100644 --- a/daemon/xfs.c +++ b/daemon/xfs.c @@ -537,7 +537,7 @@

In APIs such as guestfs_download, when the FileOut parameter exactly matches "/dev/stdout" or "/dev/stderr", don't reopen the possibly redirected output file with O_TRUNC (truncate). Instead dup the file descriptor. This magic behaviour doesn't happen for /dev/fd/* (or any other output file) allowing callers the choice of using /dev/stderr or /dev/fd/2 depending on

http://bugzilla.mindrot.org/show_bug.cgi?id=773 Summary: OpenSSH hangs or silently exits on write failure on stdout/stderr Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-bugs

Hello, I also have problems to get to run the following lines. If I run the block instead of every single line, it simply does not wait for the input. Can anybody help me? ------------------------ pos_name <- readline("Please type: ") r <- substr(pos_name, 1,1) c <- substr(pos_name, 2,nchar(pos_name)) ------------------------ Thank you! Antje Peter Dalgaard schrieb: >

I have been losing my mind over this problem, so any ideas are welcome. When running non-interactive jobs on remote machines, I want output to stderr and to stdout to remain separate in two streams just as if they were run locally. I also want jobs running remotely to die when I press Ctrl-C just as if they were run locally. At first glance these do not seem to be mutual exclusive, but when you

https://bugzilla.samba.org/show_bug.cgi?id=4320 Summary: Daemon should send stdout, stderr of {pre,post}-xfer command to client Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi again! While investigating the bug report [*] I found out that on unix, system2 does not quote its `stdin` argument while preparing the command line to launch. It does shQuote the `stdout` and `stderr` arguments, and also the `f <- tmpfile()` variable (which is used if `input` argument is provided), which seems to set a precedent. On Windows, stdin, stdout, and stderr are handled