-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Fix: error when closing the result buffer and trying to reopen it #188
Conversation
…r in split mode after having closed it manually
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Your free trial has expired. To keep using Ellipsis, sign up at https://app.ellipsis.dev for $20/seat/month or reach us at help@ellipsis.dev |
|
WalkthroughThe changes enhance the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- lua/hurl/split.lua (3 hunks)
Additional comments not posted (2)
lua/hurl/split.lua (2)
20-25
: LGTM! Centralized buffer cleanup logic.The
quit
function centralizes buffer cleanup logic, ensuring a cleaner and more maintainable approach.
38-39
: LGTM! Ensure thequit
function is correctly invoked.The
BufLeave
event handler now calls thequit
function instead of directly invokingsplit:unmount()
.Verification successful
The
quit
function is correctly invoked in place ofsplit:unmount()
.The
BufLeave
event handler now calls thequit
function, which includes thesplit:unmount()
call, ensuring the intended functionality is preserved.
lua/hurl/split.lua
: Thequit
function is defined and invoked correctly.lua/hurl/popup.lua
: Thequit
function is defined and invoked correctly.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the `quit` function is correctly invoked in the codebase. # Test: Search for the `quit` function usage. Expect: Only occurrences of the new implementation. rg --type lua -A 5 $'quit'Length of output: 1906
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- lua/hurl/split.lua (3 hunks)
Files skipped from review as they are similar to previous changes (1)
- lua/hurl/split.lua
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. LGTM!
@all-contributors add @javoscript for code. |
@javoscript already contributed before to code |
WHAT
Steps to reproduce bug without fix:
:q
WHY
Annoying bug 🐛
HOW
Call the
quit()
function, which has some extra functionality, instead ofsplit:unmount()
directly on theBufLeave
event handler.Screenshots (if appropriate):
Types of changes
Checklist:
Summary by CodeRabbit
New Features
Bug Fixes