Red Hat Bugzilla – Bug 104312
period no longer delimits word boundaries when editing bash script in vim
Last modified: 2007-04-18 12:57:32 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
When editing a bash script in vim, the period no longer delimits word
boundaries. In other words, the "w" motion command acts as if "W" had been
pressed. The same is true for "cw", "b", etc.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a new file with text:
#this is.a test of vim
#in which the.motion.commands skip over periods.incorrectly
2. write and quit the file (:wq)
3. open the file again and press various motion keys (w, b, cw, dw)
4. remove line 1 (#!/bin/sh), then :wq
5. vi the file again and re-try the motion commands
Without the #!/bin/sh line, the motion commands work as expected
Actual Results: See steps to reproduce.
Expected Results: The word motion commands (w, b, cw, etc.) should stop at
periods. Only the uppercase versions of the commands should ignore periods.
vim did not perform this way in rh-8
I've tracked down the problem to the sh.vim syntax file.
iskeyword (isk) includes the period for some unknown reason.
just remove the line
to fix it. The next release will have this fix.