-
Notifications
You must be signed in to change notification settings - Fork 272
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
Ctags problems with spaces in project name #738
Comments
Interesting… I launched correct version manually and discovered a bug in ctags!
|
Why are you posting ctags problems on |
First one is definitely geany plugin's bug, because it should be one argument instead of three. Yep, second is |
|
It is from geany's messages window, command is auto generated by P.S.: geany side bug can be fixed, and new ctags is in development: https://github.com/universal-ctags/ctags. |
and finally which plugin are you using? |
It is |
This should fix problems when the project file (and as a result the tags file too) contains spaces. Fixes the geany-plugins part of geany#738
This should fix problems when the project file (and as a result the tags file too) contains spaces. Fixes the geany-plugins part of geany#738
@v1993 Thanks for reporting the issue. I've added apostrophes around the generated tags file in #739 which should fix the issue in the plugin. Interestingly, I haven't been able to reproduce the problem itself here - even without the apostrophes tag generation worked fine with a project name containing spaces. But adding apostrophes around the name is definitely the right thing to do. |
This should fix problems when the project file (and as a result the tags file too) contains spaces. Fixes the geany-plugins part of geany#738
This should fix problems when the project file (and as a result the tags file too) contains spaces. Fixes the geany-plugins part of geany#738
This is hopefully fixed. Closing. |
So we have to single-quote
/home/v/compile/2048 NG/2048 NG.tags
.The text was updated successfully, but these errors were encountered: