Skip to content

the way to identify escape character in state_string.go need to be improved #251

@foxdd

Description

@foxdd

Describe the bug
it's in the 25th line of state_string.go. Currently, only fileJob.Content[i-1] is put into consideration that if it is back slash. But what if two consecutive back slashes there which represents one escape bachslash character and has nothing to do with the following end string? Therefore, four, six... back slashes are also possible.

To Reproduce

  1. As it is described ahead

Expected behavior
we need to judge the number of back slashes before the end string are even, so we can process the next checkForMatchSingle function

Desktop (please complete the following information):

  • OS: [e.g. macOS, Windows, Linux]
  • Version [e.g. 22]

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions