-
Notifications
You must be signed in to change notification settings - Fork 14
Scope info does not provide links for the openings #122
Comments
I'm picturing a dropdown list of links (like in fuzzy search shift-cmd-p) when there are multiple sources of definition. |
I am actually very happy with the explicited list of openings. It gives a good overview on how the definition/module is linked to the structure of the library in use. Even if the dropdown would save screen space, it would make more difficult to visualize the chain of imports. Anyways, I share with you some useful generic design guidelines for dropdowns |
I'm thinking about making a module in the text a link, so that people can also access the intermediate openings |
Yes, makes sense. As a use case for its utility, I get the following when getting the scope info of
There is a renaming of A link to the Universes file would be useful in this case. The open question is if it is better to have the text of the module linked or if the link should be explicited like in the definition (eg. to copy and paste easily to the Terminal app). |
When calling the
go-to-definition
command i am getting the links to the definitions but not to the openings, but it seems that the link should be there because of the wording:I post it here because in agda/agda#4342 was explained that
go-to-definition
is anagda-mode
command.The text was updated successfully, but these errors were encountered: