-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
Style the clickable “...” in the “arguments...:“ part of error messages to be more obviously clickable #390
Comments
What about an underline appearing when you mouse over it?
…On Fri, Jun 5, 2020 at 12:11 PM gfbee ***@***.***> wrote:
I have forgotten and rediscoverd this multiple times, and (some time ago)
at least one person on the slack asked how to see the apparently
unavailable elided arguments. Maybe we can also change it to something
other than ellipsis since in non-menu contexts it doesn't suggest further
interaction (and also it's not for the menu convention of meaning it will
involve further interaction).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#390>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADBNMBNQO2P74DM4FTHWGLRVERKXANCNFSM4NULC4UA>
.
|
That seems barely more discoverable. |
Suggestions welcome! :) |
Making the dots blue instead of red might help? So they look like a clickable link. |
Adding a space before the dots and moving them after the colon (or just removing the colon) would be good. Except that might interfere with any code thats been parsing the message to extract information. Although that might not be a problem if the change happens near where the actual display in DrRacket happens, in which case we can reconsider dots entirely. |
The dots are part of the formatting rules from the error message conventions. |
I have forgotten and rediscoverd this multiple times, and (some time ago) at least one person on the slack asked how to see the apparently unavailable elided arguments. Maybe we can also change it to something other than ellipsis since in non-menu contexts it doesn't suggest further interaction (and also it's not for the menu convention of meaning it will involve further interaction).
The edit just now changed the title to show the actual format “...:”. That I thought it was “:...” emphasizes the issue, since the “...” appears to say keep reading, the arguments are still to come after the “:”.
The text was updated successfully, but these errors were encountered: