Skip to content
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

CSE: Imported rune constants appear to be bound to strings; formating issues #2921

Closed
martin-henz opened this issue Apr 10, 2024 · 1 comment · May be fixed by #2936
Closed

CSE: Imported rune constants appear to be bound to strings; formating issues #2921

martin-henz opened this issue Apr 10, 2024 · 1 comment · May be fixed by #2936
Labels
Bug Something isn't working minor Less important than important, but more than nice-to-have

Comments

@martin-henz
Copy link
Member

martin-henz commented Apr 10, 2024

Currently we have:

Screenshot 2024-04-10 at 9 15 35 AM

The environment shows "< RUNE >" instead of just . This makes it look like the value is a string.

Also note that the string "< RUNE >" exceeds the boundary of the frame box. This problem appears to be solved for real strings:

Screenshot 2024-04-10 at 9 15 51 AM
@martin-henz martin-henz added Bug Something isn't working minor Less important than important, but more than nice-to-have labels Apr 10, 2024
@martin-henz martin-henz changed the title Imported rune constants appear to be bound to strings; formating issues CSE: Imported rune constants appear to be bound to strings; formating issues Apr 10, 2024
@martin-henz
Copy link
Member Author

This is handled in the latest version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working minor Less important than important, but more than nice-to-have
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant