You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read #1283 and closed #1448, #2010
I apologize if this has already been discussed elsewhere.
This issue has been observed presumably since version 9.0.0 (3rd of April, 2023) at least when running the PCRE2 flavor.
I work in extended (/x) mode with comments at the end of almost all lines. Previously, using tabs, I could neatly place the start of a new comment on the current line exactly below the start of the previous comment (on the previous line). At the time it looked like this:
Now it looks like this:
Do you know about this feature? Is this done on purpose and will it stay that way, or is it a bug?
_Originally posted by @alhimiker in https://github.com/cf/Regex101/issues/2044_
#> > ````~~![image](https://github.com/microsoft/computervision-recipes/assets/87707755/ba089f02-9d32-4322-966a-3330eebcfab1)~~`__
The text was updated successfully, but these errors were encountered:
Feature
I have read #1283 and closed #1448, #2010
I apologize if this has already been discussed elsewhere.
This issue has been observed presumably since version 9.0.0 (3rd of April, 2023) at least when running the PCRE2 flavor.
I work in extended (/x) mode with comments at the end of almost all lines. Previously, using tabs, I could neatly place the start of a new comment on the current line exactly below the start of the previous comment (on the previous line). At the time it looked like this:
Now it looks like this:
Do you know about this feature? Is this done on purpose and will it stay that way, or is it a bug?
The text was updated successfully, but these errors were encountered: