There's not been an upstream ctags release in a few years, but the subversion repo has been fairly active. For example, attempting to run the openbsd cvs tree through Fedora's ctags will crash, but subversion ctags works fine. Can we consider updating to a more recent snapshot?
sure, i will consider it, thanks
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
I'm working on this area at the forked project named fishman/ctags. (https://github.com/fishman/ctags.) Major improvment is listed in https://github.com/fishman/ctags/blob/master/docs/f-news.rst . After repairing its build system(maintainer.mak), I will create a rpm package using copr. Could you evaluate it? I will report again.
> I'm working on this area at the forked project named fishman/ctags. > (https://github.com/fishman/ctags.) > > Major improvment is listed in > https://github.com/fishman/ctags/blob/master/docs/f-news.rst . > > After repairing its build system(maintainer.mak), I will create a rpm > package using copr. Could you evaluate it? > > I will report again. Sure, i will do.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Reopening for reconsidering what [comment 3] and [comment 4] dealt with. Actually, I've found this very bug rather by accident, since I was looking at https://github.com/majutsushi/tagbar (proper RPM packaging is also an option) and https://github.com/universal-ctags/ctags is referred from here as a recommended backend. And this appears to be indeed a maintained project (vs. rather dead sourceforge.net original unless it was moved elsewhere silently). And now I am pleasantly surprised that the project Masatake was talking about in [comment 3] now resolves to the very "new shiny" project I mentioned. Therefore, can we get that reconsidered for sure? Is possibly too much of breakage imminent that a separate, parallel package shall be considered instead?
Also note that, for instance, CSS is supported out-of-the-box: https://docs.ctags.io/en/latest/news.html#new-parsers meaning that no extra patches are need ([bug 786451]) to extend the usefulness.
universal ctags seems a continuing development of ctags and is well maintained ATM, i think we should replace ctags by universal ctags
I'm glad that you see it this way. Then, do you think this qualifies for a self contained change[1]? I'd be inclined to think so, plus arising publicity can only spark new interest in what ctags project offers in general + the benefits for Fedora could be detailed (new languages supported, etc.), which would be useful, I think (not only to get people ready for behavioural changes in some corner cases). That would likely mean that only Rawhide and subsequently F30 are eligible assuming the change is accepted -- deadline for proposals is in January 2019 [2]. Of course, the silent route is also possible, but the explicit route looks like a better proposition to me. I can help with the change page write-up. [1] https://fedoraproject.org/wiki/Changes/Policy#Self_contained_changes [2] https://fedoraproject.org/wiki/Releases/30/Schedule
Hi jan, i full agree with you that the explicit route is a better proposition here. It's great that you can help with the change page write-up. Thanks for your help!
Great, let me crank up a skeleton that we can finalize before proceeding further.
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle. Changing version to '30.
Moving back to rawhide. It's been seven years, it would be nice to see some movement on this.
I"d also like to see this shipping, Tried it out yesterday and the new ctags functionality is worth it alone.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Re-opening this one. Than, any chance you'd have the time to work on using universal ctags? If not, perhaps the folks who have offered to help here could be added as co-maintainers to help this move along? Most, if not all plugins for various editors (vim for me) are suggesting the use of universal-ctags. In fact a few of them are explicitly documenting that exuberant ctags are not supported. Here's an example: https://github.com/liuchengxu/vista.vim In the meantime, this COPR seems to be updated from time to time, so folks here can use that I guess: - https://copr.fedorainfracloud.org/coprs/jgoguen/universal-ctags/ Cheers,
ctags has been effectively dead for couple years now. I think it makes sense to move to universal-ctags in rawhide. I will make this change this week.
it's fixed in ctags-5.9-0.1.20210307.0.fc35
Thanks very much Than. Any chance of an update to F34 too which will release in a month or two? (F35 is still about a year away)
Where are we? This has been bugging me for years, Ruby support in Exuberant Ctags is abysmal. Anything I can help with?
Oh apologies, I just noticed it has been fixed in F35. I am still on ctags-5.8-31.fc34.x86_64! Thank you so much for this! A gamechanger!