|
Size: 1483
Comment:
|
Size: 1741
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| * [[https://bitbucket.org/sr105/terse-status|terse status]] | * grep should search working copy by default |
| Line 14: | Line 14: |
| * progress | |
| Line 16: | Line 15: |
| * mergemarkers.detailed | |
| Line 20: | Line 18: |
| * pager? (durin42,mpm not a fan) | == Ideas for later == |
| Line 22: | Line 21: |
| * [[https://bitbucket.org/sr105/terse-status|terse status]] * not ready yet: has weird bugs, needs more discussion. * pager * durin42,mpm,marmoute not a fan * mergemarkers.detailed * Risky on some non-English systems == Rejected == * progress * needs to just move to core and be on by default |
Note:
This page is primarily intended for developers of Mercurial.
![/!\](/moin-static/modernized/img/alert.png "/!\"){kind=small}
This is still only an idea from durin42. It does NOT yet represent a plan of record.
Rationale
We've been accumulating functionality that the average user probably wants on by default, but can't always turn on by default due to our compatibility rules. The idea of "Friendly HG" is to give us an opt-in way for users to request our best features as they become polished and ready, even in cases where that violates some of our compatibility rules.
Proposed Items
- grep should search working copy by default
- show renames and copies in status
- color
- completely remove all traces of the rollback command
- diff.git=1
- diff.showfunc=1
- eradicate all instances of the word tip (tip command, tip pseudo-tag)
Ideas for later
disallow bare hg push
- not ready yet: has weird bugs, needs more discussion.
- pager
- durin42,mpm,marmoute not a fan
- mergemarkers.detailed
- Risky on some non-English systems
Rejected
- progress
- needs to just move to core and be on by default
Naming
The best proposal I've heard for the name for this config knob is ui.progressive. We want something that suggests the moving-target nature of the knob, but also doesn't imply that we think hg without this is bad, just that we think this is better.
Implementation
This would change some defaults, but users can still override things (for example, if we include pager, durin42 and mpm can put [extensions] pager = ! in their hgrc.) HGPLAIN would disable all default-changes from friendlyhg, so automation tooling still works as expected.