noautocmd?
- Dominant language
- Vim Script
- Stars
- 5.4k
- Forks
- 181
- PR merge metrics
- No merged PRs in 30d
Description
I'm wondering if there's anything to be done about the `noautocmd` wrappers around `enew` in this plugin. It prevents other plugins from knowing that the buffer has changed (e.g. I cannot capture `BufEnter` when I call `:Startify` even though a buffer has in fact been entered). I'm going to guess that we probably cannot get rid of the `noautocmd` but I figured I'd open up a convo about it just in case. Thanks.
Contributor guide
Research direction
Locate the noautocmd wrappers around enew and reproduce the issue by running :Startify while observing whether BufEnter is emitted. Compare the behavior with and without those wrappers and determine whether a safe, testable change is possible; the issue does not name a test or define a final resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vim
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100