Diff for "FriendlyHGPlan"

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 Name

[ui]
modernize = yes

Rejected alternatives: friendly, progressive: These have negative implications we don't particularly like.

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
  • needs an easy way to disable when it breaks something
• diff.showfunc=1
  • needs an easy way to disable when it breaks something

• eradicate all instances of the word tip (tip command, tip pseudo-tag)

• change default ui.interface to curses

Ideas for later

• hg update gains a default of --check

• disallow bare hg push

• 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

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.

CategoryNewFeatures