Thanks for your help - that was the solution (easy enough to remove these two
characters - they've been in only comments anyway).
Fortunately, the DECRIPTION file accepts umlauts, as in my second name. The
problem was only in the source file.
Felix
Am 26.02.2010 um 18:37 schrieb Duncan Murdoch
Added one other comment below.
On Fri, Feb 26, 2010 at 9:41 PM, Gabor Grothendieck
wrote:
> On Fri, Feb 26, 2010 at 8:46 PM, Ben wrote:
>> Maybe I'm still not getting something fundamental, but I didn't intend
>
> I think you are missing the R search path. Try this:
>
> search()
>
> That shows
On Fri, Feb 26, 2010 at 8:46 PM, Ben wrote:
> Maybe I'm still not getting something fundamental, but I didn't intend
I think you are missing the R search path. Try this:
search()
That shows you the search path. Normally it starts searching at the
beginning and moves forward.
> my "proto(base
On Mon, Feb 22, 2010 at 01:14:51PM +0100, Peter Dalgaard wrote:
Hi Peter,
sorry for the later answer - had to finish other tasks first :(
> I played around with inkscape again (& it IS a time sink...) The
> attached version is around 200K and not too bad looking to my eyes. How
> does it work
G'day Uwe,
On Fri, 26 Feb 2010 17:03:10 +0100
Uwe Ligges wrote:
> R CMD check executes the R code in the vignettes and checks if that
> works, and it checks if the PDFs are available. It does not check if
> it can build the vignettes, because that is only necessary on the
> maintainer's machin
Maybe I'm still not getting something fundamental, but I didn't intend
my "proto(baseenv(), expr={a <- z})$a" example to be realistic. In
practice "a <- z" would be replaced with hundreds of lines of code,
where many functions are called. In theory you could track down every
function that's globa
Announce
Special issue of the Journal of Statistical Software on
Graphical User Interfaces for R
Editors: Pedro Valero-Mora and Ruben Ledesma
Since it original paper from Gentleman and Ihaka was published, R has
managed to gain an ever-increasing percentage of academic and
professional statis
[cc'ing back to r-devel]
Maria Rizzo wrote:
> Ben,
>
> I receive the digest version of r-devel - so I do not have the
> individual messages to reply to. In reply to yours:
>
> I think this is a bug for the following reasons. While it is true
> that one can define a scale factor differently fo
On 26/02/2010 11:05 AM, Felix Schönbrodt wrote:
Hi Duncan,
I now declared the endcoding in the DESCRIPTION to UTF-8 (and all files are encoded in
that way, too). As my last name is "Schönbrodt", I'd be happy to see it that
way in the package ;-)
However, it still doesn't build on Windows (but
You can work around this by disabling large file support (configure
--disable-largefile).
This seems to be another glibc bug. In the header glob.h, there are two
lines where the pre-processor fails to check that __GNUC__ is defined,
and it isn't defined when using Sun Studio.
Evidently, glibc was
R CMD check executes the R code in the vignettes and checks if that
works, and it checks if the PDFs are available. It does not check if it
can build the vignettes, because that is only necessary on the
maintainer's machine since the PDFs are shipped with the (built) source
package.
Best,
U
On 26.02.2010 12:03, Ian Thurlbeck wrote:
Dear All
We have noticed a problem when cut-and-pasting a largish section
(> 4096 bytes ?) of R code from an editor to an R session.
It is a bad idea to do that in any case.
If you have such huge data or code, save the data / code to a file and
rea
(forwarding to R-devel)
Prof. Ripley
Thanks a lot for the help.
I greatly appreciate the clarification that R does indeed install the
package during the build process. I must have been confused. The
error is now fixed and was not related to my (false) claim that R
could not locate a dataset in
On Fri, Feb 26, 2010 at 9:01 AM, Ben wrote:
>
>> In end it seems that your real beef is with R so perhaps you should
>> be using a different language.
>
> In my case you may be right. I do think there are a million things
> wrong with R. For instance, I was looking for a package that
> overcomes
On 26/02/2010 8:52 AM, Felix Schönbrodt wrote:
Dear developers,
while our package TripleR (hosted on R-Forge) builds well on Mac and Linux, the Windows
build shows following error
(http://r-forge.r-project.org/R/?group_id=418&log=build_win32&pkg=TripleR&flavor=patched):
Fri Feb 26 00:53:38 20
> In end it seems that your real beef is with R so perhaps you should
> be using a different language.
In my case you may be right. I do think there are a million things
wrong with R. For instance, I was looking for a package that
overcomes two of the problems R IMHO has: namespace pollution an
Dear developers,
while our package TripleR (hosted on R-Forge) builds well on Mac and Linux, the
Windows build shows following error
(http://r-forge.r-project.org/R/?group_id=418&log=build_win32&pkg=TripleR&flavor=patched):
Fri Feb 26 00:53:38 2010: Building binary for package TripleR (SVN revi
Dear All
We have noticed a problem when cut-and-pasting a largish section
(> 4096 bytes ?) of R code from an editor to an R session.
System is Fedora 12 i386 with updates, R-2.9.0 and R-2.10.1 at least.
Problem disappears if you start R with --no-readline !
If happens independently of the edi
On 26/02/2010 7:09 AM, Gabor Grothendieck wrote:
On Fri, Feb 26, 2010 at 12:41 AM, Peter Danenberg wrote:
Also other object systems which are alternatives to proto seem less
relevant than basic scoping and free variable lookup in functions.
Sorry, but that seems absurd; object systems are less
On Fri, Feb 26, 2010 at 12:41 AM, Peter Danenberg wrote:
>> Also other object systems which are alternatives to proto seem less
>> relevant than basic scoping and free variable lookup in functions.
>
> Sorry, but that seems absurd; object systems are less relevant to each
> other than the totally
20 matches
Mail list logo
