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

bug: long response from :BackseatAsk does not wrap on display box #10

Closed
luiz00martins opened this issue Apr 5, 2023 · 7 comments
Closed

Comments

@luiz00martins
Copy link

When displaying the answer from :BackseatAsk, the UI box seems to not wrap the text, instead seemingly continuing outside of the screen. As an example:

image

I imagine the phrase continues after "open buffers, window layouts, and", however, it got cut off.

@luiz00martins luiz00martins changed the title bug: long response from :BackseatAsk does not wrap bug: long response from :BackseatAsk does not wrap on display box Apr 5, 2023
@james1236
Copy link
Owner

Fixed in d88695e!

@luiz00martins
Copy link
Author

Still broken on my end:
image

(Worth to note the "temporarilyenable" and "searchfeature". They probably point to the issue.)

@james1236
Copy link
Owner

james1236 commented Apr 5, 2023

Are you using windows? Maybe this is a \n vs \r\n issue since it works for me.
image

@james1236 james1236 reopened this Apr 5, 2023
@luiz00martins
Copy link
Author

Yep! I'm on windows.

@james1236
Copy link
Owner

It shouldn't make a difference, since I use \n to split virtual text feedback lines and I assume that works for you, but I have changed BackseatAsk output to use \r\n. Maybe try now? (image unrelated)

image

@luiz00martins
Copy link
Author

Found the issue. It turns out it's not a backseat.nvim issue at all, but a noice.nvim one.

This is the MWE config:

using {
	'james1236/backseat.nvim',
	config = function()
		require('backseat').setup()
	end,
}

using {
	'folke/noice.nvim',
	dependencies = {
		'MunifTanjim/nui.nvim',
		'rcarriga/nvim-notify',
	},
	config = function()
		require('noice').setup()
	end,
}

This will produce the odd cut-off.

May I ask you what exactly you are using to display the text, so I may open an issue to noice? (or you can open it yourself, if you wish!)

@james1236
Copy link
Owner

I am using vim.fn.confirm, thanks for figuring it out!

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