You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2024. It is now read-only.
It appears that the vim-rtags unsaved-file feature does not work any more due to upstream changes in rtags.
it appears the --wait is flag is necessary for the reindexing of the unsaved file to complete before we attempt to run rc (otherwise we will attempt to e.g. jump to a symbol based on the old file contents). I expect that change occurred in this commit: Andersbakken/rtags@49494fe
the --unsaved-file path is no longer resolved from the relative path. This was changed here: Andersbakken/rtags@a35b093 It's possible that change was not necessary (I will open an upstream ticket to check), but in the meantime, I don't see a disadvantage to switching to passing absolute paths into unsaved file reindexing.
I will open a pull request with these changes.
The text was updated successfully, but these errors were encountered:
mvilim
pushed a commit
to mvilim/vim-rtags
that referenced
this issue
Oct 2, 2018
It appears that the vim-rtags unsaved-file feature does not work any more due to upstream changes in rtags.
it appears the --wait is flag is necessary for the reindexing of the unsaved file to complete before we attempt to run rc (otherwise we will attempt to e.g. jump to a symbol based on the old file contents). I expect that change occurred in this commit: Andersbakken/rtags@49494fe
the --unsaved-file path is no longer resolved from the relative path. This was changed here: Andersbakken/rtags@a35b093 It's possible that change was not necessary (I will open an upstream ticket to check), but in the meantime, I don't see a disadvantage to switching to passing absolute paths into unsaved file reindexing.
I will open a pull request with these changes.
The text was updated successfully, but these errors were encountered: