[Commented On] D11751: rhg: only complain about poorly configured fallback when falling back

[aalekseyev (Arseniy Alekseyev)]

aalekseyev added a comment.


  > I'm not sure I understand what your use case is. The config is already fully read by the point we read it, so how does that help you?
  
  The static config we have only has on-unsupported=fallback, while the fallback executable is set by a command-line invocation, because that's where it's decided what the fallback binary should be.
  This makes it so  that when I'm making my own command line rhg invocation for debugging I have to either pass on-unsupported=abort, or an actual fallback executable, which is a bit of a chore.
  
  Anyway, the point here is not to support this exact workflow, but simply to be a bit more forgiving to the format (so that omitting the executable is equivalent to specifying an invalid executable).

REPOSITORY
  rHG Mercurial

CHANGES SINCE LAST ACTION
  https://phab.mercurial-scm.org/D11751/new/

REVISION DETAIL
  https://phab.mercurial-scm.org/D11751

To: aalekseyev, #hg-reviewers
Cc: Alphare, mercurial-patches
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-patches/attachments/20211124/9ea32ee7/attachment-0002.html>