On 2013-02-20 13:23, Tom Hayward wrote:
I just changed it to table format instead of code format. Is this more intuitive?
No, because it still appears as a sequence of operations (which it is). It's apparently an example of what you CAN do, and not what you SHOULD do, to get started. When I teach flying to a new student, I don't show them how to recover from a spin in the first lesson (some instructors do, but they don't retain many students) ...
It's raining, so I'm going to give this about an hour shot tonight. Each day I'll give it a try, until I have success, or get tired of the process.
During this journey, I may make sarcastic comments about the documentation (which is my complaint, not the actions of HG). Please don't take them personally; we are all volunteers. However, if the process of retaining volunteers is difficult, that adds to the load on the existing volunteers, so my hope is that they encourage modifications to the documentation. For I hope obvious reasons, I'm not the person to be making any documentation changes anytime soon.
So here goes:
#1. You say, "If this tool intrigues you, you can learn how to use it here: http://mercurial.selenic.com/wiki/MqTutorial". So, I guess if someone is not intrigued at the time (and thus doesn't follow the link), but just wants to submit some changes, one doesn't get to learn that you apparently need to do a "hg init --mq" at the beginning ...
-- to be continued ...