D613: dispatch: store the command name which is going to run in ui object

[yuja (Yuya Nishihara)]

yuja added a comment.


  This reminds me the following patch series. The discussion was quite long, but
  IIRC, we generally liked the functionality, but didn't like the implementation
  that abuses "ui" object.
  
  http://mercurial.markmail.org/message/4wlaxqjqs74vpyxy
  
  > This will help us in checking which command we are running
  >  where ever we need command specific logic instead of putting the logic in every
  >  command.
  
  Do you have any usage example?

INLINE COMMENTS

> test-basic.t:5
> +  extensions.fsmonitor= (fsmonitor !)
> +  _internal.command=config
>    devel.all-warnings=true

Perhaps this shouldn't be exposed (i.e. shouldn't be a config value.)

REPOSITORY
  rHG Mercurial

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

To: pulkit, #hg-reviewers
Cc: yuja, mercurial-devel