Community

    • Login
    • Search
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    sql language style issue with \"

    Help wanted · · · – – – · · ·
    3
    5
    122
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • jimp100
      jimp100 last edited by

      The built in sql language style seems to have issues parsing quoted literal string ending with a backslash, such as “C:\SQL Data\2019”.

      It looks as though the trailing backslash is being interpreted as an escape character which is causes a mismatched number of slashes and the wrong text rendered as a literal (grey colour).

      See lines 35,36,37 on these examples:

      With trailing slashes
      Issue

      Without trailing slashes
      Fixed

      Alan Kilborn 1 Reply Last reply Reply Quote 0
      • Alan Kilborn
        Alan Kilborn @jimp100 last edited by

        @jimp100

        Perhaps this is relevant to you:

        78bf94eb-9ed9-4a26-ace2-bbce3f17dc23-image.png

        jimp100 1 Reply Last reply Reply Quote 3
        • jimp100
          jimp100 @Alan Kilborn last edited by

          @alan-kilborn Thank you that’s just what I was after. I did look around for a setting, just completely missed it.

          Alan Kilborn 1 Reply Last reply Reply Quote 0
          • Alan Kilborn
            Alan Kilborn @jimp100 last edited by

            @jimp100 said in sql language style issue with \":

            I did look around for a setting, just completely missed it.

            It does feel like an orphan where it is! :-)

            PeterJones 1 Reply Last reply Reply Quote 2
            • PeterJones
              PeterJones @Alan Kilborn last edited by

              @alan-kilborn said in sql language style issue with \":

              It does feel like an orphan where it is!

              But being adopted by the Language tab, when it’s a Language-specific option, isn’t that extraordinary.

              The real issue is that more Languages should have Language-specific options (like whether JSON should accept comments or not; I think there are other Language-specific options that Scintilla offers that Notepad++ doesn’t give access to, as well), and those other options should go on the same page (with possibly shrinking the height of the Language Menu and Tab Settings columns)

              1 Reply Last reply Reply Quote 5
              • First post
                Last post
              Copyright © 2014 NodeBB Forums | Contributors