micro-editor / micro-editor/micro
Dynamic display of `InfoBar` messages
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
Description
Personally, I find the info bar mostly an eyesore. Either it's spams with generic actions logging, taking up space unnecessarily, or it keeps displaying that stale latest message even when it's no longer relevant. And for this reason, I prefer to keep it hidden.
However, sometimes seeing a single timely warning can become a real life timesaver, and there's no way around it. Yet.
Thus, I'd like to suggest an alternative approach, or rather optional improvements to the current one, since not everyone may agree with me on this:
-
Desired behavior:
https://github.com/user-attachments/assets/744ebcd2-c3a9-4661-9844-303afd1db191
-
Desired implementation (names are merely placeholders):
infobell: option sets the minimal level of verbosity (Message,Warning,Error,Pluginetc.) that triggers the display of theInfoBarinfobell.timeout: how long to displayInfoBarinms; renew the timer if currently shown and/or the message's being updatedinfobell: ""orinfobell.timeout: 0means keep it hidden unconditionally- only relevant when
infobar: false - ? inherit the behavior pattern of the
promptwhere it overlaps the status bar instead of toggling the info panel every time, as long as the prompt still has the higher priority - ...
Contributor guide
No contributing guide indexed for this repository
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 reviewing the existing InfoBar, infobar setting, and prompt behavior described in the issue; no source files or tests are named. Define the interaction between verbosity thresholds, timeout renewal, hidden infobars, and prompt priority, then identify tests that can verify the proposed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100