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

How to incorporate semantic trigger/custom syntax completer? #444

Open
LindyBalboa opened this issue Sep 12, 2017 · 2 comments
Open

How to incorporate semantic trigger/custom syntax completer? #444

LindyBalboa opened this issue Sep 12, 2017 · 2 comments

Comments

@LindyBalboa
Copy link

I'm working on a LaTeX completer for ycmd and it works in vim. I'm slowly attempting to move to emacs and have comanpy/ycmd as part of that setup, but I can't seem to figue this bit out. I get as far as "No semantic completer exists for filetypes ['generic']" when calling ycmd-completer.

I guess at the minimum I somehow need emacs-ycmd to pass ['tex'] to ycmd? Then after that how might I go about getting \ and { (and later on a list of regexps) to trigger completion? Is the second issue a emacs-ycmd one or a company one?

It seems #259 might have to do with this, but I'm not in a position to figure out the code. Maybe someone could document that a bit more?

Thanks!

@abingham
Copy link
Owner

I've pushed up a new latext-support branch that ought to do (or at least be close to!) what you need.

If ycmd also has "diagnostic" support for latex, you should also look at ycmd--file-types-with-diagnostics. You might also want to update ycmd-keywords-alist with latex keywords.

I'll help with this as much as I can, but a) I'm a bit overloaded and c) I only know enough latex to occasionally be dangerous. But I think what you're doing should be relatively straightforward. Thanks for contributing!

@abingham
Copy link
Owner

@LindyBalboa Did this help you at all?

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