#486 bash syntax parsing bug

closed-wont-fix
None
5
2005-08-29
2005-08-03
Ferry Huberts
No

the following bash code fragment is not parsed
correctly for syntax:

local oldname="`grep -E "$grepstr" "$tmpdir$GETDEVICES" | \ sed -r "s#$grepstr#\1#" | \ sed -r "s#$sedstr#\1#"`"

I need to add the following line to circumvent the
parsing bug:

# circumvent nedit parsing bug for bash `

Discussion

  • Ferry Huberts
    Ferry Huberts
    2005-08-03

    Logged In: YES
    user_id=1309269

    some system info:

    NEdit 5.5
    Sep 30, 2004

    Built on: Linux, 386, GNU C
    Built at: Oct 1 2004, 15:55:40
    With Motif: 2.1.30 [@(#)Motif Version 2.1.30]
    Running Motif: 2.1 [unknown]
    Server: The XFree86 Project, Inc 40300000
    Visual: 24-bit TrueColor (ID 0x22, Default)
    Locale: en_US.UTF-8

     
  • Thorsten Haude
    Thorsten Haude
    2005-08-03

    • assigned_to: nobody --> yooden
     
  • Thorsten Haude
    Thorsten Haude
    2005-08-14

    • status: open --> pending-wont-fix
     
  • Thorsten Haude
    Thorsten Haude
    2005-08-14

    Logged In: YES
    user_id=119143

    This is another case of missing recursiveness in NEdit's
    syntax highlighting patterns. Sorry, but the shells are
    offering something which NEdit can't at the moment.

     
  • Logged In: YES
    user_id=1312539

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
    • status: pending-wont-fix --> closed-wont-fix