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

Autopair with cmp not working on python file #388

Closed
RoRep1ay opened this issue Sep 5, 2023 · 3 comments
Closed

Autopair with cmp not working on python file #388

RoRep1ay opened this issue Sep 5, 2023 · 3 comments
Labels
bug Something isn't working wontfix This will not be worked on

Comments

@RoRep1ay
Copy link

RoRep1ay commented Sep 5, 2023

Description

The autopairing is not working on completion on Python file. I've tried on go / js file, and both are working normally.

Mapping bug

1.If you report a bug about indent. Please remember that plugin doesn't do anything about indent.
It just trigger the indent of your vim config so if you have wrong indent config then it will do wrong indent.
You can check by select a block of code and press ==
2. provide result of command :verbose imap <cr>.

Steps to reproduce

Open a python file, insert print -> <CR> Only print is outputted
It should output print() with cursor inside the parenthesis.

Minimal config

local cmp_autopairs = require('nvim-autopairs.completion.cmp')
local cmp = require('cmp')
cmp.event:on(
  'confirm_done',
  cmp_autopairs.on_confirm_done()
)
@RoRep1ay RoRep1ay added the bug Something isn't working label Sep 5, 2023
@RoRep1ay
Copy link
Author

Did some little digging and realized it failed to do so because of this line:
https://github.com/windwp/nvim-autopairs/blob/master/lua/nvim-autopairs/completion/handlers.lua#L17

Seems like this is LSP server related. Right now, I'm using pyright, checking their source code, looks like they're setting this funcParensDisabled to true.

@liuyuzhenn
Copy link

Save issue here, pretty annoying.

Copy link

stale bot commented Nov 16, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Nov 16, 2023
@stale stale bot closed this as completed Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants