You are correct, it most definitely is a convoluted way to identify a path,
but this is one incredibly specific scenario. The case I'm talking about
only occurs when running a script in Rgui for Windows using Ctrl+R (or
pasting into the R Console) to run a piece of code. Scenarios such as
running f
Expecting a window handle relevant to the script to exist for the purpose of
identifying a path seem to be orthogonal problems to me. But Andrew has
indicated offlist that he has alternate code for other cases only uses this
technique when appropriate.
I still feel this is too convoluted as a w
I don't have cigwin installed but from the command window, the terminal
that Git installs, RGui, and RStudio they all return "windows" for the
.Platform$OS.type for me.
On Thu, Sep 30, 2021 at 2:38 PM Duncan Murdoch
wrote:
> On 30/09/2021 5:21 p.m., Jeff Newmiller wrote:
> > What if you are on W
On 30/09/2021 5:21 p.m., Jeff Newmiller wrote:
What if you are on Windows but running R at the command prompt, or via cygwin,
or in the console window of RStudio?
This seems unstable to me.
Sorry, too much context missing. What's unstable?
Duncan Murdoch
On September 30, 2021 11:52:16 AM
What if you are on Windows but running R at the command prompt, or via cygwin,
or in the console window of RStudio?
This seems unstable to me.
On September 30, 2021 11:52:16 AM PDT, Andrew Simmons
wrote:
>Hello,
>
>
>I'm updating my package 'this.path' which is supposed to retrieve the
>absolu
Hello,
I'm updating my package 'this.path' which is supposed to retrieve the
absolute path of the executing script when called. It's similar to 'here',
except that 'here' constructs paths relative to a project directory,
whereas 'this.path' constructs paths relative to script directories. I was
u
On Fri, 24 Sep 2021 21:48:12 +0200
Jan van der Laan wrote:
> my tests run fine when run with R CMD check, but not with R CMD check
> --as-cran
<...>
> pandoc then calls R again with a script which is part of the package
Part of R CMD check --as-cran is placing fake R and Rscript executables
on
Returning to the original question, if it's helpful: I'd like to know what
constraints led to considering an export only available on Windows, and see
if we can suggest some other designs. It'd be good to keep the user's
mental model abstracted from the platform they're working on. There are
often
One of the very best fortunes nominations!
[...]
I suspect something like
if (stats::runif(1) > 0.5) export(someFunction)
would work too, for a particularly frustrating experience for your
users. It would mean half the installs export the function, and half don't.
Duncan Murdoch
