4

The dot(.) in username within first 3 character preventing from comment replies?

Because I never got replies from anyone else using that feature.

Improve this question

3 Answers 3

Reset to default
5

Ooops, I misspoke in this answer. Apologies.

This was a long-standing bug of too-strict matching on @foo -- it now uses the proper valid username character set to match, [\w'\.\-].

Will be fixed in next deploy, within a few hours.

Improve this answer
3
  • @Jeff: The underscore _ is missing in your character set although it's valid in user names and appears to work just fine in comment notifications. I'm not sure, however, if I should add _ or \_ to your list.
    – Hendrik Vogt
    Commented Sep 2, 2011 at 12:50
  • @hendrik \w includes underscore. See regular-expressions.info/reference.html
    – Jeff Atwood
    Commented Sep 2, 2011 at 13:00
  • @Jeff: Ah, great, thanks a lot! I only looked at man grep on my linux console, where I didn't find that.
    – Hendrik Vogt
    Commented Sep 2, 2011 at 13:03
2

I had forgotten about that, but yes, apparently either the FAQ or the implementation need updating.

Improve this answer
0
0

Note that trailing dots (though valid in a user name) are removed before matching.

Hence Thanks, @name. matches both Name. with the dot, and Name without the dot. But: @R. is too short to notify R. Smith.

Improve this answer
2
  • The last part is not true, @R. does very well match R. Smith (we obviously don't remove the trailing period if that would leave just one letter; that wouldn't make any sense). My point in that comment was just that it may not be the best idea to always strive for the shortest possible combination of letters to reply to someone.
    – balpha StaffMod
    Commented Jan 28, 2011 at 6:35
  • oops, just realized I was digging up an ancient post... Deleting...
    – NH.
    Commented Jan 16, 2018 at 15:03

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .