Performance when completing cmdline ":!" and "e /"

[kting28]

When I enable command line completion, :! will freeze neovim for a good 10 seconds as it search through every command in the path. My unique network environment has paths that are expected to be slow . Is there anyway to either disable the :! completion or limit the entries it returns?

Similarly, I'm also looking for a way to either disable e / path completion as going from top root will trigger read to my / path which has NSF mounted drives that are mounted on access.

[saghen]

See https://cmp.saghen.dev/recipes#disable-completion-in-only-shell-command-mode for the former. For the latter, you could probably do something with sources.providers.path.enabled = function() ... end

[kting28]

Thanks for converting the issue to discussion. The shell command change works !

For the path , this is what I'm trying to achieve:

:e  /     # don't start completing yet .. this is root 
:e /a/b/c  # starts completing from 3 levels down

let me write the func that checks the input string has least X forward slashes to begin completion

[saghen]

Ah that would apply to the cmdline source rather than the path source in that case. Missed the :e in your original post, sorry about that

[kting28]

I added e / after I made the post :)

[kting28]

ok this seems to work - so any command followed by a space and a / will trigger the count of forward slashes until there's enough.

      cmdline = {
        enabled = function()
          local cmdtype = vim.fn.getcmdtype()
          local cmdline = vim.fn.getcmdline()
          
          -- Existing: ignore cmdline completions when executing shell commands
          if cmdtype ~= ':' or cmdline:match("^[%%0-9,'<>%-]*!") then
            return false
          end
          
          -- New: check for absolute paths starting from root
          local path_match = cmdline:match("%s(/[^%s]*)")
          if path_match then
            local slash_count = select(2, path_match:gsub("/", ""))
            return slash_count >= 6  -- Only enable completion 6 levels down 
          end
          
          return true
        end
      }
    }

but while investigating this, I noticed that built-in path completion does not have any hang at all ! i.e. with