Question

We have snippets for quite a lot of things. For example, I have a snippet called o for some long and easy to misspell technical term. Aside: I even got it to work outside the text area.

Now when I type ( o `, I get this message:

'(o' is not a known snippet; type '`' again to list them all.

Apparently FogBugz regards the ( character as part of the snippet. Why?! I mean: sure, someone might want to create a snippet with parentheses in its name, but wouldn't it be much more useful to be able to use snippets directly after parentheses?

Same goes for double quotes. And for most (all?) other punctuation.

Can this please be fixed? Or made configurable?

Case FC2345289

Answer 1

I also initially thought this error was for the reason you hypothesize (i.e., what if someone wanted to include quotes or parentheses in their snippet name?), but upon looking a little closer this is actually just a flat-out bug.

If you try to create a new snippet using anything other than letter, numbers, underscores, and forward slahes you receive the following error:

Looking at our snippet code, this appears to be a matter of allowing one set of characters for snippet names at creation time but searching for a different set of characters when it comes time to use those snippets.

I've filed a case internally to have this looked at.

Update: This has been fixed and will be released in a future version of FogBugz.