org-projectile:known-projects shouldn't load remote projects #10
Comments
I feel like this is more of an issue with projectile than with org-projectile. You should have the same issue when switchign to a project wiht projectile. |
projectile does not acess the path until I pick it, it uses the list on purely textual basis. I didn't read the code but it never asked me for remote ssh password (unless I actually picked remote project). |
I see. I think that the password prompts come from when we run file-truename on the path. This is still something I would like to do, but ill try to come up with a way to avoid this. |
@Mekk I added an option that is enabled by default that skips over projects that require any special access. Things should work now. |
sdwolfz
added a commit
to syl20bnr/spacemacs
that referenced
this issue
Jan 20, 2019
According to org-projectile's repo, this bug has been fixed: IvanMalison/org-projectile#10 Recommending the reference be removed from the documentation.
vv111y
added a commit
to vv111y/spacemacs
that referenced
this issue
Jan 21, 2019
According to org-projectile's repo, this bug has been fixed: IvanMalison/org-projectile#10 Recommending the reference be removed from the documentation.
billy1kaplan
added a commit
to billy1kaplan/spacemacs
that referenced
this issue
Apr 19, 2019
According to org-projectile's repo, this bug has been fixed: IvanMalison/org-projectile#10 Recommending the reference be removed from the documentation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My attempts to call
org-projectile:project-todo-completing-read
take long time, ask passwords (and then end up in crash which may be related, or not). The reason is that they include remote (scp) paths for remote repositories I happened to open in the past.There are two parts of this issue:
projectile-project-root-cache
has more than hundred items including more than 10 remote (tramp) itemsThe text was updated successfully, but these errors were encountered: