[Octave-bug-tracker] [bug #55723] print -deps doesn't work with option -tight on Windows

[Mike Miller]

Follow-up Comment #5, bug #55723 (project octave):

There is a lot of logic in print.m for constructing command pipelines on
either Unixy systems or Windows systems. Part of that logic uses the " & "
separator between subsequent commands on Windows systems (and the " ; "
separator on Unixy systems). That shows in the debug output you pasted in
comment #0.

Is that still correct on current systems? Or is the command pipeline being
sent to bash even on Windows these days, and the " & " is being interpreted as
a background job delimiter?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55723>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/