nvim-flutter / nvim-flutter/flutter-tools.nvim
[FR} - Ability to set fixed height for `__FLUTTER_DEV_LOG__`
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 1.4k
- Forks
- 116
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
Currently I'm using the following in my config:
init = function()
vim.api.nvim_create_autocmd("BufEnter", {
pattern = "__FLUTTER_DEV_LOG__", -- Flutter log buffers have this pattern
callback = function()
vim.wo.winfixheight = true -- Lock height
end,
})
end,
This locks the height according to what I've specified here:
dev_log = {
open_cmd = "botright 10split", -- command to use to open the log buffer
}
The good thing about this is ff your terminal window resizes, the dev log buffer remains at its fixed height.
The problem:
Debugging flutter apps often require restarting or resizing the window of the application being debugged which if you're using a WTM can become super annoying having to manually resize the dev log window every time.
Would be super convenient if we're able to have this built in to the config opts for dev_log though.
Cheers
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the dev_log configuration and its open_cmd are handled when the FLUTTER_DEV_LOG buffer is created. Compare that flow with the issue's BufEnter and winfixheight example. Done means a dev_log height can be configured and remains fixed when the terminal or application window is resized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flutter, lua, neovim
- Domain
- mobile-dev, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100