Closed abeldekat closed 7 months ago
Thanks for the issue!
This is somewhat expected, though:
evaluate_single
is true
, it gets evaluated.I'll take a look if there is a reasonable approach to mitigate this.
After thinking more about this, I think this is an OK behavior. Mostly because it is somewhat expected (as described before). But also resolving this might contradict the design of allowing items to be evaluated several times in a single Starter buffer (like "narrow down" -> "evaluate" -> "narrow down" -> "evaluate" kind of loop).
Closing as "please don't create single entry items
along with evaluate_single = true
".
Closing as "please don't create single entry items along with evaluate_single = true".
This had me smile. I promise I won't do this ever again....)
Just had the same problem. In sections like recent files (current directory only) you can't know how many items there will be. This means evaluate_single = true
can't be used safely.
Just had the same problem. In sections like recent files (current directory only) you can't know how many items there will be. This means
evaluate_single = true
can't be used safely.
I think this might be the problem only on new-ish installation (or directory if latest files are configured to use only current directory) and if there is only one section. It seems like a reasonably rare and solvable (add section with "edit" and "quit" items, for example) issue.
Contributing guidelines
Module(s)
mini.starter
Description
I replaced dashboard-nvim with mini.starter, adding items one by one. When there is only one item in items, and evaluate_single=true, a stackoverflow occurs.
I think that the culprit is in this fragment
Neovim version
0.9.5
Steps to reproduce
Expected behavior
...
Actual behavior