Skip to content

Conversation

Uzaaft
Copy link

@Uzaaft Uzaaft commented Oct 18, 2025

Stumbled upon this while adding amp.nvim to astrocommunity: AstroNvim/astrocommunity#1675

The vim.print messages feels disruptive and breaks the users "flow".

Like when I enter neovim after adding the plugin, the cursor gets moved to the cmdline like this:
image

And I have to dismiss it before it goes to where I expect it to. Feel like vim.notify is a better usage for this.

@bahrmichael
Copy link
Collaborator

Thank you for this PR and your work on astrocommunity! This change looks good to me, and I'll merge it tomorrow after some testing 👍

@bahrmichael
Copy link
Collaborator

I noticed that vim.notify is not a good fit here, as it will show a popup in my lazyvim setup. I think the right path forward here is using a logfile, and I'll work on that tomorrow 👍

Screenshot 2025-10-20 at 18 50 34

@Uzaaft
Copy link
Author

Uzaaft commented Oct 20, 2025

Got it. I thought that was the purpose of this, to notify the user of the loglevel they set, or else the initial implementation didnt make sense 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

Successfully merging this pull request may close these issues.

2 participants