Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COIt is not going to work: a) there is no “!start” program, only “start” b) you forgot to escape spaces c) “start” treats `/wait` as a start of the command because it is not `start` program. `!start` is handled by vim internally and accepts only `/min` and `/b` arguments, only one of them at a time.
      singulars
    2. COTo use `start` program you have to escape it using double quotes. And escape quotes for use in `:set`. As I don’t like all those escapes command should look like `let &makeprg='"start" /min /wait ninja -C build-ninja'`, but it doesn’t look like it actually works: in this case “command not found errors” are not thrown which are if I use your variant with a) and b) issues resolved (i.e. removed bang and escaped spaces), but nothing gets started as well. It looks like cmd.exe just don’t like quotes here. Alternative is space before `start`, but leading spaces are stripped of `&makeprg` when run.
      singulars
    3. COYou can, of course, escape spaces and remove bang. It won’t make built-in replacement of `start` accept `/wait` argument. And `&makeprg` is unfortunately passed directly to the same code that is responsible for handling `!` commands with leading spaces stripped. I know how to resolve this issue (supply absolute path to executable), but `start.exe` is *not* capturing started programs output (at least its wine implementation). Hence it is useless as `&makeprg` value.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload