Skip to content

Commit

Permalink
Fix #354: use noautocmd in nvim_open_win call
Browse files Browse the repository at this point in the history
  • Loading branch information
@wbthomason
wbthomason committed Jun 3, 2021
1 parent a5f3d1a commit 3715ce4
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion lua/packer/display.lua
View file
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,8 @@ local function prompt_user(headline, body, callback)
row = y,
focusable = false,
style = 'minimal',
border = config.prompt_border
border = config.prompt_border,
noautocmd = true,
}

local win = api.nvim_open_win(buf, false, opts)
Expand Down

4 comments on commit 3715ce4

@beauwilliams
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This commit is causing a bug on my machine

Error executing vim.schedule lua callback: .../site/pack/packer/opt/packer.nvim/lua/packer/display.lua:152: Invalid key 'noautocmd'

Commenting out this line solves the issue for me right now.

@beauwilliams
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please note, update your neovim if you see this issue.

I went from neovim HEAD-a282a17_2 -> HEAD-36802b8_2 and it fixed the issue

FYI for homebrew users might need to run brew upgrade neovim --fetch-HEAD as just running brew upgrade neovim says its up to date

@wbthomason
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@beauwilliams @bashtoni Sorry, I've added a notice to the README indicating that users will need to be on a sufficiently recent Neovim to avoid this. I wish there was a mechanism to check if this feature existed before using it, but I'm not aware of any.

@beauwilliams
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No worries at all. Yep that's a great idea to stick a notice in the readme sure some others will have same issue too 👍

Please sign in to comment.