swaroopch / byte-of-vim Goto Github PK

Introduction.md line 28.
In table comparing Vim with other editor:
There is: How to find and replace only in lines 50-100? Run :50,10s/old/new/g
Supposed to be: How to find and replace only in lines 50-100? Run :50,100s/old/new/g

I started reading the "Scripting" chapter of your nice book, and arrived at the Macro section. I tried out the macro proposed there across all lines and found out that it doesn't work in one of them. In particular, it doesn't work on the abul fazl is the historian line, because in step 4 of the macro when moving by one word, in most other lines the cursor would now be on the word is, but on this line it is on fazl instead, which means the macro for this particular line results in something like Abul was a the historian in Akbar's court., not at all what should have happened. And because this section is meant to showcase the power of macros, having the macro fail like that could confuse newcomers to Vim, leading them to think they did something wrong.
The most obvious solution for this would probably be to remove the abul fazl line altogether, since the other 3 lines are proof enough that the macro works well on a predictable context.
Thanks in advance for understanding.

P.S. Another step you could add to ensure the reproduction of the macro doesn't fail under different circumstances could be to add 0 at the beginning of the macro to ensure that the cursor is at the beginning of the line, because moving downwards lines by j often puts the cursor elsewhere than on the first character of the line, and when the macro is triggered from anywhere but the beginning of the line it obviously doesn't result in the desired outcome.

I'd be happy to do some small chunks of work on this - but it isn't clear what I can do to help.
If there were a list of issues, like "port chapter X to markdown" or "extract images from chapter y", I think these are things that people could help out with a little bit at a time. As is, I'm not sure how to assist. I got here by seeing the note welcoming contributions.

Even a section of the doc listing that incomplete parts would be helpful as we could submit pull requests with a part completed and that section removed from the list...