Fix cargo module load when executable is not present.

[undyamon]

Closes #17

[Shatur]

Maybe put Job:new here to avoid checking if it's an executable twice?

[undyamon]

You mean something like this?

  local ok, job = pcall(Job.new, Job, {
    command = 'cargo',
    args = { '--list' },
    enabled_recording = true,
  })
  if not ok then
    utils.notify(job, vim.log.levels.WARN)
    return {}
  end
  job:sync()

  if job.code ~= 0 or job.signal ~= 0 then
    utils.notify('Unable to get list of available cargo subcommands', vim.log.levels.WARN)
    return {}
  end

[Shatur]

Yep!

[undyamon]

I pushed so I could test the config in nixos. Hold on a sec.

[undyamon]

utils.notify(job, vim.log.levels.WARN)

This line dumps the stack trace as a warning the first time one uses auto (and it realizes cargo is not available). It is slightly annoying because it causes the classic Press ENTER or type command to continue.

Do you have a better idea on how to handle this? Sometimes it could be useful to get the warning so I don't think we should discard it.

[Shatur]

I think it's fine if user uses auto in a repo with Cargo.toml? But instead of stacktrace I would write something like 'unable to execute "cargo"'.