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

Complete command use #86

Closed
mttcrsp opened this issue Nov 5, 2015 · 4 comments
Closed

Complete command use #86

mttcrsp opened this issue Nov 5, 2015 · 4 comments

Comments

@mttcrsp
Copy link

mttcrsp commented Nov 5, 2015

I'm having troubles using the complete command:

  • every time I try to use it with the --file argument I get a Failed to read file at ... error, while the syntax command works just fine on the same file;
  • completion results do not always show up, as an example: sourcekitten complete --text "[1].m" --offset 4 works just fine and shows all of the available options, sourcekitten complete --text "[1].m" --offset 5 returns an empty array while it should return an option for the map function.

Loving the project.

(SourceKitten 0.5.0 installed via Homebrew, Xcode 7.1)

severalregularfoxterrier

@jpsim
Copy link
Owner

jpsim commented Nov 5, 2015

The complete command expects absolute paths to the file. that's less than ideal and I should improve that so it supports relative paths.

@jpsim
Copy link
Owner

jpsim commented Nov 5, 2015

completion results do not always show up, as an example: sourcekitten complete --text "[1].m" --offset 4 works just fine and shows all of the available options, sourcekitten complete --text "[1].m" --offset 5 returns an empty array while it should return an option for the map function.

This is actually a limitation in how SourceKit generates completion requests, so there's not much I can do for you there.

@mttcrsp
Copy link
Author

mttcrsp commented Nov 5, 2015

Ok, thanks for the immediate feedback! 👍

@jpsim
Copy link
Owner

jpsim commented Nov 17, 2015

SourceKitten handles relative paths much better now thanks to #101.

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

No branches or pull requests

2 participants