Fwd: Switch to git?

[Brian Visel]

> Here's my two cents, if you don't mind.
> 
> Some time ago I was working on a Debian machine without a configured
> default editor and when I tried to run hg ci, it would start
> `sensible-editor`, and, since it wasn't configured either, it would in
> turn start `select-editor` (both scripts are from sensible-utils
> package).
> 
> It looked like this:
> 
> ---
> Select an editor.  To change later, run 'select-editor'.
>   1. /bin/ed
>   2. /bin/nano        <---- easiest
>   3. /usr/bin/vim.basic
>   4. /usr/bin/vim.nox
> 
> Choose 1-4 [2]:
> ---
> 
> If mercurial had something like this --a basic, but interactive,
> configurator-- it would ideally cover every new user's needs without
> the need (from a user) to read about and then select extensions
> one-by-one and (from a script) to guess defaults by his git/bazaar/svn
> config file.

..a list of available and enabled extensions would be quite nice --
something like:

1 [ ] * hgext.acl - Changeset Access Control
2 [ ] * hgext.alias - Allow user-defined command aliases
3 [X] * hgext.bookmarks - Provides the 'bookmarks' command
[...]
l [ ] * hgext.win32text - Unix/Mac/DOS line ending conversion utilities
m [ ] * hgext.zeroconf - mDNS/DNS-SD (Zeroconf) support for 'hg serve'
n [ ] ! hgext.zzfoobaz (/path/to/custom/mercurial/extension)
o - Enter the path to an external (unsupported) extension

Extensions marked with * are supported.
Extensions marked with ! are not supported.
Enter the corresponding character to enable or disable an extension: 


..being able to enable the extensions from the UI would give a distinct
sense of legitimacy to the whole thing..