Closed mpourmpoulis closed 4 years ago
0fcbc51877481349f38878509cb96068217c9694 tried to take care off of problems with strings that had prefixes like r"something"
or u"something"
but introduced a typo mean
instead of min
which was causing the exception. However it failed To take care off triple quoted strings causing wrong results. Both these problems should now be solved in the develop branch
Description
General Information
Plug-In Version: v0.1.2,develop, probably the entire 0.1.x Is affected
Queries Affected
[ ] Argument
[ ] Big Roi
[x] Sub Indexing
[ ] Operations
[ ] Collections
picking up parts of certain types of strings fails! this also causes commands of the for
smart string 2
to fail if problematic strings are within the search spaceResponse To Command
[x] the command fails/nothing happens at all
[ ] the command select/operates on a wrong result,
[ ] somehow the whole preserving the current state(alternatives,origin,initial_origin and so on) was messed up by the command! For instance,
[ ] the command seems to select/operates on a random result
[ ] the command has some other unintended behavior
Context In Which It Appears
Does the problem seem to appear or disappear only some of the time? Does there seem to be
[ ] spatial context/correlation with the cursor? for instance
[ ] a temporal context?
[x] correlation with a pattern in the code? Such a pattern might be structural, sometimes lexical,in some cases even some piece of incomplete code that was not handled properly. A strong indicator for such a case when introducing small changes to the code has things from working perfectly into breaking. In case you have identified(or you have any suspicion about) this pattern(or maybe patterns), does the error occure when it appears
it seems that it does not like at all, when
"
or'
are inside a string that is surrounded by'
,"
respectivelyeven if they are escaped. In contrast these actually works
the same applies for triple quoted strings as well!
Error Message
[ ] error message appears in a pop-up
[x] an exception trace back is printed in the sublime console(Ctrl + `)
[ ] the command fails silently