How to play more nicely with file path expansion? #7
Comments
I think you can still use the path as one single string in |
Would such paths retain portability to, say, Windows? I guess I’ve always assumed that separate parts was a best practice, but maybe it is unnecessary. |
Windows accept slashes, mostly. In my experience, problems arise if they get converted to backslashes and you try to compare paths and find they're different even if they are the same. So, code that works on Linux/OS X may fail on Windows. I just checked, |
- More explicit documentation for the `...` argument to `here()` (#7).
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary. |
In a recent twitter-storm about project-based thinking and file paths, a really good point was raised that I too have felt (sorry, I can't find the tweet now).
RStudio, for example, does tab completion on filenames within a Project, which is very handy.
But then
here::here()
expects the path parts separated out into a character vector.Is there a way to have our cake and eat it too? Could the relative paths produced by RStudio be acceptable to
here::here()
? Or could there be a helper function or add-in that converts these easy-to-get paths into the proper form?The text was updated successfully, but these errors were encountered: