disable blink for cmdline

[NobbZ]

Summary by CodeRabbit

• New Features
  • Updated the command line behavior through a new configuration option. The command line functionality is now disabled by default during standard operations, while support remains available for search-specific interactions. This update refines the user experience by clearly aligning functionality with different usage contexts.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new configuration option was added to the blink.cmp module in the plugins/nobbz/lua/nobbz/blink.lua file. The change introduces a cmdline table with the property enabled set to false, effectively disabling the command line functionality while retaining search context functionality. Additional comments provide context and reference a GitHub discussion for further clarification.

Changes

File(s)	Change Summary
plugins/nobbz/lua/nobbz/blink.lua	Added cmdline = { enabled = false } in the setup of blink.cmp, with comments clarifying that command line functionality is disabled for non-search contexts.

Poem

Oh, what a hop in the code I see,
A new config option prances with glee.
cmdline now rests with "false" in its heart,
While comments whisper their clarifying art.
Hoppy celebrations in bytes and light,
This rabbit cheers your code tonight!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5f11460 and 7274731.

📒 Files selected for processing (1)

• plugins/nobbz/lua/nobbz/blink.lua (1 hunks)

🔇 Additional comments (1)

plugins/nobbz/lua/nobbz/blink.lua (1)

5-7: LGTM! Clear configuration change with helpful comments.

The addition of the cmdline = { enabled = false, } configuration explicitly disables blink functionality for the command line while keeping it enabled for search contexts, as intended in the PR objectives. The comments clearly explain the purpose and provide a useful reference to the relevant GitHub discussion.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.