Differences between revisions 2 and 3
Revision 2 as of 2015-03-12 19:30:43
Size: 1485
Editor: AugieFackler
Comment:
Revision 3 as of 2015-03-14 03:21:13
Size: 1483
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
 * [[https://bitbucket.org/durin42/terse-status|terse status]]  * [[https://bitbucket.org/sr105/terse-status|terse status]]

Note:

This page is primarily intended for developers of Mercurial.

/!\ 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

  • terse status

  • show renames and copies in status
  • color
  • progress
  • completely remove all traces of the rollback command
  • mergemarkers.detailed
  • diff.git=1
  • diff.showfunc=1
  • eradicate all instances of the word tip (tip command, tip pseudo-tag)
  • pager? (durin42,mpm not a fan)
  • disallow bare hg push

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.

FriendlyHGPlan (last edited 2017-12-06 21:53:09 by PulkitGoyal)