5 ms·
When will mercurial learn that these things should be default. One of the only reasons I moved to git was I didn't have to hand hold people setting up all the e
by apples2apples 13y ago
When will mercurial learn that these things should be default. One of the only reasons I moved to git was I didn't have to hand hold people setting up all the extensions.
- jordigh 13y agoWhenever I teach hg, I just give them a template .hgrc and the first lesson is about putting their name in there. It's a one-time cost for any Mercurial user. The Mercurial dev team is very conservative. The reason some of these extensions aren't default yet are due to bugs or because they don't work well on Windows or because they require the user to learn some advanced usage (e.g. an improper rebase can result in apparent data loss to the uninitiated). Some of these just have a plain yucky UI, e.g. histedit's UI is very close to "git rebase -i". It would be much nicer if it had some sort of curses interface instead. Mercurial is in this for long haul, and it gets better all the time. As its extensions mature, they'll be turned on by default. Right now, it's a matter of flipping them on.