Moving fb extensions to core.

[Matt Harbison]

On Thu, 06 Jul 2017 17:27:58 -0400, Martin von Zweigbergk via  
Mercurial-devel <mercurial-devel at mercurial-scm.org> wrote:

> On Thu, Jul 6, 2017 at 2:10 PM, Kevin Bullock
> <kbullock+mercurial at ringworld.org> wrote:
>>> On Jul 5, 2017, at 13:13, Pulkit Goyal <7895pulkit at gmail.com> wrote:
>>>
>>> morsestatus: This extension wraps the status command to show more
>>> things about the current state of the repo by showing if histedit,
>>> bisect, graft, unshelve, rebase or merge is going on and show how to
>>> continue and abort that state. I personally think adding a --more flag
>>> will be good.
>>
>> That sounds like `hg summary` to me, or at least sounds like things  
>> that `hg summary` ought to show. Another idea that I poked at a while  
>> back at Matt's behest, but never finished: having `hg summary` show  
>> what would happen on an `hg update`.
>
> "hg summary" doesn't include the list of modified files. If it did, I
> might get used to using it instead of using "hg status". I've found
> FB's morestatus very useful since it was enabled for me a month or two
> ago.

Would mixing a list of files and global state cause issues with  
templating?  Last week I tried setting a ctx on the formatter in the files  
command, hoping to print all of the files and sizes, with the {rev} as a  
banner.  Then loop over every revision in bash and print that, to try to  
find any huge files that were making the repo excessively large.

It seemed that if you set the context inside fm.startitem(), {rev} prints  
out for every file.  If you set it outside that call (in this case I set  
it before entering cmdutil.files()), it prints out first (but only once),  
no matter what order the keywords in the template are.  It seems like the  
current repo state items would be similar.

FWIW, I had the same initial thought as Kevin, though I haven't found  
summary very useful either and rarely reach for it.

>> To me, this extra info doesn't feel like a great fit for `hg status`,  
>> which also doesn't show things like: the current branch name, current  
>> commit ID, number of parents, etc. `hg status` has always just been  
>> about the state of the files in the working copy.
>>
>> pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
>> Kevin R. Bullock
>>
>> _______________________________________________
>> Mercurial-devel mailing list
>> Mercurial-devel at mercurial-scm.org
>> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel