[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 149443] New: lua script syntax highlighting errors (# operator,
From:       trick () icculus ! org
Date:       2007-09-01 4:11:31
Message-ID: 20070901061130.149443.trick () icculus ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=149443         
           Summary: lua script syntax highlighting errors (# operator,
                    strings, comments)
           Product: kate
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kwrite-devel kde org
        ReportedBy: trick icculus org


Version:            (using KDE KDE 3.5.7)
Installed from:    Unlisted Binary Package
OS:                Linux

A few issues with Lua script highlighting:

* The # character is treated by kate as a comment starter.  # does not start comments \
in Lua however, unless it's the first character of the script (to specify an \
interpreter to the shell in the usual way).  In stead, # is used as a string/table \
length operator (since Lua 5.1).

* Strings in single quotes are not recognized as strings at all by kate.

* Escape sequences within strings are not recognized.  Valid Lua escape sequences are \
\a, \b, \f, \n, \r, \t, \v, \\, \", \' and also \N, \NN, \NNN (where N is a decimal \
digit), and is evaluated in both double- and single-quote strings (but not block \
strings).

* Block strings are not recognized by kate.  Block strings start with [[ and end only \
with ]] (multiline), or (since Lua 5.1) can also have a variable number of equal \
signs between the two brackets, matching the end brackets with the same amount of \
equal signs (eg [==[ matches ]==] and not anything else).

* Long (block) comments are also not recognized.  Block comments are comments \
                immediately followed by a block string start, and ends at the next \
                block end, eg:
--[[
 multi-line
   comment
-- foo ]]
(The extended equal sign syntax can be used for block comments too.)


(As a side note, it's impossible to search existing bugs for 'lua' since the search \
engine discards strings of less than 4 chars)


[prev in list] [next in list] [prev in thread] [next in thread]