Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better relative paths handling and returning more useful values from API #103

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Conversation

mirlord
Copy link

@mirlord mirlord commented Jul 30, 2013

I'm not sure that a suggested fallback from incubate to surround will work on windows, but looks logically.

Returning path lists, that were just loaded, is very useful for plugins, that use pathogen's internal API. i.e. I've created my own vim-profiles plugin, that uses this feature. Also vim-ipi may benefit from this change, since now it is forced to make extra rtp value comparison before and after pathogen invocation to detect loaded plugins.

Vladimir Chizhov added 3 commits July 31, 2013 03:34
Nested paths like 'bundle/public/{}' (containing more than one path
separator) were not detected as relative. Thus they were passed to
`surround`, instead of `incubate`.
If pathogen#incubate() was called for a non-default relative path and
nothing was found in runtimepath - it will "fallback" to
pathogen#surround(). It will also protect absolute/relative path
detection logic from failing on some platforms, like windows.
@tpope
Copy link
Owner

tpope commented Aug 1, 2013

Official interface is execute pathogen#infect(). The idea was that a future version might return VimL to be executed in the context of one's vimrc. I'll think further on allowing this for pathogen#incubate() and the like but pathogen#infect() is off the table.

@mirlord
Copy link
Author

mirlord commented Aug 1, 2013

  1. What's the problem to extend a returned object with VimL or anything else later?
  2. So I'll wait for your decision on pathogen#surround() and pathogen#incubate() return values. Please provide me your opinion on how to fix pathogen#infect() to keep it aligned with your roadmap view. For my own needs - it's ok to use them directly, passing pathogen#infect(), so it's ok for me just to revert the returned value of pathogen#infect() to an empty string.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants