| T O P I C R E V I E W |
| XMi |
Posted - Apr 18 2015 : 06:32:44 AM
Hi,
The new VA Hashtag feature is nice. However there is a little problem: comments containing URL with a # used as a
URL fragment identifier (http://en.wikipedia.org/wiki/Fragment_identifier) are considered as hashtags by VA.
For example, If I have the following comment:
// For more info, see:
// https://url.spec.whatwg.org/#urls
The VA Hashtag window will list the hashtag #urls |
| 8 L A T E S T R E P L I E S (Newest First) |
| gregmarr |
Posted - May 18 2015 : 11:23:52 AM
quote:
Originally posted by feline
The ability to exclude directories is planned for the next build.
Thanks.
|
| gregmarr |
Posted - May 17 2015 : 10:06:54 PM
quote:
Originally posted by gregmarr
A character got lost in my first example. It should be #xA9;
and it's still missing. There should be a & before the #.
|
| feline |
Posted - May 16 2015 : 6:38:34 PM
The ability to exclude directories is planned for the next build. |
| gregmarr |
Posted - May 11 2015 : 8:23:53 PM
Being able to exclude directories would certainly be helpful.
|
| gregmarr |
Posted - May 11 2015 : 8:21:30 PM
A character got lost in my first example. It should be #xA9;
The second example is because 1.#QNAN00000000 is a single string with a # in the middle.
The third and fourth examples are contained inside quoted strings in the comment, which is why I said that they could go either way.
Here's some context on these examples.
// Hexadecimal character reference.
// Pass through unchanged.
// #xA9; -- copyright symbol, for example.
/*
The 7ffd bit pattern seems to be enough to cause the
FLT_INVALID_OPERATION but displays itself in MSDEV as
1.#QNAN00000000000, which looks more like a quiet NaN.
*/
/* Strip the prepended error numbers ("#nnn ") from error and warning
* messages before passing them to the error or warning handler.
*/
/* Strip "#nnnn " from beginning of error message. */
Would it make sense to say that the tags must be surrounded by whitespace or comment delimiters?
So these would be recognized as tags
/*& #xA9 ;*/
/*1. #QNAN0000000000*/
//#QNAN00000000
but not these
/*#xA9 ;*/
/*& #xA9;*/
/*1.#QNAN0000000000*/
|
| feline |
Posted - Apr 23 2015 : 3:36:25 PM
You can set the minimum length for a tag, which might help a bit, depending on how you are using Hashtags:
http://docs.wholetomato.com/default.asp?W578
The problem with your examples is that I am not sure how to turn these into guidelines for what to include vs what to exclude. Simply saying that Hashtags cannot contain digits seems unwise.
Personally, I can actually see myself using something like #XXX as a rough and ready marker for something I am currently working on. It would not mean anything, but it would be another form of IDE bookmark, fast to type and not requiring any thought.
Are these stray tags coming from within your solution, or from libraries? We are considering allowing you to exclude directories, so I am wondering if that would help here. |
| gregmarr |
Posted - Apr 23 2015 : 2:24:38 PM
Some more things that definitely aren't
#xA9;
1.#QNAN00000000000
and some that could go either way
// ("#NNN")
// "#NNN"
|
| feline |
Posted - Apr 20 2015 : 5:34:43 PM
I am seeing the same effect here. Thank you for the clear description.
case=89145
A couple of other users have reported the same problem. We did not expect the # right after the / in a URL, but have now fixed this internally, so this should be fixed in the next build of VA. |
