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.

Sign up for GitHub

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

Jump to bottom

Missing jedi-vim Keymaps #255

Closed
legout opened this issue Apr 19, 2013 · 6 comments
Closed

Missing jedi-vim Keymaps #255

legout opened this issue Apr 19, 2013 · 6 comments

Comments

@legout
Copy link

legout commented Apr 19, 2013

Hi,

I recently switched from jedi-vim to YCM. I´m missing jedi-vim keymaps for goto, rename, get_definition and related_names. At least, the keycaps defined in my .vimrc won´t work.

And hints?

Thanks
Volker
@Valloric
Copy link
Member

You can't use those keymaps because those features haven't yet been implemented. Even then, the command names will be different.

@Julian
Copy link

Julian commented May 2, 2013

Why does this require any integration in YCM to just work as it does in Jedi?

@jck
Copy link

jck commented May 8, 2013

What is the preffered way to accesss those commands? Should we install jedi-vim in addition to YCM?

@JazzCore
Copy link
Contributor

JazzCore commented May 8, 2013

YCM now has a support for jedi goto functions, pull latest changes and check the doc section about it. Refactorings isnt here at the moment. I can make them, @Valloric, whats your opinion? They can also be implemented as a subcommands,

@Valloric
Copy link
Member

Valloric commented May 8, 2013

Refactorings should be implemented as subcommands of the completer, yes.

@chtenb chtenb mentioned this issue May 8, 2013
Closed
@dbrgn
Copy link

dbrgn commented Jul 23, 2013

Any news for the rename functionality? :)

bijancn pushed a commit to bijancn/YouCompleteMe that referenced this issue Jul 26, 2016
@homu
Auto merge of ycm-core#255 - Andersbakken:master, r=Valloric
ba4ac8f 
clang_reparseTranslationUnit takes CXReparse_Flags, not CXTranslation…

Currently there's no flags even existing so one could argue whether it makes sense to incur the extra mutex lock but I didn't want to change anymore than necessary.

<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/valloric/ycmd/255)
<!-- Reviewable:end -->
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@dbrgn @jck @Julian @Valloric @JazzCore @legout