Bug 79898 - vim highlights bash scripts incorrectly
vim highlights bash scripts incorrectly
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: vim (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Karsten Hopp
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-17 16:36 EST by Glen
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-12-19 06:55:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Glen 2002-12-17 16:36:52 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
When editing a bash script with vim, if there is a statement like:

variable=$(/bin/date)

then the $( and the ) get highlighted like they are errors, even though they aren't.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Open a bash script with vim.
2.Add a statement using the $( and )
3.
    

Actual Results:  The $( and ) are highlighted as though they are errors.

Expected Results:  Same as the actual results.

Additional info:
Comment 1 Karsten Hopp 2002-12-18 05:30:47 EST
Please change the first line of your shell script to '!#/bin/bash' instead of
'!#/bin/sh'. /bin/sh is a link and can point to any shell which might not
support the $(xxxx) command syntax. That's why vim shows this as an error.
Comment 2 Glen 2002-12-18 14:18:27 EST
My scripts already say #!/bin/bash at the top.
Comment 3 Karsten Hopp 2002-12-19 06:55:25 EST
Oh ;-(  
  
Well, it works with my version here which is the one from Rawhide.   
Please try the one from ftp://ftp.redhat.com/pub/redhat/linux/rawhide/ 
 

Note You need to log in before you can comment on or make changes to this bug.