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
I think there should be only one search result pointing to the documentation of that function (the third one). The other two contain anchors, where the first one doesn't have any effect, and the second one scrolls down one line so that the heading is not visible (not useful IMO).
The text was updated successfully, but these errors were encountered:
the first result (the one where the anchor is all - separated, no .) is the permalink for that heading. generally I think we do want permalinks for headings in our docs, but I wonder if there's a way to disable generating them for the main h1 tag on an API page? It's written by docutils so not sure if it's configurable. The second result (where the anchor has a mix of . and - separators) I'm not sure where that comes from, and I suspect it's actually a bug --- searching for mne.io.read-raw-edf in the generated page source gets no hits so it's not even a valid anchor. My guess is that the latter (invalid) form is "original" and it gets sanitized to the all-dash version by either Sphinx or by the theme, but that sanitization process doesn't remove the old anchor from Sphinx's search index or something.
mne.io.read_raw_edf
mne.io.read_raw_edf (Python function, in mne.io.read_raw_edf)
mne.io.read_raw_edf
Specifically, the link to
I think there should be only one search result pointing to the documentation of that function (the third one). The other two contain anchors, where the first one doesn't have any effect, and the second one scrolls down one line so that the heading is not visible (not useful IMO).
The text was updated successfully, but these errors were encountered: