similar to: readline/history size (PR#211)

Hiall, I have the following problem: I need to use forms containing collections (i will call them FCC), and I want to construct them dynamically, as I need to deal with quite large forms (more than 600 input fields). The variables @model_name and @field_name contain the proper model and field names as strings, which is enough for "normal" form input fields. (i.e. the "if

Dear Prof. Roger Koenker, On Tue, 22 Oct 2024 09:08:12 +0000 "Koenker, Roger W" <rkoenker at illinois.edu> wrote: > > fN <- rqss(y~qss(x,constraint="N")+z) > > *** caught segfault *** > address 0x0, cause 'invalid permissions? Given a freshly produced quantreg.Rcheck directory, I was able to reproduce this crash by running R -d gdb # make

Dear all, I am still trying to find out what goes wrong when I use ace (I get an 'NAs in foreign fuction call (arg3)' but when I go through it with debug there seem no data to be missing). I had some errors (see at end of message) while installing 'acepack'. Do you think it is possible that these lead to the fact, that simple problems run ok but larger problems result in an

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

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

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:

Hi, I'm trying to compile two functions into one function. the first funtion is called 'fs' which is self-made function, another function is from the built-in 'integration' function that is copy-paste-edited. If built separatey, these functions work well. However that is not the case if combines together, where certainly I made mistake somewhere when constructing the code.

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

Hey all, I have ssh-askpass installed on Centos 5.7 and I'm trying to find a way to log into the host and not have it ask me to enter in my long / complex passphrase every time I ssh into another host. I've googled for some scripts that you can add to your bash configuration so that you won't have to do that. So I have to end up typing 'eval $(ssh-agent) &&

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

I've only been using R on and off for 9 months and started using the glasso package for sparse covariance estimation. I know the concept is to shrink some of the elements of the covariance matrix to zero. However, say I have a dataset that I know has some underlying "baseline" covariance/correlation (say, a value of 0.3), how can I change or incorporate that into to the

Hi all, While compiling R to RISC-V64 architecture and debugging in R's C source codes, I think I have found a small bug. Can anyone please verify whether it is a real bug? The possible bug lies in the file `R-4.2.2/src/library/stats/src/approx.c` in function `R_approxfun` around line 148: #ifdef DEBUG_approx REprintf("R_approxfun(x,y, nxy = %.0f, .., nout = %.0f, method = %d,

some time ago i communicated the same issue to sean, and i'm very glad he has improved the package -- thanks! i'm purposefully posting to r-devel rather than to bioconductor. i think that download.file could be improved to avoid this sort of spamming output seen previously with getGEO. currently, it prints dots (when it does) in 5 10-packs per line, line after line. instead, it could

I have a problem to understand the way gc_inhibit_torture is defined. In include/Defn.h it is declared as extern, using the __MAIN__ trick this leads to a definition in main/main.c. But in main/memory.c you define (and initialize) gc_inhibit_torture again: int gc_inhibit_torture = 1; /* gets set to zero after initialisations */ Then, in e.g. unix/system.c immediately at the beginning of

Hi, I am trying to estimate a quantile regression using panel data. I am trying to use the model that is described in Dr. Koenker's article. So I use the code the that is posted in the following link: http://www.econ.uiuc.edu/~roger/research/panel/rq.fit.panel.R This code run perfectly. Then I want to know what the result means.The result show $ierr,$it,and $time. What these estimators