similar to: Environment variable MAKE not defined on Windows

Hi, On both Unix and Windows there is a mechanism to add variables to the environment when R is started. I noticed that, on Unix, this mechanism is not used when R is started normally at the command line but only when it's started using the 'R CMD' syntax. One problem with this is some lack of consistent cross-platform behaviour. For example: On Linux: $ echo $TEXINPUTS $

/Hello. SUMMARY: $ BOOM=$'\xFF' LC_ALL=en_US.UTF-8 Rscript --vanilla -e "Sys.getenv()" Error in substring(x, m + 1L) : invalid multibyte string at '<ff>' $ BOOM=$'\xFF' LC_ALL=en_US.UTF-8 Rscript --vanilla -e "Sys.getenv('BOOM')" [1] "\xff" BACKGROUND: I launch R through an Son of Grid Engine (SGE) scheduler, where the R

> On 31 Jan 2023, at 12:51 , Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > > On 1/31/23 11:50, Martin Maechler wrote: <snippage> >> hmm.., that's a pity; I had hoped it was a pragmatic and valid strategy, >> but of course you are right that type stability is really a >> valid goal.... >> >> In general, what about behaving close

Ok, thanks! I'm not dealing with UTF-8 so I don't think Process::GetEnv will work. I was looking for something that caches calls to getenv so checks could be put into tight(-ish) loops without too much performance impact. Would such a utility be of interest to the community? -David Reid Kleckner via llvm-dev <llvm-dev at lists.llvm.org> writes: >

Tomas, I think you're not addressing the actual issue which is a clear regression in Sys.getenv() [because it used to work and still works for single env var, but not a list] and the cryptic error due to that regression (caused by changes in R-devel). So in either case, Sys.getenv needs fixing (i.e., this should really go to the bugzilla). Its behavior is currently inconsistent. The quoted

In a package 'vig' R CMD build vig (or tools::buildVignettes(dir="vig") with $ cat vig/vignettes/vig1.Rnw \documentclass{article} \begin{document} <<>>= x <- 1 @ \end{document} $ cat vig/vignettes/vig2.Rnw \documentclass{article} \begin{document} <<>>= x @ \end{document} produces vig2.pdf where x is defined with value 1 -- the vignettes share a build

getenv(<varname>) currently returns "" if the <varname> is undefined. However, if <varname> is defined but empty, getenv(<varname>) still only returns "". I think this is quite unfortunate but consistent with the prototype. --- I'd propose to change the current behavior. Something which should be pretty back compatible would for the first

Hello! I want to detect some environment on a remote host (in C program, getenv()), but it is failed. Here is a little program which I try to run on a remote host with command: "#ssh myhost myecho" /* myecho */ #include <stdio.h> main (){ char *dir; if ((dir = getenv("MYDIR")) != NULL) printf ("environment is %s\n",dir);

Yes, but in your example getenv is called every time enableFooBar needs to be initialized. What if your code is itself wrapped inside another loop you can't see (for example, the PassManager invoking passes)? Maybe I'm being overly pedantic. We use a lot of environment variables in our compiler because it's really super annoying and takes a lot of developer time to have to update

Env vars that change compiler output make it impossible to write tools such as ccache or distcc. Including the entire env in the hash value that determines whether ccache has a cache hit (as well as the compiler command line and the preprocessed source file) would be ridiculous and would result in very few cache hits. On Thu, Sep 6, 2018 at 11:34 AM, Matthias Braun via llvm-dev < llvm-dev at

Is there an LLVM-ish way to handle environment variables? Specifically, I want to check existence and/or value of an environment variable and take appropriate action. I was kind of surprised that LLVM doesn't seem to have any special/optimized way to deal with environment variables. The one Stackoverflow I found on it suggested using getenv(). Thanks! -David

To R-devel, In `R CMD build`, the ID of the user is automatically inserted into the DESCRIPTION file, e.g. Packaged: 2018-11-06 14:01:50 UTC; <MY USER ID> This is problematic for those of us who work in corporate settings. We must not divulge our user IDs in the packages we develop and release. Jim Hester pointed out that these two lines in `add_build_stamp_to_description_file()`

>>>>> Tomas Kalibera >>>>> on Tue, 31 Jan 2023 10:53:21 +0100 writes: > On 1/31/23 09:48, Ivan Krylov wrote: >> Can we use the "bytes" encoding for such environment variables invalid >> in the current locale? The following patch preserves CE_NATIVE for >> strings valid in the current UTF-8 or multibyte locale (or

Hi Martin, It is really a 'PATH' problem. After adding C:\Program Files\Graphviz2.20\bin to the 'PATH' environment variable, the Rgraphviz package can be loaded without any error messages. Sorry that I ONLY set my 'PATH' environment variable correctly for R but not for Graphviz. Thank you and Duncan so much for your great help. Howard On Tue Mar 30 18:12:54

Thanks, Kurt. I think I now have enough time to write a patch. What are the steps? I have read https://www.r-project.org/bugs.html#how-to-submit-patches but I do not seem to have permission to create a Bugzilla account at https://bugs.r-project.org/bugzilla/. Will On Mon, Nov 12, 2018 at 2:46 AM Kurt Hornik <Kurt.Hornik at wu.ac.at> wrote: > >>>>> Will L writes: >

In trying to change the driver used by Sweave on the command line using R CMD Sweave --driver=foo I consistently get the "directory 'foo' does not exist' error. (For any value of 'foo', even the default 'RweaveLatex'.) Looking up the source code for function .Sweave that is called by 'R CMD Sweave', I notice that the argument 'driver', if

I've recently been trying to run the United Devices THINK agent under wine. On installation, all was going well until the registration process tried to connect to the UD server, when it failed to establish contact. Investigation of the debug messages revealed that it was getting the address to contact vi a call into msvcrt.getenv() which was returning the value "C:\WINDOWS" for all

On 1/31/23 09:48, Ivan Krylov wrote: > Can we use the "bytes" encoding for such environment variables invalid > in the current locale? The following patch preserves CE_NATIVE for > strings valid in the current UTF-8 or multibyte locale (or > non-multibyte strings) but sets CE_BYTES for those that are invalid: > > Index: src/main/sysutils.c >

I'm using R 1.6.1 on Windows 95 with cygwin bash as my shell. The 'shell' command tries to determine which shell the user prefers via the following steps: shell <- Sys.getenv("R_SHELL") if (!nchar(shell)) shell <- Sys.getenv("SHELL") if (!nchar(shell)) shell <- Sys.getenv("COMSPEC") For me, shell

Right. glibc's amusing stance is that you setenv/putenv are not thread safe, but getenv is. I assume Ruby exposes setenv and therefore simply not calling setenv isn't an option. Would it solve your problems if all getenv() calls happened at cl::ParseCommandLineOptions() time? On Thu, May 23, 2013 at 9:49 AM, Dirkjan Bussink <d.bussink at gmail.com>wrote: > Hello, > >