search

proteanthread / vim

Automatically exported from code.google.com/p/vim
0 stars 0 forks source link

[PATCH] Missing "the" in documentation. #84

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. usr_41.txt reads "Sometimes you want to make a change and go back to where 
cursor was."

It should read "where the cursor was".

What version of the product are you using? On what operating system?

hg HEAD.

Attached is a patch to correct the problem.

Original issue reported on code.google.com by shlomifi...@gmail.com on 12 Oct 2012 at 7:57

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by brammool...@gmail.com on 12 Oct 2012 at 10:32

GoogleCodeExporter commented 9 years ago 
This issue is still present in «hg clone https://code.google.com/p/vim/» in 
revision «changeset:   3872:1001f417a37182832612cde6d11fb321907e49ea». Why 
was it closed as fixed without the patch being applied? Either it should be 
marked as invalid (which I believe it is not), or the patch should be applied 
and pushed before it is closed.

Frustrated,

-- Shlomi Fish

Original comment by shlomif@gmail.com on 18 Oct 2012 at 2:26

GoogleCodeExporter commented 9 years ago 
Runtime file changes go out at irregular intervals.  I mark items as fixed when 
I updated the master copy (that's on my harddisk, nobody else sees it yet).

Original comment by brammool...@gmail.com on 18 Oct 2012 at 6:21

GoogleCodeExporter commented 9 years ago 
Bram: OK, I see. Seems like there was a communication problem. Maybe include a 
standard blurb explaining all this when closing this bug in the future (and I 
don't understand why you can't use Mercurial for individual commits to the 
runtime files as well).

Original comment by shlomif@gmail.com on 21 Oct 2012 at 11:40

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
In reply to comment 4:
Bram does use Mercurial for individual runtime files, only he uses a private 
Vim repository on his hard disk. From time to time (and for instance between 
patches 7.3.702 and 7.3.703) he pushes them to the public repository from which 
everyone can pull them, thus bringing all runtime files in sync between private 
and public repositories. Otherwise it may happen that updated runtime files are 
published "out of turn" (for instance runtime/menu.vim at patch 7.3.696, and 
runtime/doc/eval.txt at patch 7.3.694 documenting an update to the src/eval.c 
file in the same patch) but it is the exception rather than the rule.

Original comment by antoine....@gmail.com on 21 Oct 2012 at 5:51