similar to: [BioC] Suppress output from getGEO

Dear R-ers, I am using getGEO to download expression data from the Gene Expression Omnibus. With default settings, when a file is downloaded and parsed, lots of dotted lines are printed in the terminal, like this: .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... ..........

Rusty, I currently try to make my guest boot from an virtio root device without having an external kernel. Some of the tools that I tried expect HDIO_GETGEO to work. The most interesting value is likely the geo.start value to get the offset of a partition. This value is filled by block/ioctl.c if fops->getgeo is set. This patch also fills in some standard values for heads, sectors and

Rusty, I currently try to make my guest boot from an virtio root device without having an external kernel. Some of the tools that I tried expect HDIO_GETGEO to work. The most interesting value is likely the geo.start value to get the offset of a partition. This value is filled by block/ioctl.c if fops->getgeo is set. This patch also fills in some standard values for heads, sectors and

Hi Jeremy, The below implements the getgeo hook for Xen block devices. Extracted from the xen-unstable tree where it has been used for ages. It is useful to have because it allows things like grub2 (used by the Debian installer images) to work in a guest domain without having to sprinkle Xen specific hacks around the place. Signed-off-by: Ian Campbell <ijc@hellion.org.uk> diff --git

Hi Jeremy, The below implements the getgeo hook for Xen block devices. Extracted from the xen-unstable tree where it has been used for ages. It is useful to have because it allows things like grub2 (used by the Debian installer images) to work in a guest domain without having to sprinkle Xen specific hacks around the place. Signed-off-by: Ian Campbell <ijc@hellion.org.uk> diff --git

Pete Biggs writes: > On Thu, 2020-08-06 at 10:26 +0100, isdtor wrote: > > [root at localhost ~]# lsb_release -d > > Description: CentOS Linux release 8.2.2004 (Core) > > [root at localhost ~]# cat /etc/resolv.conf > > # Generated by NetworkManager > > search subdomain.company.com company.com > > nameserver 1.2.3.4 > > nameserver 5.6.7.8 > >

> > man host > > > > -N ndots > > The number of dots that have to be in name for it to be considered absolute. The default value is that defined using > > the ndots statement in /etc/resolv.conf, or 1 if no ndots statement is present. Names with fewer dots are interpreted > > as relative names and will be searched for in

Hi all, I have been trying to add the line: h = n - p0 + 1; just after h = n / 2 + 1; (line 131) in the source code (the original paper mention this is possible for p0&lt;n). with p0 declared as an int (actually i used the same declaration protocol as n everywhere in the code). The &quot;new&quot; source compiles, but when i give it reasonable values of p0, it runs unto

On Thu, 2020-08-06 at 10:26 +0100, isdtor wrote: > [root at localhost ~]# lsb_release -d > Description: CentOS Linux release 8.2.2004 (Core) > [root at localhost ~]# cat /etc/resolv.conf > # Generated by NetworkManager > search subdomain.company.com company.com > nameserver 1.2.3.4 > nameserver 5.6.7.8 > > [root at localhost ~]# host foo > foo.subdomain.company.com

I have the following contrived code in package format. On Solaris and Mac OS X, code runs just fine. On Windows, it crashes the R environment with the "Send Bug Report" dialog. I tried R 1.8.1 (Win2K) and R 1.9 (WinXP) binaries with the same result. PCs otherwise appear properly configured for creating R packages. Anything blatantly wrong? Suggestions? TIA Relevant files from package

On Sun, 15 Sep 2019, Jan Gorecki wrote: > Dear R-devel community, > > There appears to be an inconsistency in R C API about the exceptions > that can be raised from C code. > Mapping of R C funs to corresponding R functions is as follows. > > error -> stop > warning -> warning > REprintf -> message This is wrong: REpintf is like cat with file = stderr().

You can file it as a wishlist item in the bug trackign system. Without a compelling case or a complete and well tested patch or both I doubt it will rise to the top of anyone's priority list. Best, luke On Sun, 15 Sep 2019, Jan Gorecki wrote: > Thank you Luke for prompt reply. > Is it possible then to request a new function to R C API "message" > that would equivalent to

Dear R-devel community, There appears to be an inconsistency in R C API about the exceptions that can be raised from C code. Mapping of R C funs to corresponding R functions is as follows. error -> stop warning -> warning REprintf -> message Rprintf -> cat Rprint/cat is of course not an exception, I listed it just for completeness. The inconsistency I would like to report is

Full_Name: Russell Senior Version: 0.64.0 OS: linux-2.2.x Submission from: (NULL) (198.107.133.11) It appears that the GNU readline history size is limited to 50 entries. This is apparently occurring because R is not bothering to override the readline default value (from readline-4.0): ./history.c:59:#define DEFAULT_HISTORY_GROW_SIZE 50 It appears that it ought to be possible to override

Thanks - I'll find another way to send messages to the main thread for printing. -Winston On Tue, Nov 21, 2017 at 12:42 PM, <luke-tierney at uiowa.edu> wrote: > On Tue, 21 Nov 2017, Winston Chang wrote: > >> Is it safe to call Rprintf and REprintf from a background thread? I'm >> working on a package that makes calls to fprintf(stderr, ...) on a >>

Thank you Luke for prompt reply. Is it possible then to request a new function to R C API "message" that would equivalent to R "message" function? Similarly as we now have C "warning" and C "error" functions. Best, Jan On Sun, Sep 15, 2019 at 5:25 PM Tierney, Luke <luke-tierney at uiowa.edu> wrote: > > On Sun, 15 Sep 2019, Jan Gorecki wrote:

Is it safe to call Rprintf and REprintf from a background thread? I'm working on a package that makes calls to fprintf(stderr, ...) on a background thread when errors happen, but when I run R CMD check, it says: Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor the system RNG. Is it safe to replace these calls

Hello, I am trying to download a SOFT matrix file for GSE series to extract raw intensity data. gse<- getGEO('GSExxxx', AnnotGPL=T) However, I am not able to use the function Table(gse), which returns the following error >>>Error in function (classes, fdef, mtable) : unable to find an inherited method for function "Table", for signature "GSE" If I

In some code that I have written, use of url() is generating the output line: "cannot open: HTTP status was `404 Not Found`" The problem is that I do not want R to be outputting any error messages - I have 'internet.info' set to 3, show.error.messages set to FALSE and the url() wrapped in a try(). When the URL is not found I am already handling it in a manner consistent with

Hi all, I'm working on a GUI frontend for R, and I'm looking for a good way to catch all warning- and error-output. The reason for this is mostly, that I would like to know, which sections of the output are "normal" output, warnings, and errors. This would allow for some nice features, such as highlighting warnings and errors in a different color, or popping up a message