Yeah, we should do that.

…

On Mon, Oct 15, 2018 at 3:41 PM Kevin S. Van Horn ***@***.***> wrote: I think I found the cause. Technically, it's not a bug, just a seriously user-hostile behavior. First of all, the problem wasn't in the directory claimed to be the problem -- it was in an *ancestor* directory, specifically my user home directory. It took a lot of experimentation, and looking at the actual package code, to figure this out. Secondly, once I had determined that there must be something in my home directory that was making it think it was a project root, it still took at least another half an hour to 45 minutes to find the cause. I deleted every file or directory I could find that started with ".R", and that still didn't solve the problem; eventually I found a "vanhorn.Rproj" file that I had overlooked. So why couldn't the function tell me this upfront? A simple message saying "/Users/vanhorn/ is a package root -- file /Users/vanhorn/vanhorn.proj found" would have saved me a huge amount of time and frustration. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#42 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADOrqhRcwSeqP244L7m3dHP0SVW4OuLwks5ulOUEgaJpZM4XczAT> .

rstan_package_skeleton thinks every directory is an existing project directory #42

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions