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
As part of #1861, this issue is to track removing the support for the "basic" regex flag that sets the pattern to BRE syntax.
The questions are:
Should the "b"/"basic" flag be removed altogether, and we pretend it doesn't exist? Or should it still exist in the list of flags, be annotated "deprecated" in the print output, and cause an explicit fatal error if used?
Should the "e"/"extend" flag for ERE syntax also be removed, since there is no other syntax option anyway and it's pointless?
The text was updated successfully, but these errors were encountered:
...be annotated "deprecated" in the print output, and cause an explicit fatal error if used?
Yes.
Should the "e"/"extend" flag for ERE syntax also be removed, since there is no other syntax option anyway and it's pointless?
Please, keep e flag. I assume e is still used in some old .ctags files.
Removing b has very strong reason. However, e has not.
Even if we remove e, we cannot reuse e for another purpose.
Both e and b are kinds of retired numbers.
BTW, though I like using long names for flags, we can still introduce a letter flag(short flag) if it helps writing .ctags. I have not enough experience to decide whether a flag should be short. So I always choose long names.
As part of #1861, this issue is to track removing the support for the "basic" regex flag that sets the pattern to BRE syntax.
The questions are:
Should the "b"/"basic" flag be removed altogether, and we pretend it doesn't exist? Or should it still exist in the list of flags, be annotated "deprecated" in the print output, and cause an explicit fatal error if used?
Should the "e"/"extend" flag for ERE syntax also be removed, since there is no other syntax option anyway and it's pointless?
The text was updated successfully, but these errors were encountered: