On Thu, Mar 16, 2023 at 6:39 PM Dirk Eddelbuettel wrote:
>
>
> On 16 March 2023 at 17:15, Henrik Bengtsson wrote:
> | We're all starting out with a fresh R_LIBS_USER once a year when a new
> | minor version of R is released,
>
> Maybe not "we all". I don't, and I know other Linux users who don't f
Hmm ... I can no longer reproduce this under r83996 when configuring
--without-lapack and --without-blas {the default}. Now det(A), det(B),
det(C), and det(D) are all NaN.
I assume that the reason is the recent update to use LAPACK 3.11.0?
But I don't see any related NEWS here:
https://netl
On Thu, Mar 16, 2023 at 4:08 PM Dirk Eddelbuettel wrote:
>
>
> On 16 March 2023 at 13:39, Felipe Contreras wrote:
> | I see R by default installs packages in ~/R. I know I can change the
> | default directory with R_LIBS_USER, but software shouldn't be
> | polluting the home directory.
> |
> | For
On 16 March 2023 at 17:15, Henrik Bengtsson wrote:
| We're all starting out with a fresh R_LIBS_USER once a year when a new
| minor version of R is released,
Maybe not "we all". I don't, and I know other Linux users who don't force a
rebuild unless needed (as with R 3.6.* -> R 4.0.0).
R signals
> Your best bet really to govern your .libPaths from your Rprofile.site and
Renviron.site ...
To do this for any version of R, one can add:
R_LIBS_USER=~/.local/share/R/%p-library/%v
to ~/.Renviron or the Renviron.site file. This automatically expands
to the platform and R x.y version early on w
On 16 March 2023 at 13:39, Felipe Contreras wrote:
| I see R by default installs packages in ~/R. I know I can change the
| default directory with R_LIBS_USER, but software shouldn't be
| polluting the home directory.
|
| For example both python and node install packages to ~/.local/lib,
| ruby
Hi,
I see R by default installs packages in ~/R. I know I can change the
default directory with R_LIBS_USER, but software shouldn't be
polluting the home directory.
For example both python and node install packages to ~/.local/lib,
ruby to ~/.local/share. They don't install to for example ~/node.
Hi,
There are a limited number of MIME file types that are accepted through the
list server, with plain text being one. Even though a patch file should be
plain text, it is possible that your mail client may not have set the correct
MIME type for your patch file attachment. If so, that would ex
People have let me know that the attachment didn't make it through.
Do patches get filtered out?
Please find it there:
https://github.com/lionel-/r-svn/commit/e3de56798b1321a3fa8688a42bbb73d763b78024.patch
I'm also happy to post it on the bugzilla if that makes sense.
Best,
Lionel
On 3/16/23, L
Hello Lionel,
Just letting you know off-list that the patch didn't make it through.
Unfortunately, I don't remember the exact rules regarding attachments
(does text/plain work?), but an external link is always an option,
especially for large patches.
--
Best regards,
Ivan
__
Hello,
We've run into this issue multiple times and it's often a head
scratcher when it happens. We are using workarounds but it would be
great to fix this for R 4.3. Would an R core member have time to
review the patch that we supplied in
https://bugs.r-project.org/show_bug.cgi?id=18489 ?
Best,
Hello,
I started using clangd to get better static analysis and code
refactoring tooling with the R sources (using eglot-mode in Emacs, it
just works once you've generated a `compile_commands.json` file with
`bear make all`). I noticed that the static analyser can't understand
several header files
12 matches
Mail list logo
