fix: correct alacritty executable name in terminal detection (allacrity → alacritty)#32
fix: correct alacritty executable name in terminal detection (allacrity → alacritty)#32Jah-yee wants to merge 1 commit into
Conversation
Fixes DevcontainerConnect terminal detection when using alacritty. The vim.fn.executable() check used 'allacrity' instead of 'alacritty', causing the terminal detection to fall through to the 'no supported terminal emulator found' branch and silently fail. Fixes erichlf#31
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughFixed a typo in the Alacritty terminal emulator detection logic within ChangesTerminal Emulator Detection
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Fix DevcontainerConnect terminal detection when using alacritty as the terminal emulator.
Root cause
In
lua/devcontainer-cli/devcontainer_utils.lualine 238, thevim.fn.executable()check incorrectly usedallacrityinstead ofalacritty:This caused the terminal detection to fall through to the "no supported terminal emulator found" branch, making
DevcontainerConnectsilently fail (Neovim closes but no alacritty window spawns).Fix
1 character change:
allacrity→alacritty.Testing
vim.fn.executable("alacritty")now correctly returns1when alacritty is installed, allowing the proper terminal detection branch to execute.Related
Fixes #31
Summary by CodeRabbit
Bug Fixes