-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Relative paths of files() are passed to a command when custom_target
is used
#3589
Comments
evverx
added a commit
to evverx/systemd
that referenced
this issue
May 18, 2018
In systemd#6561, `run_target` was changed to `custom_target`, which inadvertenly caused relative paths to be passed to ctags due to mesonbuild/meson#3589. The switch to `run_target` causes absolute paths to be passed again and makes it easier to jump from file to file, hopefully delaying the need to exit Vim :-)
evverx
added a commit
to evverx/systemd
that referenced
this issue
May 18, 2018
In systemd#6561, `run_target` was changed to `custom_target`, which inadvertently caused relative paths to be passed to ctags due to mesonbuild/meson#3589. The switch to `run_target` causes absolute paths to be passed again and makes it easier to jump from file to file, hopefully delaying the need to exit Vim :-)
keszybz
pushed a commit
to systemd/systemd
that referenced
this issue
May 19, 2018
In #6561, `run_target` was changed to `custom_target`, which inadvertently caused relative paths to be passed to ctags due to mesonbuild/meson#3589. The switch to `run_target` causes absolute paths to be passed again and makes it easier to jump from file to file, hopefully delaying the need to exit Vim :-)
Yamakuzure
pushed a commit
to elogind/elogind
that referenced
this issue
Aug 23, 2018
In systemd/systemd#6561, `run_target` was changed to `custom_target`, which inadvertently caused relative paths to be passed to ctags due to mesonbuild/meson#3589. The switch to `run_target` causes absolute paths to be passed again and makes it easier to jump from file to file, hopefully delaying the need to exit Vim :-)
Yamakuzure
pushed a commit
to elogind/elogind
that referenced
this issue
Aug 24, 2018
In systemd/systemd#6561, `run_target` was changed to `custom_target`, which inadvertently caused relative paths to be passed to ctags due to mesonbuild/meson#3589. The switch to `run_target` causes absolute paths to be passed again and makes it easier to jump from file to file, hopefully delaying the need to exit Vim :-)
nyorain
added a commit
to nyorain/tokonoma
that referenced
this issue
Nov 18, 2019
evverx
added a commit
to evverx/systemd
that referenced
this issue
Jan 16, 2022
Looks like mesonbuild/meson#957 was reintroduced in meson-0.57.0 (and looking and https://mesonbuild.com/Release-notes-for-0-57-0.html I'm not sure whether it was intentional or not) so run_command can no longer be used to get around mesonbuild/meson#3589. Let's just force ctags to always use absolute paths to fix it once and for all.
keszybz
pushed a commit
to systemd/systemd
that referenced
this issue
Jan 18, 2022
Looks like mesonbuild/meson#957 was reintroduced in meson-0.57.0 (and looking and https://mesonbuild.com/Release-notes-for-0-57-0.html I'm not sure whether it was intentional or not) so run_command can no longer be used to get around mesonbuild/meson#3589. Let's just force ctags to always use absolute paths to fix it once and for all.
Yamakuzure
pushed a commit
to elogind/elogind
that referenced
this issue
Dec 21, 2022
Looks like mesonbuild/meson#957 was reintroduced in meson-0.57.0 (and looking and https://mesonbuild.com/Release-notes-for-0-57-0.html I'm not sure whether it was intentional or not) so run_command can no longer be used to get around mesonbuild/meson#3589. Let's just force ctags to always use absolute paths to fix it once and for all.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried to figure out why a switch from
run_target
tocustom_target
causedctags
to generatetags
containing relative paths. I found #1011 whererun_target
had been fixed, but it seems thatcustom_target
hasn't been changed similarly yet.The text was updated successfully, but these errors were encountered: