-
Notifications
You must be signed in to change notification settings - Fork 189
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
More than one target found for 'myst' cross-reference [myst.xref_ambiguous] #892
Comments
Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗 |
We have not been able to find any notation to satisfy the MyST parser, trying to link to the |
I am also running into this issue. I need to have user be able to use the But I also have a 500 files with those same names. Having to rename those will be a pain. |
What version of
myst-parser
are you using?2.0.0
What version dependencies are you using?
$ python -c "import myst_parser; print(myst_parser.__version__)" 2.0.0
$ python -c "import docutils; print(docutils.__version__)" 0.20.1
$ python -c "import sphinx; print(sphinx.__version__)" 7.2.6
What operating system are you using?
Mac
Describe the Bug
Problem
In a file called
df.md
, we want to cross-reference theorm
label, which is in a fileorm.md
, next todf.md
, like(orm)= # CrateDB and ORM libraries
When doing it using MyST linking, in either of that form,
we are receiving the venerable ambiguity warning, which is an error in our case, because we are exclusively using Sphinx with
-W --keep-going
:However, we have not been able to find any notation to satisfy the MyST parser, in both directions, either trying to be more explicit to reference
std:ref:
, orstd:doc:
. Do you have any hints how to make it work?Workaround
It works well when using the
{doc}
/{ref}
syntax, apparently, well, because it is explicit by design?Expected Behavior
Documentation or Bug?
Thoughts
Regarding the handling of invalid references, it would be sweet if any of the applicable features to suppress warnings about
myst.xref_ambiguous
could be made work per-page through a corresponding front matter. We have not been able to make it work. If you can confirm, and agree, this item should probably make it into a separate issue?To Reproduce
Trivia: Within a file called
orm.md
, there is a reference label also calledorm
. C'est la vie.orm.md
(orm)= # CrateDB and ORM libraries
df.md
The text was updated successfully, but these errors were encountered: