hi, Am Mittwoch, 16. August 2017, 20:07:24 CEST schrieb Pierre de Villemereuil: > You obviously know this stuff better than I do. I guess it's good news my > concerns where misplaced! ;)
let's see what thomas makes out of it all :-D > > because the current working directory doesn't make much sense, as you > > usually don't start RKWard from a particular/changing working directory. > > Well I do, because I usually start it by opening a script, but that's below > the point... Especially since, in my workflow, the script is what matters > and I'm not particularly attached to the workspace (quite impossible to > work like that with RStudio for example...). i think RKWard ignores workspaces in the directory where you think you're launching it, because it has its own working directory configured. but you can of course launch it with a particular R script. in KDE, klicking on an R script should actually open it in RKWard by default. > > RKWard overrides some (very few) R core functions. in this case it's > > likely > > because it depends on a running R session in the backend, so a user > > shouldn't be able so simply call q() and crash the application ;-) > > I actually never tried. Just did and right now it's calling the dialog > Save/Discard/Don't quit. I guess that's what you mean when you that q() is > overridden. yes, you can check yourself: just call "q" (without the brackets) to see the code, and it should tell you that the function is from namespace "rkward". viele grüße :: m.eik -- dipl. psych. meik michalke institut f"ur experimentelle psychologie abt. f"ur diagnostik und differentielle psychologie heinrich-heine-universit"at d-40204 d"usseldorf
signature.asc
Description: This is a digitally signed message part.
