Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rspec describe blocks whose titles include : are not discovered #11

Closed
NewAlexandria opened this issue Sep 4, 2013 · 4 comments
Closed

Comments

@NewAlexandria
Copy link

The matcher for describe blocks is imprecise.

Including a : in this list causes other errors (incorrect nesting). I tested this by rebuilding with such a change. Probably a regex matcher is needed somewhere.

Pardon I didn't research further.

@masatake
Copy link
Member

In the list : is not included.

@masatake
Copy link
Member

Now I understand what you mean.

@masatake masatake reopened this Jul 31, 2015
@NewAlexandria
Copy link
Author

Thank you

@masatake masatake changed the title rpsec describe blocks whose titles include : are not discovered rspec describe blocks whose titles include : are not discovered Nov 19, 2015
masatake added a commit to masatake/ctags that referenced this issue Nov 19, 2015
Close universal-ctags#453.

(This is about a bug spotted in universal-ctags#453 by @mislav and in universal-ctags#11 by
 @NewAlexandria.)

Kinds C and d are for Rspec.

Parts of code related to above kinds assume a ruby string
comes after Rspec keywords (describe or context).

This is a wrong assumption. A class name can be used there.

It is nice if ctags can handle these rspec code well, but we
don't have enough resource to make it now.

So in this commit I delete rspec related code temporary. I
just reserve a kind letter 'd' for rspec for the future. 'C'
is completely deleted because (1) describe and context have
the same meaning in rspec, and (2) we would like to assign
'C' for Ruby constant as ripper-tags does.

Signed-off-by: Masatake YAMATO <[email protected]>
b4n pushed a commit to geany/geany that referenced this issue Mar 19, 2016
Close universal-ctags/ctags#453.

(This is about a bug spotted in universal-ctags/ctags#453 by @mislav and
 in universal-ctags/ctags#11 by @NewAlexandria.)

Kinds C and d are for Rspec.

Parts of code related to above kinds assume a ruby string
comes after Rspec keywords (describe or context).

This is a wrong assumption. A class name can be used there.

It is nice if ctags can handle these rspec code well, but we
don't have enough resource to make it now.

So in this commit I delete rspec related code temporary. I
just reserve a kind letter 'd' for rspec for the future. 'C'
is completely deleted because (1) describe and context have
the same meaning in rspec, and (2) we would like to assign
'C' for Ruby constant as ripper-tags does.

Signed-off-by: Masatake YAMATO <[email protected]>
@masatake
Copy link
Member

RSpec parser is remiplemented as a regex based subparser running on Ruby base parser.
If the issue is still reproduced, reopen this with an example input.

pragmaware added a commit that referenced this issue Jan 18, 2018
…case

Units,C++: add an input crashing ctags
masatake pushed a commit to masatake/ctags that referenced this issue Mar 12, 2020
Add a new definition 'USE_UNICODE_AGE_PROPERTIES'. If undefine this,
age properties (e.g. \p{Age=6.3}) are disabled. Age properties require
large size of data, and it becomes larger when Unicode is updated.
Disabling this reduces the data size.

Related: universal-ctags#11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants