Add support for vscDebugger

[bersbersbers]

whereami::thisfile() returns NULL when debugging code using https://github.com/ManuelHentschel/vscDebugger.

I see a couple of options:

1. Relax the check at

   whereami/R/thisfile.R

   Line 72 in 64ee46b

   if (identical(args(sys.function(i)), args(base::source))) {

2. Include this check:

if (exists(".vsc.getSession")) {
    .vsc.getSession()$file
}

[yonicd]

thanks for opening this issue. i will try to get to it this week.

[yonicd]

what is the expected result? if i add .vsc.getSession()$file i get main.R in the debug console

[bersbersbers]

what is the expected result? if i add .vsc.getSession()$file i get main.R in the debug console

It depends on the context, I guess. In interactive R.exe, I get this:

> .vsc.getSession()$file
Error in .vsc.getSession() : could not find function ".vsc.getSession"
> library(vscDebugger)
> .vsc.getSession()$file
[1] ""

which is expected, I guess. The same is true in plain Rscript.exe:

C:\Users\bers>echo library(vscDebugger);print(.vsc.getSession()$file) > test.R && Rscript test.R
[1] ""

because we are not using vscDebugger for debugging.

By contrast, when debugging, in VS Code using https://github.com/ManuelHentschel/VSCode-R-Debugger, D:\testing.R which contains only

print(.vsc.getSession()$file)

the output is (correctly)

[1] "D:\\testing.R"

[ColinFay]

Was coming here to post that we need VSCode support :)

whereami::whereami()

is empty when run from VSCode.

[ColinFay]

Note: on modern version of the R VSCode extension, there are wrappers around rstudioapi, so you can do rstudioapi::getActiveDocumentContext()$path inside VSCode

[yonicd]

are we sure it isnt working?

[bersbersbers]

Yes, we are sure it's not working ;) because this issue is about whereami::thisfile(), not whereami::whereami():

Or am I wrong in expecting that whereami::thisfile() should return something useful here?

[bersbersbers]

Here's something else which is weird:

While .whereami and .thisfile have the same body, they behave differently.

[yonicd]

not sure why you are using whereami::thisfile the function itself should return NULL since it doesn't answer any of the checks that it is intended to look at.

whereami::whereami is the right choice when running interactively, and even then if it is not interactive under the hood it is falling back to thisfile.

[yonicd]

what is the usecase of print(whereami)? there is already a function for this called whereami::cat_where

[bersbersbers]

not sure why you are using whereami::thisfile

Because whereami::whereami does not return a filename, but some object that I would have to extract the filename from.

the function itself should return NULL since it doesn't answer any of the checks that it is intended to look at.

That is good to know - it wasn't clear from the reference manual.

whereami::whereami is the right choice when running interactively

I am not working interactively, unfortunarely.

and even then if it is not interactive under the hood it is falling back to thisfile.

True, but not completely, as shown above in my first example above.

what is the usecase of print(whereami)? there is already a function for this called whereami::cat_where

This is only an example to simulate what happens when the return value is captured in a variable. I usually do something like setwd(dirname(whereami::thisfile())).