Log In  

Here's a strange bug I found. If you write something like this in the code editor:


and you search for 0 with CTRL+F, it will highlight the first 0. If you then press CTRL+G, however, it will fail to find the second one. The same goes for the 5.

From my testing, this seems to only happen with every other occurence. If you search for 0 here:


then CTRL+G will only highlight the first and the third argument.

I've only had it happen with function arguments, and only with single-character arguments; single-letter variable names also have this problem. Putting a space after the commas also makes it behave properly.

It's a bit of a problem when writing tweetcarts where you have little whitespace, short variable names, and want to find variables or number literals to replace while optimizing :)

P#61417 2019-01-31 23:23

This has been fixed in 0.1.12. Thanks!

Fixed: CTRL-F search in code skips matches that are close together
P#63425 2019-04-12 05:58

[Please log in to post a comment]