Skip to content
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

Question about your telescope config #10

Open
JustAHobbyDev opened this issue Jan 11, 2025 · 0 comments
Open

Question about your telescope config #10

JustAHobbyDev opened this issue Jan 11, 2025 · 0 comments

Comments

@JustAHobbyDev
Copy link

JustAHobbyDev commented Jan 11, 2025

pcall(require("telescope").load_extension, "fzf")
pcall(require("telescope").load_extension, "smart_history")
pcall(require("telescope").load_extension, "ui-select")

Hey Teej! I've been enjoying your Advent of Nvim video series. While I'm not new to Neovim, it has been great getting the guided tour through the configuration and has helped me refine my own.

That said, I've been looking at other people's configs on GitHub abd I noticed a few things about your Telescope config that I was curious about:

  1. You've opted for no config directive in the spec. I'm guessing you don't think it necessary because your telescope is not lazy loaded? I think I've misunderstood how lazy loading works until recently. As per the lazy.nvim docs:

Plugins will be lazy-loaded when one of the following is true:

The plugin only exists as a dependency in your spec
It has an event, cmd, ft or keys key
config.defaults.lazy == true

  1. Your use of pcall to load the extensions. Is this needed because Telescope is not lazy loaded?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant