You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rperl command appears to create the _Inline directory in the current working directory and doesn't clean this up. This is OK if I am my source code directory; however, when I run "rperl -v" from my home directory, I don't care for it creating _Inline there.
While I am still an rperl infant, my gut check would be to use the Inline directory keyword and force the default to either ~/.Inline on the Unices or preferably ~/.local/share/rperl/Inline. On Windows, this should in the %HOME% directory and created with the hidden flag set.
This would put the responsibility on the developer to place this elsewhere during the development cycle or possibly as part of an install package if the developer had a reason not to use the default.
Thanks,
lbe
The text was updated successfully, but these errors were encountered:
@lbe
Yes I am more than happy to have your help dealing with this often-annoying issue of the automatically-created _Inline/ directories. As mentioned in my previous comment, please review the instructions in the CONTRIBUTING file so that we can set you up as an RPerl contributor:
The rperl command appears to create the _Inline directory in the current working directory and doesn't clean this up. This is OK if I am my source code directory; however, when I run "rperl -v" from my home directory, I don't care for it creating _Inline there.
While I am still an rperl infant, my gut check would be to use the Inline directory keyword and force the default to either ~/.Inline on the Unices or preferably ~/.local/share/rperl/Inline. On Windows, this should in the %HOME% directory and created with the hidden flag set.
This would put the responsibility on the developer to place this elsewhere during the development cycle or possibly as part of an install package if the developer had a reason not to use the default.
Thanks,
lbe
The text was updated successfully, but these errors were encountered: